Kubernetes Cloud Provider for VMware Cloud Director 1.4 Release Notes

Kubernetes Cloud Provider for VMware Cloud Director 1.4 \| 18 JUL 2023 Check for additions and updates to these release notes.

Kubernetes Cloud Provider for VMware Cloud Director 1.4 | 18 JUL 2023

Check for additions and updates to these release notes.

Documentation

Upgrade Kubernetes Cloud Provider for VMware Cloud Director from version 1.2.x and v1.3.x to v1.4.
It is necessary to perform this workflow as kubectl patch does not work to upgrade to Kubernetes Cloud Provider for VMware Cloud Director version 1.4 from 1.2.x and 1.3.x.

To upgrade Kubernetes Cloud Provider for VMware Cloud Director from version 1.2.x and 1.3.x to 1.4, complete the following steps:
1. Use kubectl delete deployment to delete the Kubernetes Cloud Provider for VMware Cloud Director deployment.
2. Use kubectl apply to create the deployment of Kubernetes Cloud Provider for VMware Cloud Director version 1.4. For the deployment manifest details, see https://raw.githubusercontent.com/vmware/cloud-provider-for-cloud-director/1.4.0/manifests/cloud-director-ccm.yaml.

An IP address is not obtained for LoadBalancer Service if Edge Gateway has IP Spaces.

Kubernetes Cloud Provider for VMware Cloud Director cannot get a free IP address for a LoadBalancer service if it has IP spaces.

Workaround:

Users can specify an IP address to use in spec.loadBalancerIP for the LoadBalancer service.
LoadBalancer Services with the same name in different namespaces can be bound to the same IP address.

This issue occurs in LoadBalancer service names are not unique, for example by including the namespace in the name.

Workaround:

Create a unique name or add the namespace to the LoadBalancer Service name.
Updating service from LoadBalancer to ClusterIP does not clean up all LoadBalancer service CCM resources.

If a DNAT rule is in operation, this can get cleaned up, but the virtual service and pools may remain.

Workaround:

Delete the LoadBalancer service and recreate the service.