Upgrade your solution
Install a more recent package, apply the required changes in configuration, and upgrade the helm charts
Read time 1 minuteLast updated 6 days ago
The upgrade process requires that you pull a more recent package, using the same method as described for the first installation.
To upgrade your solution, complete these steps:
-
To ensure that you are still authenticated with the container registry, run this command:
$ oras login uccmpprivatecloud.azurecr.io Username: Token:
-
If you don't know the release, run the following command to list all releases:
oras repo tags uccmpprivatecloud.azurecr.io/releases/aws-configuration
-
To pull the desired version, run this command:
oras pull uccmpprivatecloud.azurecr.io/releases/aws-configuration:2025.13.100
-
To extract the package over the top of the existing configuration, run this command:
tar -xvzf unity-private-cloud-aws-*.tar.gz -C /path/to/asset-solutions-private-cloud
-
In the changelog, compare the changes between the two versions and check for any required changes in configuration.
The changelog is in this directory:
/path/to/asset-solutions-private-cloud/aws/CHANGELOG.md
- If some configurations require changes, update them.
-
Apply the Terraform plan:
$ cd aws/terraform $ make init-us-east-1 $ make apply-us-east-1 Outputs: aws_secretsmanager_secret_config_name = "asset-solutions/configuration" enable_cluster_autoscaler = true enable_external_secrets = true enable_istio = false enable_metrics_server = true environment_name = "dev" TARGET_DIR is empty. Defaulting to ../argocd/us-east-1: Merging helm values files... Copying generated Helm charts and values to target directory: ../argocd/us-east-1 ✅ Successfully generated Helm charts and values. Cleaning up temporary files...
-
To upgrade the helm charts, run this command:
cd aws/terraform make helm-upgrade-us-east-1
- New infrastructures are provisioned.
- New packages are pulled and deployed.