Tanzu Mission Control (TMC) Fails to Create New Clusters After VKS Update with Error: " failed to render cluster class template for TKG Service vSphere: invalid argument: no releases in cluster options (invalid argument)”

Products

• VMware Tanzu Mission Control
• VMware vSphere Kubernetes Service

Issue/Introduction

^{After successfully updating the underlying vSphere Kubernetes Service (VKS) environment, users are unable to provision new workload clusters through Tanzu Mission Control (TMC).}

^{Attempts to deploy a new cluster fail during the template rendering stage, displaying the following specific error:}

^{API Error: Failed to get management cluster classes: failed to list cluster class: failed to render clusterclass: &{OrgID:##### ManagementClusterName:##### ProvisionerName:##### Name:builtin-generic-v3.x.x}: failed to render cluster class template for TKG Service vSphere: invalid argument: no releases in cluster options (invalid argument)}

Environment

^{TMC SAAS}

^VKS

Cause

^{The root cause is a synchronization failure between the updated VKS management cluster and the TMC integration layer, specifically the TMC Sync Agent.}

     ^{1. VKS Update: The VKS update changes the underlying configuration and TKR list on the management cluster.}

     ^{2. Stale Sync Agent: The TMC Sync Agent pod, responsible for caching and propagating this information to the TMC service, retains a stale or previous configuration state.}

     ^{3. Failure: Because the agent is not fully synchronized with the updated VKS environment, TMC receives an empty or corrupted list of available releases when attempting to render the               ClusterClass template, resulting in the "no releases in cluster options"}

     ^{4. The management cluster itself is operational; the issue is isolated to the communication bridge provided by the Sync Agent.}

Resolution

^{The resolution is to force a complete resynchronization between the VKS Management Cluster and the TMC service by restarting the Sync Agent pod.}

^{Step 1: Access the Management Supervisor Cluster}

^{Log in to the Supervisor Cluster environment that is registered with Tanzu Mission Control using kubectl with the appropriate kubeconfig file.}

^{Step 2: Identify and Restart the Sync Agent Pod}

^{Restart the Sync Agent deployment to clear its cache and force a fresh synchronization.}

^{# Get the name of the sync agent deployment (Name may vary slightly)}

^{kubectl get deployments -n svc-tmc-c#####}

^{# Restart the deployment (Replace 'sync-agent' with the actual deployment name and namespace)}

^{kubectl rollout restart deployment <sync-agent-deployment-name> -n <svc-tmc-c######>}

^{Step 3: Verify Synchronization Status}

^{Wait approximately 5 to 10 minutes for the Sync Agent pod to restart and for TMC to successfully pull the updated TKR list.}

^{Step 4: Re-test Cluster Creation}

^{Attempt to provision a new cluster via the Tanzu Mission Control interface. The ClusterClass template should now render correctly, displaying the list of available Kubernetes releases.}

Additional Information

^{For documentation on TMC administration and troubleshooting synchronization, refer to the Broadcom documentation:}

^{https://techdocs.broadcom.com/us/en/vmware-tanzu/standalone-components/tanzu-mission-control/saas/tanzu-mission-control-documentation/tanzumc-using-GUID-0A81E446-39F0-44D9-8C73-190307BCDEFB.html}