v2025.2 LTS Stable release with long-term support v2025.1 STS Stable release with standard-term support v2024.2 LTS Stable release with long-term support v2024.1 STS Stable release with standard-term support v2.20 LTS Stable release with long-term support Unsupported versions

Upgrade YugabyteDB Anywhere

You can use Helm to upgrade your YugabyteDB Anywhere (YBA) installed on Kubernetes to a newer version.

If you are upgrading a YugabyteDB Anywhere installation with high availability enabled, follow the instructions provided in Upgrade instances.

Install the YugabyteDB Kubernetes Operator
To install the YugabyteDB Kubernetes Operator on an existing YugabyteDB Anywhere instance, see Install Kubernetes Operator.

Before running an upgrade, execute the following command to obtain the latest versions of YugabyteDB Anywhere from Helm charts:

helm repo update

Upgrade using Helm

To upgrade to a specific version while preserving overrides you might have applied to your initial YugabyteDB Anywhere installation or previous upgrades, execute the following command:

helm upgrade yw-test yugabytedb/yugaware \
  --version 2025.2.2 \
  -n yb-platform \
  --reset-then-reuse-values \
  --set image.tag=2025.2.2.1-b1 \
  --atomic \
  --timeout 30m \
  --wait

To obtain the value for --set image.tag, execute the following command:

helm list | awk '{if (NR!=1) print $NF}'

If you do not wish to port your overrides, do not include --reset-then-reuse-values. Instead, you may choose to pass your existing overrides file by adding --values custom-values.yaml to your command during the upgrade.

When --atomic is used, if the upgrade fails for any reason (pods not Ready, hooks fail, timeout, and so on), Helm will automatically roll back to the last successful release.

Use --timeout to give the upgrade enough time; if the upgrade exceeds this time, Helm treats it as a failure, and (if --atomic is set) triggers a rollback.

When --wait is used, Helm waits for workloads to become Ready.

If you have upgraded YugabyteDB Anywhere to version 2.12 or later and xCluster replication for your universe was set up via yb-admin instead of the UI, follow the instructions provided in Synchronize replication after upgrade.