VMware Cloud Director Container Service Extension 3.1.4 Release Notes

VMware Cloud Director Container Service Extension 3.1.4 \| 22 JUL 2022 Check for additions and updates to these release notes.

VMware Cloud Director Container Service Extension 3.1.4 | 22 JUL 2022

Check for additions and updates to these release notes.

Product Support Notice

Native offering for VMware Cloud Director Container Service Extension 3.1.x will reach end of general support on February 1st, 2023.
Native Kubernetes Templates will no longer be updated. It is recommended to use the Tanzu Kubernetes Grid offering. For more information, see Template Announcements.

Support for Ubuntu 20.04 Kubernetes OVAs from VMware Tanzu Kubernetes Grid Versions 1.5.3 and Kubernetes version 1.22.
Support for Ubuntu 20.04 Kubernetes OVAs from VMware Tanzu Kubernetes Grid Versions 1.5.4 and Kubernetes version 1.22.
Interoperability with VMware Cloud Director 10.4.0 GA. For more information, refer to the compatibility matrix.
Support for RDE 2.0 request payloads in which RDE 2.1 clusters are created.
Bug fix to support Ubuntu 20.04 native templates.
Bug fix to mitigate VM reboot issue.
Bug fix for TKG cluster creation failure with missing right error.

Native cluster creation fails for Ubuntu 20 templates

This failure is due to a race condition in faster customer environment infrastructures.

Resolution

This issue is fixed in VMware Cloud Director Container Service Extension 3.1.4.
TKG Cluster creation fails with “ACCESS_TO_RESOURCE_IS_FORBIDDEN due to lack of [VAPP_VIEW] right” even though this right is not missing

This issue is due to a security context being wiped out.

Resolution

This issue is fixed in VMware Cloud Director Container Service Extension 3.1.4.
TKG cluster creation intermittently fails due to a VM reboot

This occurs due to a cloud-init script execution error when a VM is rebooted, and this issue may be encountered as a VM postcustomization timeout.

Resolution

This issue is fixed in VMware Cloud Director Container Service Extension 3.1.4.

TKG cluster resize fails after 1 day of cluster creation

This issue in resizing the TKG cluster occurs because the token to join a cluster has expired. The issue may also be encountered when trying to resize a TKG cluster that was upgraded to VMware Cloud DIrector Container Service Extension 3.1.3 or 3.1.4.

Resolution

This issue is fixed in VMware Cloud Director Container Service Extension 3.1.3 for newly created clusters.
For clusters created before VMware Cloud Director Container Service Extension 3.1.3, the following workaround is to create a new token and update the RDE:
1. Run the following in the control plane node: kubeadm token create --print-join-command --ttl 0
2. In Postman, GET the entity at: https:///cloudapi/1.0.0/entities/. The entity ID can be retrieved from the cluster info page or via vcd cse cluster info
3. Copy the response body in Step 2 and replace the kubeadm join ... command with the output in Step 1 to form the request body.
4. Do a PUT on the same URL as in Step 2 with Content-Type: application/json and with the request body formed in Step 3.
5. You can perform the resize operation. If the resize failed, then the operation may be triggered again after Step 4 due to the RDE update triggering the behavior.