Skip to content

Commit

Permalink
W-17238022-VPCrelease-dm
Browse files Browse the repository at this point in the history
  • Loading branch information
dmerlob committed Nov 14, 2024
1 parent 4e2ef17 commit d264c50
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions cloudhub/modules/ROOT/pages/vpc-upgrade.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,9 @@ After you provision the private space, the *Cancel Upgrade* button no longer sho

After you complete the upgrade, the private space is fully provisioned and you can start deploying applications to it.

[NOTE]
When deploying new CloudHub 2.0 application, don't use CloudHub default domain as using CloudHub default domains can lead to issues such as potential traffic outages.

You can start migrating your applications individually by creating new versions in the CloudHub 2.0 private space and then deleting the corresponding application in the CloudHub VPC. After migrating all your applications, delete your old VPC and any attached dedicated load balancers on CloudHub.

During the migration, you can continue to deploy and manage applications in your VPC to maintain business continuity. After the upgrade, your CloudHub dedicated VPC is locked for any changes to the infrastructure, including environment or business group associations, network connections, and internal DNS, to prevent configuration drift. Make all changes in the newly created private space instead. Any configuration changes carried over to the CloudHub 2.0 private space are applied to the CloudHub VPC during the upgrade.
Expand Down

0 comments on commit d264c50

Please sign in to comment.