Tanzu Mission Control (TMC) Supervisor registration fails when attempting to integrate a vSphere Supervisor into TMC via Workload Management.
This issue specifically occurs after an administrator attempts to troubleshoot an initial registration failure by manually deleting the TMC vSphere Namespace (typically named svc-tmc-cXX). Deleting this namespace removes essential underlying Kubernetes components required for successful registration.
The observed symptoms are:
The root cause is the absence of critical Kubernetes resources required for TMC registration, specifically the tmc-agent-installer CronJob.
When the TMC vSphere Namespace is manually deleted by an administrator, the Supervisor's automation (WCP) does not automatically replace all the low-level configuration files and Kubernetes objects needed to restart the registration process from a clean state. The deletion removes the tmc-agent-installer CronJob, which is responsible for populating other necessary configuration files and Custom Resource Definitions (CRDs) required for the TMC agents to deploy and connect successfully. The missing resources leave the Supervisor in an invalid state, causing the Registration URL field to be stuck and uneditable.
Due to the need to manually manipulate core system files on the vSphere Supervisor control plane, which can be disruptive or destructive if performed incorrectly, do not attempt to manually fix this issue.
Contact Support immediately and reference this Knowledge Base article for assistance. Support teams have the necessary tools and procedures to safely repair the Supervisor environment and restore the missing registration components.