Upgrade your solution
Pull a more recent release, sync updated images, and redeploy using the vpctl tool
読み終わるまでの所要時間 2 分最終更新 1日前
注意
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 key in your file to the desired version:
releaseVersionmanifest.yamlreleaseVersion: 0.13.0
注
Each release declares the minimum required version of the vpctl tool in the file. If your vpctl tool is too old, the and commands stop with an upgrade message. Reinstall the vpctl tool to a compatible version before continuing.
compatibility.yamlrelease generatesecret generate2. Pull the new release
Run this command:
vpctl release pull --clean-output
3. 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 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.
manifest.yaml注意
If the changelog calls out a breaking change with required migration steps, complete them before continuing with the rest of this guide. For example, upgrading to release replaces RustFS with Garage and requires you to either drain the RustFS persistent volumes or mirror their contents to Garage before you run . Refer to the On-Premises release notes for the full procedure that applies to your target release.
0.13.0vpctl release deploy4. 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 flag skips images that are already in your registry, and removes local images after each push.
--skip-existing--cleanupIf your manifest opts in to the 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:
deployment.helmChartMode: remotevpctl artifact sync charts
5. 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 flag. The process writes back the persisted values to the import file and reuses them on subsequent runs without regeneration:
--persistvpctl secret generate --import secrets.import.yaml --use-defaults --persist
6. 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.13.0"git pushvpctl release deploy --format argocd
7. 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.