VMware Tanzu Platform for Kubernetes Release Notes

VMware Tanzu Platform for Kubernetes simplifies application deployment by providing a set of building blocks. These release notes provide information about new updates in Tanzu Platform for Kubernetes. For information about getting started and how to use Tanzu Platform for Kubernetes, see Creating and Managing Applications with Tanzu Platform for Kubernetes.

Cluster types supported for lifecycle management

Tanzu Platform for Kubernetes provides lifecycle management of the following Kubernetes cluster types:

Cluster type	Details
Tanzu Kubernetes Grid Service clusters running in vSphere with Tanzu	vSphere 8.0 U2c and vSphere 8.0 U3 TKr: 1.28.8 and 1.27.11 Supervisor: 1.27, 1.26, and 1.25 Load balancer: Avi, HA Proxy CNI: Antrea, Calico
AWS EKS clusters	Kubernetes versions 1.29, 1.28, and 1.27

June 2024

What’s new

New and improved features include:

Lifecycle management support for Tanzu Kubernetes Grid service clusters running in vSphere with Tanzu. You can now use Tanzu Platform for Kubernetes to connect to a Supervisor in vSphere with Tanzu and manage the full lifecycle of its workload clusters.
Added the ability to see the scheduling status of a space to the Tanzu Platform for Kubernetes hub. For more information, see monitoring Space readiness
Added the ability to scale an application by managing the number of replicas of the deployed application, as well as increasing or decreasing the CPU and Memory for each replica. More more information, see scaling applications.
Added the ability to manage egress rules on a per space basis rather than at the profile level to enable more granular control of egress rules. See managing egress rules for more information.
Added the ability to create, bind, unbind, and delete services in the Tanzu Platform for Kubernetes hub. For more information, see Creating, binding, and unbinding services.
Added the ability to Promote resources from builds and between Spaces.
Added the ability to add and override environment variables at runtime to an application and handle sensitive data. See Configure secret runtime environment variables for more information.
Added the ability to create, bind, unbind, and delete services in the Tanzu Platform for Kubernetes hub. For more information, see Creating, binding, and unbinding services.
Added the ability to delete a deployed application from a Space.
Added support for VMware vSphere 8.0 Update 3.

Resolved issues

Resolved an issue that prevented the ACME Protocol from being with the cert-manager Capability.

Known issues

When using Tanzu Platform hub to install a Capability to a cluster group, the Capability is pinned to a specific version. This causes the Capability to fail to install when Tanzu Platform for Kubernetes is updated and can cause Spaces to become unschedulable.

Workaround: See Removing pinned Capability version for custom cluster groups.

Breaking Changes

The Egress Capability has been removed as a dependency of the TCS package. The Egress Capability must now be added explicitly as a Capability on a cluster group. This was added to the Tanzu provided run cluster group as part of the release. However, user-created cluster groups will need to have the Egress Capability added explicitly to ensure that Spaces requiring the Egress Capability can be scheduled. See Add capabilities to the cluster group for your run environments for information on how to add a Capability to a user-created cluster group.

May 2024

What’s new

This is the first release of VMware Tanzu Platform for Kubernetes. For information about getting started and how to use Tanzu Platform for Kubernetes, see Creating and Managing Applications with Tanzu Platform for Kubernetes.

Known issues

An organization is currently limited to a maximum of 40 projects created within it.
The telemetry data of an application deployed to a space may experience lag that results in network topologies and related Kubernetes resource not being displayed in the Tanzu Platform for Kubernetes hub deployed applications
You might see duplicate cluster entries on the Kubernetes Management page (under Setup & Configuration). This issue stems from duplicate cluster entries in the Tanzu Platform database, one record from Tanzu cluster lifecycle management, and another from inventory that Tanzu Platform retrieved from your cloud account. You can safely ignore these duplicate cluster entries and their associated status. To manage your Kubernetes clusters, navigate to Infrastructure > Kubernetes Clusters.
When an EKS lifecycle management credential is in the created or validating status/state, and a user requests it to be deleted, the credential starts the deletion process (status: deleting), but is unable to complete and return to the previous state. To avoid this situation, wait to delete a credential until after it becomes validated. Validation typically takes only a few minutes.
The cross-cluster Capability can prevent ingress routing from working correctly and should not be included in a Profile as any deployed application to a Space will not be accessible.
When a Space deletion request is initiated, if the GSLB DNS records cannot be cleaned up successfully, the Space controller will retry the cleanup operation for several minutes. During this time, the Space appears to be taking longer than usual to delete.

This could indicate an issue with your AWS GSLB Credential or associated IAM policies. After several minutes, the Space controller will stop retrying the cleanup and will delete the Space resources in Tanzu Platform. When this happens, make sure you check the Route53 zone originally used by that Space for any left over records and manually clean them up.

Breaking changes

In the latest release of VMware Tanzu Platform for Kubernetes, the FluxCD Source Controller and FluxCD Helm Controller capabilities have been updated to use FluxCD v2.3. As a result, all related capabilities now have updated API groups and versions:

HelmRelease - from helm.toolkit.fluxcd.io/v2beta1 to helm.toolkit.fluxcd.io/v2
HelmChart - from source.toolkit.fluxcd.io/v1beta2 to source.toolkit.fluxcd.io/v1
HelmRepository - from source.toolkit.fluxcd.io/v1beta2 to source.toolkit.fluxcd.io/v1