文档

​
​

Development

User Acquisition

Monetization

工业

Self-Hosted Deployment

Amazon Web Services

Microsoft Azure

On premises

vpctl

Self-Hosted Deployment

此页面不支持所选语言。
​
​
Self-Hosted Deployment
  • Overview
  • Amazon Web Services
    • Release notes
    • Installation
    • Maintenance
      • Autoscaling of pods
      • Backup and recovery
      • Test and troubleshoot your solution
      • Health checks
      • Rotate secrets
      • Upgrade
      • Migrate Mini-USF to v2
      • Move Unity Licensing Server storage to EBS
      • Migrate Elasticsearch to the ECK operato
      • Service limits
  • Microsoft Azure
  • On premises
  • Administration
  • Security
  • vpctl
  1. Self-Hosted Deployment (previously called Unity Virtual Private Cloud)
  2. Self-Hosted Deployment in Amazon Web Services
  3. Maintenance

Upgrade your solution

Install a more recent package, apply the required changes in configuration, and upgrade the helm charts
阅读时间2 分钟
最后更新于 1 个月前

警告
The upgrade process extracts configuration files and template files over the top of the existing configuration. The recommended practice is to ensure that the current configuration is committed to source control before any upgrade, so that you can roll back to the previous configuration.
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:
  1. To ensure that you are still authenticated with the container registry, run this command:
    $ oras login uccmpprivatecloud.azurecr.ioUsername: Token:
  2. If you don't know the release, run the following command to list all releases:
    oras repo tags uccmpprivatecloud.azurecr.io/releases/aws-configuration
  3. To pull the desired version, run this command:
    oras pull uccmpprivatecloud.azurecr.io/releases/aws-configuration:2025.13.100
  4. 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
  5. 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
  6. If some configurations require changes, update them.
  7. Apply the Terraform plan:
    $ cd aws/terraform$ make init-us-east-1$ make apply-us-east-1Outputs:aws_secretsmanager_secret_config_name = "asset-solutions/configuration"enable_cluster_autoscaler = trueenable_external_secrets = trueenable_istio = falseenable_metrics_server = trueenvironment_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...
  8. To upgrade the helm charts, run this command:
    cd aws/terraformmake helm-upgrade-us-east-1
The upgrade process results in these changes:
  • New infrastructures are provisioned.
  • New packages are pulled and deployed.

Copyright © 2026 Unity Technologies
法律信息隐私政策CookiesDocumentation Terms of Use请勿出售或分享我的个人信息您的隐私选择(Cookie 设置)

“Unity”、Unity 徽标及其他 Unity 商标是 Unity Technologies 或其附属公司在美国和其他地方的商标或注册商标(此处查看更多信息)。其他名称或品牌是其各自所有者的商标。

为方便起见,一些页面是机器翻译的,可能包含不准确的内容。如有信息不一致的情况,以英文版本为准。


    报告此页面的问题