W-23544596-vpc-peering-upgrade-kt

[kevintroller]

Summary

• Documents that the VPC upgrade tool migrates VPN and TGW only; VPC peering is not deleted if an upgrade completes.
• Leftover peering stays on the CloudHub VPC. CloudHub apps can keep using it. CloudHub 2.0 apps in the new private space can't.
• How-to steps (migrate off peering; what to do with leftover peering) are source comments only until CloudHub engineering confirms them.

GUS: W-23544596

Request vs. draft

Ticket request	Status
Confirm VPC peering is not deleted after a CH1 → CH2 private space upgrade	Added to vpc-upgrade.adoc (overview)
Upgrade migrates VPN and TGW only; peering is unaffected	Added next to the existing TGW/VPN transfer sentence
Eligibility: migrate to TGW or VPN before upgrading	Already documented — not duplicated
Customer-facing steps to migrate off peering / clean up leftover peering	Placeholder comments only — waiting on engineering

Sources

• GUS W-23544596 — docs request
• GUS W-23543602 — investigation, Closed - Doc/Usability; leftover peering reproduced
• Slack #ms-support-swarm-si — swarm (Richard: peering remains, not connected to CH2 subnets; Randall confirmed CH2 apps can't use it)
• Slack #cloudhub-doc-review — open questions

Test plan

• Review the leftover-peering paragraph on vpc-upgrade for accuracy
• Confirm placeholder comments should stay until CloudHub answers the #cloudhub-doc-review questions
• Do not publish how-to steps until engineering confirms them