TKG kind:Cluster object unavailable after onboarding under TSM
search cancel

TKG kind:Cluster object unavailable after onboarding under TSM

book

Article ID: 386804

calendar_today

Updated On:

Products

VMware Tanzu Kubernetes Grid Management VMware Tanzu Service Mesh

Issue/Introduction

Workload Cluster is running within a Tanzu Service Mesh (TSM) environment; however, the corresponding cluster object is not displayed, preventing the administrator from editing the target cluster object.

# kubectl get cluster -A
NAMESPACE           NAME      AGE
vmware-system-tsm   cluster   152d

# kubectl edit cluster test-cluster-1
Error from server (NotFound): clusters.client.cluster.tsm.tanzu.vmware.com "test-cluster-1" not found

# tanzu cluster list -A
NAME            NAMESPACE   STATUS   CONTROLPLANE  WORKERS  KUBERNETES
test-cluster-1  default     running  3/3           3/3      v1.28.7+vmware.1

 

Environment

Tanzu Kubernetes Grid v2.5.x under Tanzu Service Mesh (TSM)

Cause

Another KIND:cluster is added by TSM.

# kubectl api-resources | grep -E 'NAME|clusters'
NAME      SHORTNAMES    APIVERSION                               NAMESPACED   KIND
clusters  cluster       client.cluster.tsm.tanzu.vmware.com/v1   true         Cluster
clusters  cl            cluster.x-k8s.io/v1beta1                 true         Cluster 

Resolution

Use SHORTNAMES "cl".

  • kubectl get cl
  • kubectl edit cl $CLUSTER_NAME