기술 자료

​
​

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분
최근 업데이트: 한 달 전

경고
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
법률 정보개인정보 처리방침쿠키Documentation Terms of Use개인 정보 판매 또는 공유 금지개인정보 보호 선택(쿠키 설정)

'Unity', Unity 로고 및 기타 Unity 상표는 미국 및 기타 지역 내 Unity Technologies 또는 그 계열사의 상표 또는 등록상표입니다(자세한 내용은 여기에서 확인하세요). 기타 명칭 또는 브랜드는 해당 소유자의 상표입니다.

일부 페이지는 편의를 위해 기계 번역되었으며 부정확한 내용이 있을 수 있습니다. 정보가 상충되는 경우, 영어 버전을 우선으로 참조하세요.


    이 페이지의 문제 보고