In a vSphere with Tanzu environment, when you enable Workload Management, the Supervisor cluster that gets deployed operates as the management cluster. After supervisor cluster is deployed, you can provision two types of workload clusters
- Tanzu Kubernetes clusters.
- Clusters based on a ClusterClass (aka Classy Cluster).
TKG on vSphere 8 provides different sets of APIs to deploy a TKC or a Classy cluster:
- v1alpha3 API
- v1beta1 API
When you deploy a cluster using v1beta1 API, you get a Classy Cluster or TKG 2.0 cluster which is based on a default ClusterClass definition.
By default workload cluster don’t trust any self-signed certificates. Prior to TKG 2.0 clusters, the easiest way to make Tanzu Kubernetes Clusters (TKCs) to trust any self-signed CA certificate was to edit tkgserviceconfigurations and define your Trusted CAs there. This setting was then enforced on any newly deployed TKCs.
For TKG 2.0 clusters, the process has changed a bit and in this post I will walk through configuring the same.… Read More