This topic outlines how Tanzu Kubernetes Grid uses Tanzu Kubernetes releases (TKrs) and VM images to deploy clusters that run nodes with specific Kubernetes versions and operating systems.
To support running diverse applications efficiently and reliably, you can customize Tanzu Kubernetes Grid (TKG) clusters to run its worker nodes and other VMs on different Kubernetes versions, operating systems, and operating system (OS) versions. For supported Kubernetes versions, VMware publishes Tanzu Kubernetes releases (TKrs), which associate a specific patch version of Kubernetes with compatible versions of a base OS plus compatible versions of additional components required by cluster nodes.
Each TKr contains everything that a specific patch version of Kubernetes needs to run on various VM types on different infrastructures, and the management cluster uses a TKr to create a workload cluster that runs the desired Kubernetes and OS version.
How TKrs are published, how TKG uses them, and which Kubernetes versions they support depend on the management cluster deployment option:
TKG with a standalone management cluster:
TanzuKubernetesRelease
objects
~/.config/tanzu/tkg/bom
directorytanzu kubernetes-release get
For TKG with a standalone management cluster, TKrs distributed by VMware support a selection of OSes by default, as listed in the Target Operating Systems table below.
You can also create clusters based on additional OSes listed as Custom image in the table. To do this, you run Kubernetes Image Builder and create a custom TKr as described in Build Machine Images.
The following table shows the operating systems for cluster nodes that Tanzu Kubernetes releases support:
Distributed with TKG | Custom Image (see Build Machine Images) |
---|---|
For Kubernetes v1.27+:
For Kubernetes v1.27 and earlier:
|
|