Tanzu Kubernetes Releases

This topic explains Tanzu Kubernetes releases (TKrs), and how Tanzu Kubernetes Grid uses them to deploy clusters running specific Kubernetes versions on cluster nodes with different operating systems.

See Deploy Workload Clusters with Different Kubernetes Versions for how to manage TKrs and use them to deploy clusters.

Tanzu Kubernetes Releases

Tanzu Kubernetes Grid manages Kubernetes versions and updates the versions that it can run by using custom resources definition (CRD) objects called Tanzu Kubernetes releases (TKrs). A TKr includes components such as Antrea and Contour that can be deployed in Tanzu Kubernetes Grid cluster.

A TKr controller periodically polls a public registry for new Kubernetes version BoM files. When it detects a new version, it downloads the BoM and creates a corresponding TKr. The controller then saves the new BoM and TKr in the management cluster, as a ConfigMap and custom resource, respectively.

The tanzu CLI queries the management cluster to list available Kubernetes versions. When the CLI needs to create a new cluster, it downloads the TKr and BoM, uses the TKr to create the cluster, and saves the BoM to the local ~/.config/tanzu/tkg/bom directory.

Tanzu Kubernetes Releases and Component Versions

The components’ version included in a TKr are compatible with the TKr’s version of Kubernetes. The minor versions of the components remain the same for all TKrs with the same minor version of Kubernetes. However, the patch versions for the components may vary for TKrs with the same minor version of Kubernetes.

All TKrs with the same minor version of Kubernetes share the same minor version of a component in the BoM, but their patch version numbers may vary. For example, a TKr with Kubernetes v1.23.8 has Antrea v1.5.3, Pinniped v0.12.1 and other TKrs with Kubernetes versions 1.22.x may contain different patch versions numbered as Antrea 1.2.y, but not 1.3.y and Pinniped v0.12.z, but not v0.11.z.

To check the version of a component in a TKr:

  1. Find the BoM file on your local machine that corresponds to the TKr, for example ~/.config/tanzu/tkg/bom/tkr-bom-v1.23.8+vmware.1-tkg.1-tf-v0.25.0.yaml.

  2. In the BoM file, check the version listed for the component. For example,

    antrea:
    - version: v1.5.3+vmware.2
     images:
       antreaImage:
         imagePath: antrea/antrea-debian
         tag: v1.5.3_vmware.2.
    
    pinniped:
    - version: v0.12.1+vmware.1
     images:
       pinnipedImage:
         imagePath: pinniped
         tag: v0.12.1_vmware.1
    

    For the Kubernetes version in the same file,

    kubernetes:
    - version: v1.23.8+vmware.1
     images:
       kubeAPIServer:
         imagePath: kube-apiserver
         tag: v1.23.8_vmware.1
       kubeControllerManager:
         imagePath: kube-controller-manager
         tag: v1.23.8_vmware.1
    

Tanzu Kubernetes Release Availability on Azure

VMware publishes TKrs to all Microsoft Azure regions within the AzurePublicCloud and AzureUSGovernment cloud environments.

Target Operating Systems

The following table shows the operating systems for cluster nodes that Tanzu Kubernetes releases support:

vSphere AWS Azure
Distributed with TKG Ubuntu 20.04
Photon OS 3
Ubuntu 20.04
Amazon Linux 2
Ubuntu 20.04
Ubuntu 18.04
Custom Image (see Build Machine Images) Ubuntu 20.04
Ubuntu 18.04
RHEL 8
Photon OS 3
Ubuntu 20.04
Ubuntu 18.04
Amazon Linux 2
Ubuntu 20.04
Ubuntu 18.04

check-circle-line exclamation-circle-line close-line
Scroll to top icon