In a Tanzu Mission Control Self-Managed (TMC-SM) environment, a Supervisor cluster reports health as Unknown state indefinitely after a re-registration attempt.
Additional symptoms include:
AgentInstall is deleted using the command "kubectl delete agentinstall"Manual deletion of the AgentInstall Custom Resource (CR) fails to fully uninstall components because the TMC Cluster Agent is a Managed Resource governed by a declarative reconciliation loop. Directly deleting the AgentInstall CR via kubectl delete removes the configuration object but does not trigger the proper, orchestrated cleanup routines by the TMC controller/agent.
To resolve this, you must perform a clean uninstallation of the existing agents using the TMC agent uninstaller before attempting a new registration.
uninstall-agents.yaml:apiVersion: installers.tmc.cloud.vmware.com/v1alpha1
kind: AgentInstall
metadata:
name: tmc-agent-installer-config
namespace: TMC-NAMESPACE
spec:
operation: UNINSTALLApply the configuration to trigger the removal with kubectl apply -f uninstall-agents.yaml
Verify that the agent pods and resources have been removed from the namespace with kubectl get all -n TMC-NAMESPACE
Source: Manually Remove the Cluster Agent from a Supervisor Running in vSphere
For detailed steps, refer to: Register a Management Cluster with Tanzu Mission Control