vSphere Tanzu Supervisor Cluster showing Health and Status Unknown in Tanzu Mission Control SaaS UI (Administration - Management cluster menu)
search cancel

vSphere Tanzu Supervisor Cluster showing Health and Status Unknown in Tanzu Mission Control SaaS UI (Administration - Management cluster menu)

book

Article ID: 399088

calendar_today

Updated On:

Products

VMware Tanzu Mission Control

Issue/Introduction

In the TMC SaaS UI when viewing the Administration - Management cluster menu, the registered Supervisor Cluster has Health and Status of Unknown.

The component health controller-manager and scheduler were showing down.

In the vCenter the Supervisor - TMC menu is showing the registration as successful.

From the Supervisor Cluster context running kubectl get pods -n <svc-tmc-cX> where <svc-tmc-cX> is the TMC namespace shows that agent-updater , agent-installer, extension-updater, extension-installer and tmc-agent-installer but no more.

Environment

Tanzu Mission Control SaaS

vSphere Kubernetes Service

Cause

Supervisor registration with TMC SaaS while reporting as complete did not complete successfully
The registration URL had expired and a new registration URL was required to reregister the Supervisor cluster with TMC SaaS.

Resolution

Note - do not alter or delete any resources associated to TMC SaaS ie under the svc-tmc-cX namespace, for example do not delete the svc-tmc-cX namespace from the Supervisor cluster.

Please reach out to support for help with below steps for reregistering the Supervisor Cluster in TMC SaaS.

They will take you through the below procedure.

 - Remove the AgentInstall for TMC
 - Uninstall the AgentInstall for TMC
 - Check the AgentConfig yaml has correct certificate and pull / update AgentConfig yaml if an issue
 - Sync with Engineering to obtain a new registration URL for Supervisor reregistration in TMC and update the AgentInstall yaml
 - Reapply the AgentConfig
 - Reregister the Supervisor with TMC
 - Reapply the AgentInstall
 - Monitor TMC pods and UI until Health and Status change from Unknown to Healthy.

After completion of this the Supervisor cluster should be of Status Healthy.