TMC Self-Managed Clusters Remain Stuck in “Upgrading” State After Successful Cluster Upgrade

Products

• VMware Tanzu Mission Control - SM

Issue/Introduction

After completing a cluster upgrade, multiple clusters in a Tanzu Mission Control Self-Managed (TMC-SM) environment remain stuck in the “Upgrading” state within the TMC UI.

Although the upgrade status does not complete in TMC-SM, the clusters themselves are fully functional. Control plane components, worker nodes, workloads, and networking continue to operate normally. This behavior indicates an issue with the TMC-SM upgrade workflow rather than a failure at the cluster level.

Cause

This issue occurs due to a version incompatibility between TMC Self-Managed 1.4.2 and vSphere Kubernetes Service (VKS) 3.5.

TMC-SM 1.4.2 does not support managing the lifecycle of VKS 3.5 clusters. As a result, TMC is unable to complete the upgrade workflow, causing the cluster status to remain stuck in the “Upgrading” state even though the cluster upgrade itself has completed successfully.

Resolution

Upgrade Tanzu Mission Control Self-Managed to version 1.4.3.

TMC-SM 1.4.3 introduces support for managing VKS 3.5 clusters. After upgrading to this version, the upgrade workflows complete successfully and the affected clusters transition out of the “Upgrading” state.

Refer to the TMC Self-Managed 1.4 release notes for compatibility details: Updates for v1.4.3