ACTION NEEDED: Tanzu Mission Control Domain Name Change

Products

• VMware Tanzu Mission Control
• Tanzu Mission Control

Issue/Introduction

Update 

Based on additional testing, we’re publishing an addendum to the original KB article. 

The action item to update network rules mentioned below should be performed immediately if your managed clusters are behind a firewall.

The action item to update your local image registry mentioned below should be performed immediately if you are using the local image registry feature.

Overview 

As part of VMware’s integration into Broadcom, we will be transitioning the domain name used to access Tanzu Mission Control. Today to access Tanzu Mission Control customers use <customer-prefix>.tmc.cloud.vmware.com. Starting Nov 22, 2024, you should start preparing to migrate to <customer-prefix>.tmc.tanzu.broadcom.com. To avoid disruption, please perform steps outlined under “Action Items” below as applicable to your environment to migrate to the new endpoint.  

The Tanzu backend migration will commence on Nov 22, 2024, at 4:00 pm Pacific time and is expected to be completed by 9:00 pm. During this time, you will not be able to access Tanzu Mission Control via UI, CLI, or API to perform cluster management tasks. Note that cluster and associated application workload availability will NOT be disrupted during this time.

Resolution

Action Items

To prepare for this migration and ensure Tanzu Mission Control is accessible with the new domain, please complete the following steps as applicable to your environment to avoid service disruption.

Immediate Action Required

The following changes should be applied as soon as possible as applicable to your environment: 

• Update Network Rules

• If your managed clusters are behind a firewall or a proxy server, update network rules to permit traffic from the Broadcom domain

• • Update your network allow list to include *.tmc.tanzu.broadcom.com  

• Local Image Registry

• If you are using the local image registry feature, you must sync the latest images into your registry after the migration is completed
• Follow related steps in this document as required. 

Action Required Before January 31, 2025

The following changes must be performed prior to January 31, 2025 or if you experience related issues as applicable to your environment:

Automation

• Upgrade Tanzu CLI to the latest version - If you are using Tanzu CLI to manage your clusters, upgrade to the latest version. Tanzu CLI  v1.5.x and later will dynamically pull the new domain information ensuring continued access post migration. Instructions for installing and updating Tanzu CLI are available here. If you are unable to update your Tanzu CLI, you will need to update the tmc context used.  
• Update TMC Terraform provider API endpoint - If you are using the TMC Terraform provider to manage your clusters, update the Terraform provider API endpoint to reference your new Tanzu Mission Control organization URL. 
• Direct TMC API consumption - If you are interacting with the TMC API directly, ensure you have updated the endpoint in any custom code interacting with the Tanzu Mission Control API. 

TKG supervisor registration URL

• Customers may encounter issues when registering TKG supervisor clusters after the endpoint change
• If you receive an error similar to “registration link domain name verification failed”, follow the steps to update the AgentConfig CR to include the Broadcom domain in this document 

If you require assistance, please work with your VMware Tanzu account team or contact the support desk.