Kubernetes Cloud Provider for VMware Cloud Director 1.6 Release Notes

Kubernetes Cloud Provider for VMware Cloud Director 1.6 | 18 JAN 2024 Kubernetes Cloud Provider for VMware Cloud Director 1.6.1 | 31 JUL 2024 Check for additions and updates to these release notes.

What's New July 2024

• Added deployment support for Load Balancers against Edge Gateways with multiple uplink connections.

• Added deployment support for Load Balancers against Edge Gateways that belong to data center group.

What's New January 2024

• Added support for Gateways that use IP spaces. For more information, see Supporting Gateways that use IP Spaces. To avail of this feature successfully, it is necessary to use Kubernetes Cloud Provider for VMware Cloud Director 1.6, and Kubernetes Cluster API Provider for VMware Cloud Director 1.3.0.

• Upgraded VMware Cloud Director API version used by Kubernetes Cloud Provider for VMware Cloud Director from 36.0 to 37.2.

• golang.org/x/crypto upgraded from 0.14.0 to 0.17.0.

Documentation

To access the full set of product documentation, go to Kubernetes Cloud Provider for VMware Cloud Director Documentation.

Upgrade

• Upgrade Kubernetes Cloud Provider for VMware Cloud Director from 1.6 to 1.6.1

  To upgrade Kubernetes Cloud Provider for VMware Cloud Director from 1.6 to 1.6.1, perform the following command in kubectl.

  kubectl patch deployment -n kube-system vmware-cloud-director-ccm -p '{"spec": {"template": {"spec": {"containers": [{"name": "vmware-cloud-director-ccm", "image": "projects.registry.vmware.com/vmware-cloud-director/cloud-provider-for-cloud-director:1.6.1"}]}}}}'

• Upgrade Kubernetes Cloud Provider for VMware Cloud Director from 1.5.x to 1.6

  To upgrade Kubernetes Cloud Provider for VMware Cloud Director from 1.5.x to 1.6, perform the following command in kubectl.

  kubectl patch deployment -n kube-system vmware-cloud-director-ccm -p '{"spec": {"template": {"spec": {"containers": [{"name": "vmware-cloud-director-ccm", "image": "projects.registry.vmware.com/vmware-cloud-director/cloud-provider-for-cloud-director:1.6.0"}]}}}}'

• Upgrade Kubernetes Cloud Provider for VMware Cloud Director from 1.2.x and 1.3.x to 1.6.

  To upgrade Kubernetes Cloud Provider for VMware Cloud Director from 1.2.x and 1.3.x to 1.6, 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.6. For the deployment manifest details, see raw.githubusercontent.com/vmware/cloud-provider-for-cloud-director/1.6.0/manifests/cloud-director-ccm.yaml.

Known Issues

• 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.