VMware Tanzu Kubernetes Grid (TKG) Bootstrap – Part 3

Preview in new tab

In the second series VMware Tanzu Kubernetes Grid (TKG) – PART2. I  covered the basic of VMware Tanzu Portfolio, supported platform for Tanzu whether VMware Cloud  (On-Premises or VCPP Cloud) or Public cloud  (AWS or Azure) and supported  kubernetes versions with latest VMware Tanzu Kubernetes Grid 1.2 release.

Before  deep diving  into Tanzu Kubernetes Grid (TKG) Architecture, Let’s discuss about Bootstrap Environment

The bootstrap environment is typically a VM on which you run the Tanzu Kubernetes Grid CLI or VM from where you plan to deploy the Management or Workload Cluster/s. When you initiate Tanzu Kubernetes Grid instance, it bootstrap on local VM first and then transfer to the cloud infrastructure of your choice whether VMware cloud  (On-Premises or VCPP Cloud) or Public cloud  (AWS or Azure). After bootstrapping the management cluster, This VM can be  used to manage the Tanzu Kubernetes Grid instance.

The TKG CLI is used to initialize cluster, as well as to create, scale, upgrade, and delete Tanzu Kubernetes clusters. Basically Administrator or Developer needs to have TKG CLI to administrator or manage the kubernetes infrastructures or Applications.

When you initialize the TKG cluster, A cluster plan runs within bootstrap VM to provides a set of configurable values for deployment, for example, the number of control plane machines, worker machines, number of vCPUs, amount of memory, and other parameters you want for your TKG cluster. 

TKG Management Cluster

The Management Cluster is the first cluster that you deploy when you create a Tanzu Kubernetes Grid instance. This is Kubernetes cluster that performs the role of the primary management and operational center for the Tanzu Kubernetes Grid instance. This cluster is where Cluster API runs.

TKG Workload Cluster

Once you have deployed Management Cluster, You can initiate the deployment of Tanzu Kubernetes cluster/s from the management cluster by using the Tanzu Kubernetes Grid CLI. These clusters are also called workload clusters. These are clusters where PODs/Containers will run and will host your applications.

A single bootstrap environment can be used to bootstrap as many instances of Tanzu Kubernetes Grid as you want to have for different environments, e.g. Test, dev, Production running in different IaaS Providers – vSphere, AWS or Azure.

That’s all about bootstrap, will discuss more on architecture in VMware Tanzu Kubernetes Grid (TKG) Architecture – Part 4. Stay tuned for next part.

Hope this will be informative. Happy learning and happy sharing 🙂 

Leave a Reply

Your email address will not be published. Required fields are marked *