TMC deployed workload clusters are not visible in Namespaces in vSphere client
search cancel

TMC deployed workload clusters are not visible in Namespaces in vSphere client

book

Article ID: 393212

calendar_today

Updated On:

Products

Tanzu Kubernetes Runtime Tanzu Mission Control VMware vCenter Server 8.0

Issue/Introduction

  • A new workload cluster is created from Tanzu Mission Control

  • When running:

    kubectl get tanzukubernetescluster -A

    the new cluster is not visible

  • When viewing the Tanzu Kubernetes cluster in the vSphere UI, a newly deployed cluster shows as N/A for phase

Environment

TMC
vSphere 8

Cause

This is due to the change of moving from v1alpha3 to v1beta1 where tanzukubernetescluster is being retired. New clusters are deployed with cluster so the previous API's are not applicable anymore. 

Resolution

This is working as designed. Eventually tanzukubernetescluster will be retired, but this is not an option with Tanzu Mission Control currently. When this option is available Tanzu Mission Control will publish further information.

Additional Information

Powered by Wolken Software