This guide shows W&B Server administrators how to update the W&B Server version and license key for an existing self-managed deployment. Keeping your server and license current ensures access to the latest features, fixes, and continued entitlement to use W&B Server. Update your W&B Server version and license with the same method you used to install W&B Server. The following table lists how to update your license and version based on different deployment methods.Documentation Index
Fetch the complete documentation index at: https://wb-21fd5541-docs-2661.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
| Release type | Description |
|---|---|
| Terraform | W&B supports three public Terraform modules for cloud deployment: AWS, Google Cloud, and Azure. |
| Helm | Use the Helm Chart to install W&B into an existing Kubernetes cluster. |
Update with Terraform
If you deployed W&B Server with one of the W&B-maintained Terraform modules, use Terraform to update both your license key and the W&B version in place. The following table lists W&B-managed Terraform modules by cloud platform.| Cloud provider | Terraform module |
|---|---|
| AWS | AWS Terraform module |
| Google Cloud | Google Cloud Terraform module |
| Azure | Azure Terraform module |
- Navigate to the W&B-maintained Terraform module for your cloud provider. See the preceding table to find the Terraform module that matches your cloud provider.
-
In your Terraform configuration, update
wandb_versionandlicensein your Terraformwandb_appmodule configuration: -
Apply the Terraform configuration with
terraform planandterraform apply. -
Optional: If you use a
terraform.tfvarsor other.tfvarsfile, update or create one with the new W&B version and license key.From your Terraform workspace directory, apply the configuration:
Update with Helm
Two Helm-based update paths are available: update from your existing Helm values file, or set the new license and image tag directly on the upgrade command. The following sections describe each approach.Update W&B with spec
Use this approach when you manage your Helm configuration in a tracked*.yaml values file.
-
Specify a new version by modifying the
image.tagorlicensevalues, or both, in your Helm chart*.yamlconfiguration file: -
Update the Helm repository and upgrade the W&B release using your values file:
Update license and version directly
Use this approach to update the license and image tag without editing a values file, and reuse your existing Helm release configuration.-
Set the new license key and image tag as environment variables:
-
Upgrade your Helm release, merging the new values with the existing configuration:
Update with admin UI
Use the admin UI to rotate your license key from within the W&B App, without changing your deployment configuration. This method only works for updating licenses that aren’t set with an environment variable in the W&B server container, typically in self-managed Docker installations. This method updates the license only. It doesn’t change the running W&B Server version.- Obtain a new license from the W&B Deployment Page, ensuring it matches the correct organization and deployment ID for the deployment you want to upgrade.
- Access the License page in the W&B App. Click Settings > License or browse to
HOST_URL/console/settings/license, whereHOST_URLis your W&B Server host URL. - Navigate to the license management section.
- Enter the new license key and save your changes.