Checkout what is the architecture for TKG and how it integrates with the Supervisor and its components. Learn how networking and storage work for TKG clusters as well what is high-availability for TKG and which Supervisor deployment supports it.
What to read next
TKG Architecture The TKG provides self-service life cycle management of TKG clusters. You use the TKG to create and manage TKG clusters in a declarative manner that is familiar to Kubernetes operators and developers.
TKG Cluster Networking A TKG cluster provisioned by the TKG supports two CNI options: Antrea (default) and Calico. Both are open-source software that provide networking for cluster pods, services, and ingress.
Storage for TKG Clusters TKG clusters, as some other components and workloads that run in Supervisor namespaces, require persistent storage.
High-Availability for TKG Clusters You can provide high-availability to TKG clusters when they are deployed on a three vSphere Zone Supervisor . A vSphere Zone maps to a vSphere cluster, which means that when you deploy a Supervisor on three vSphere Zones, it utilizes the resources of all three underlying vSphere clusters. This protects your workloads running inside TKG clusters against failure on a vSphere cluster level. On a single-zone deployment, high-availability for TKG clusters is provided on an ESXi host level by vSphere HA.
TKG Authentication Learn what are the different authentication mechanisms and their use with TKG clusters.