Upgrade your solution

Pull a more recent release, sync updated images, and redeploy using the vpctl tool

읽는 시간 3분

최근 업데이트: 8일 전

경고

The upgrade process generates new configuration files and charts. Before you upgrade, commit your current configuration to source control so that you can roll back to the previous configuration if necessary.

The upgrade process uses the vpctl tool to pull a more recent release and redeploy the solution.

To upgrade your solution, complete these steps:

1. Update the manifest version

Update the

releaseVersion

key in your

manifest.yaml

file to the desired version:


releaseVersion: 0.16.0

참고

Each release declares the minimum required version of the vpctl tool in the

compatibility.yaml

file. If your vpctl tool is too old, the

release generate

and

secret generate

commands stop with an upgrade message. Reinstall the vpctl tool to a compatible version before continuing.

2. Validate the cluster

A release can raise the minimum Kubernetes version or add a requirement that your cluster didn't need before. To check that the cluster still meets the deployment prerequisites:


vpctl cluster check

Resolve every failure before you continue.

The command reads from the cluster and doesn't change it. For the full list of checks, refer to vpctl cluster commands.

The command requires vpctl 0.13.0 or newer.

3. Pull the new release

Run this command:


vpctl release pull --clean-output

4. Review the changelog

In the extracted release, compare the changes between the two versions and check for any required changes in configuration:


cat extracted-release/CHANGELOG.md

If you need to change any configuration, update your

manifest.yaml

file. For details about manifest fields and examples, see the Manifest reference. For a history of vpctl command changes, including new flags and breaking changes, see the vpctl Changelog.

경고

If the changelog calls out a breaking change or an action required for existing deployments, complete it before you continue with the rest of this guide. For example, upgrading to release

0.16.0

requires you to add the

basic

client scope to three Keycloak clients by hand, because Keycloak skips the realm import on a realm that already exists. Refer to the On-Premises release notes for the full procedure that applies to your target release.

5. Sync the updated artifacts

Authenticate to both registries, then sync Docker images and ORAS artifacts to your private registry:


docker login uccmpprivatecloud.azurecr.iodocker login <your-registry-url>vpctl artifact sync preflightvpctl artifact sync images --skip-existing --cleanupvpctl artifact sync oras

The

--skip-existing

flag skips images that are already in your registry, and

--cleanup

removes local images after each push.

If your manifest opts in to the

deployment.helmChartMode: remote

preview, also mirror the OCI Helm charts that are published to the Unity registry. Not all charts are available yet, so this command syncs only the charts that are published so far:


vpctl artifact sync charts

6. Regenerate and deploy the secrets

If the new release introduces new secrets, regenerate the secrets:


vpctl secret generate --import secrets.import.yaml --use-defaultsvpctl secret deploy

To preserve the previously generated values across upgrades, add the

--persist

flag with an explicit file path. The process writes the generated values back to that file and reuses them on subsequent runs without regeneration:


vpctl secret generate --import secrets.import.yaml --use-defaults --persist secrets.import.yaml

7. Regenerate and deploy the charts

Helm deployment


vpctl release generate --clean-outputvpctl release deploy --dry-runvpctl release deploy

ArgoCD deployment


vpctl release generate --format argocd --clean-outputgit add generated-charts/git commit -m "Upgrade to release v0.16.0"git pushvpctl release deploy --format argocd

8. Verify the upgrade

Check that all pods are running:


kubectl get pods --all-namespaces --watch

Ensure that all pods eventually move to the Running state. If a pod isn't running, describe it and check its logs to find the issue.

The upgrade process results in these changes:

Updated container images are deployed.
New or modified Helm charts are applied.
Configuration changes from the new release take effect.

기술 자료

Development

User Acquisition

Monetization

산업 분야