VMware Tanzu Kubernetes Grid Service Release Notes

VMware Tanzu Kubernetes Grid Service 3 Check for additions and updates to these release notes.

VMware Tanzu Kubernetes Grid Service 3

Check for additions and updates to these release notes.

About the TKG Service

VMware TKG Service provides components for provisioning and managing the lifecycle of Kubernetes clusters in the vSphere IaaS control plane environment.

These release notes provide details for each TKG Service release. Refer to the documentation for usage information.

Release Snapshot

TKG Service 3.1 is generally available for use with vSphere 8 Update 3.

Name	Release Date
TKG Service 3.1	7/8/2024

What's New

TKG Service 3.1 includes the following new features:

Updates TKG Service components to support the TKr v1.30 release
Improvements to Kubectl and Tanzu CLI to identify legacy TKRs (refer to the documentation for more information about TKr formats)

Known Issues

After restoring Supervisor to a backup taken with TKG Service 3.0, the TKG Service version displayed in the web interface is 3.1.

Post upgrading to TKG Core Service 3.1.0, the restore to the backup taken with TKG Core Service 3.0.0 is not supported.

Workaround: None

Fixed Issues

One of the OSImages might be missing from non-legacy TKr >= v1.28 if vSphere is upgraded from 7.x to 8.x.

Description: TKr >= v1.28 will have all required OSImages present when vSphere is upgraded from 7.x to 8.x.
TKr controller should not recommend TKr for vSphere 7.x as upgrade for a cluster using TKr for vSphere 8.x

The Tanzu CLI was listing legacy TKrs as options for upgrading a classy cluster when running 'tanzu cluster upgrade'.
Block upgrades to TKG 1.0 TKr for Classy clusters

You cannot upgrade to TKr for vSphere 7.x using a classy cluster.

TKG Service 3.0

Release Snapshot
What's New
Known Issues

Release Snapshot

TKG Service 3.0 is generally available for use with vSphere 8 Update 3.

Name	Release Date
TKG Service 3.0	6/25/2024

What's New

Prior to vSphere 8.0 Update 3, TKG Service components responsible for the lifecycle of TKG clusters were delivered as part of vCenter releases. Starting with the vSphere 8.0 Update 3 release, TKG Service components are decoupled from vCenter and packaged as a Supervisor service which can be updated and managed independent of vCenter releases.

With this flexibility, TKG Service releases are delivered two ways: independent and bundled with vCenter. When released independently, you can register and upgrade the TKG Service separate from upgrading vCenter. When bundled with vCenter, after upgrading vCenter the TKG Service is automatically registered for upgrade. Refer to the TKG Service documentation for details.

TKG Service 3.0 is the first release of the decoupled TKG Service. It is available as part of the vSphere 8.0 Update 3 release. The system automatically installs TKG Service 3.0 when you install or upgrade to the vSphere IaaS control plane component versions listed in the table. Once installed, you can upgrade to subsequent TKG Service releases, such as TKG Service 3.1, 3.2, and so on.

Component	Required Version
vCenter Server	8.0 Update 3 (8.0.3)
vSphere Namespaces	0.1.9
Supervisor	1.28.3, 1.27.5, 1.26.8
TKr	v1.25.7 or later for vSphere 8.x

Known Issues

TKG Service 3.0 has the following known issues.

One of the OSImages might be missing from non-legacy TKr >= v1.28 if vSphere is upgraded from 7.x to 8.x.
Description: If, after upgrading from vSphere 7.x to 8.x, you list available TKrs for vSphere 8.x, you may not see both OSImages. For example, the following command returns only one OSImage when you should see two (must be run from the vSphere Namespace where a TKG cluster is provisioned):
```
kubectl get osimage -A | grep 1.28
```
Workaround: Delete any non-legacy TKr >=v1.28 and wait for it to be re-created which will happen after approximately 10 minutes. The recreated TKr will have both the Photon and Ubuntu images, and the OSImage Kuberentes resources will also be created for both Photon and Ubuntu.

If you cannot wait for the TKr to be recreated, you can delete the active vmware-system-tkg-controller-manager pod which will recreate the TKr.
Supervisor backup taken via TMC with TKG Service 3.0 installed does not restore after 8 hours due to token expiration.

Description: On a TMC-managed cluster, after restoring a Supervisor from backup taken with TKG Service 3.0, the TMC agent is in a CrashLoopBackoff state.

Workaround: Reregister the cluster with TMC.