Provider VDC backed by a Supervisor Cluster does not show the blue Kubernetes Icon and default Provider VDC Kubernetes Policy is not created

Products

• VMware Cloud Director

Issue/Introduction

• A vCenter Server 7.0 or later instance enabled for vSphere with VMware Tanzu functionality has been added to VMware Cloud Director.
• A Provider VDC backed by an ESXi cluster which is enabled as a Supervisor Cluster in vSphere has been created in Cloud Director.
• In the Cloud Director Provider UI under Resources > Cloud Resources > Provider VDCs, the Provider VDC does not show the blue Kubernetes icon which would show that it supports Kubernetes.
• No default Provider VDC Kubernetes Policy is present in the Provider VDC under Policies > Kubernetes.
• After performing a Reconnect on a vCenter from Cloud Director the Provider VDC stops showing the blue Kubernetes icon which would show that it supports Kubernetes.
• Provider VDC backed by VKS lost blue K8S icon

Environment

VMware Cloud Director 10.x

Cause

This issue can occur if the user account used by Cloud Director to connect to vCenter has issues collecting details on the Namespaces resource pool created under the ESXi cluster which is enabled as a Supervisor Cluster in vSphere.
Cloud Director can only mark the Provider VDC as supporting Kubernetes if it can see this Namespaces resource pool and store its details in the Cloud Director database.

Resolution

Due to a change in the VMware Tanzu Kubernetes Grid and VMware Tanzu Kubernetes Grid Service architecture in vSphere 8.0.3, VMware Cloud Director supports TKG and TKGS clusters only with vSphere 8.0 Update 2c or earlier. VMware Cloud Director 10.6 Release Notes

The following workaround can be to applied for vSphere 8.0 Updated 2c or earlier:

1. Open the Cloud Director Provider UI as a System Administrator and navigate to Resources > Infrastructure Resources > vCenter Server Instances.
2. Click on the name of the vCenter which backs the Provider VDC to open its details.
3. Under General > vCenter Server Info note the Username used by Cloud Director to connect to vCenter.
4. Open the vSphere UI and navigate to Hosts and Clusters.
5. Expand the ESXi cluster which is enabled as a Supervisor Cluster that backs the Provider VDC.
6. Confirm that a Namespaces resource pool is present.
7. Navigate to Administration > Single Sign On > Users and Groups > Groups and open the Administrators group.
8. Click Add Members and add the user that Cloud Director uses to connect to vCenter as a member, this is the Username found in step 3. above.
9. Return to the Cloud Director Provider UI the Resources > Infrastructure Resources > vCenter Server Instances page.
10. Click the radio button beside the vCenter which backs the Provider VDC and click Reconnect to reset the connection.
11. After the reconnect operation completes wait 3-5 minutes for Cloud Director to resync the vCenter inventory.
12. Navigate to Resources > Cloud Resources > Provider VDCs and confirm that the Provider VDC now shows the blue Kubernetes icon.
13. Click the name of the Provider VDC and confirm that a default Provider VDC Kubernetes Policy is present under Policies > Kubernetes.