To resolve this issue use Cluster API Provider for VMware Cloud Director (CAPVCD) v1.1.1 or later when creating Kubernetes clusters in Container Service Extension.
CAPVCD v1.1.1 introduced changes to resolve the issue as outlined in the release notes here:
Cluster API Provider for VMware Cloud Director Release v1.1.1
To ensure that Container Service Extension is using CAPVCD v1.1.1 or later when creating Kubernetes clusters take the following steps:
- Log into the Cloud Director Provider portal as a System Administration.
- Open the Kubernetes Container Clusters plugin and open the CSE Management, Server Details tab.
- Under Component Versions confirm that CAPVCD is set to v1.1.1 or higher.
- To change the CAPVCD version follow the steps outlined in the Container Server Extension documentation:
- Log into the Cloud Director Provider portal as a System Administration.
- Open the Kubernetes Container Clusters plugin and open the CSE Management, Server Details tab.
- Click Update Server, select the Update Configuration option, and click Next.
- Under CSE Server Components increase the CAPVCD Version to the desired supported version, for example by typing v1.1.1.
- Click Submit Changes to apply the change and click Back to return to Server Details.
- Restart the existing VMware Cloud Director Container Service Extension Server vApp containing the Container Service Extension servers to apply the updated configuration.
- Deploy a new Kubernetes cluster and confirm that it is using CAPVCD v1.1.1 by opening it in the Kubernetes Container Clusters plugin and viewing the Overview, Kubernernetes Resources section.