5

Deploy vSphere TKG Clusters Through Mission Control

 3 years ago
source link: https://theithollow.com/2020/12/14/deploy-vsphere-tkg-clusters-through-mission-control/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
By Eric Shanks

There is new functionality included in VMware Tanzu Mission Control (TMC) that I’m pretty excited about. After the recent update, you can now register your vSphere with Tanzu Supervisor cluster with TMC and then begin provisioning workload clusters.

Before you can provision clusters, you’ll need to register your TKG Supervisor cluster to TMC. Those procedures require you to apply and update some YAML which you can find here.

Deploy a vSphere TKG Cluster through TMC

Login to your TMC account and go to the Clusters tab. Click the CREATE CLUSTER button where you’ll now see a drop down. Select Tanzu Kubernetes Grid Service on vSphere 7.

image-13.png

Select the Supervisor cluster from the drop down list. This list is populated with the registration instructions referred to earlier in this post. Then select a provisioner. This is a namespace within the Supervisor cluster where your TKG cluster objects will live.

image-14.png

Notice the Provisioner in TMC matches my Namespace in vCenter’s Workload Management Tab.

image-20.png

Now define your Cluster details. Names, descriptions, and labels. But also select a TMC cluster group. Cluster Groups often have TMC policies for enforcing controls across groups of clusters. Using groups and policies, is a simple way to apply security or governance policies to fleets of clusters.

image-15.png

The next screen asks some cluster configuration questions such as the pod/service CIDRs, and what storage classes to use. Those storage classes come from your configured supervisor cluster and are presented as a drop down.

image-16-758x1024.png

Select the level of availability:

  • Single node: 1 Control Plane Node (could be many workers)
  • Highly available: 3 Control Plane Nodes (could be many workers)

You’ll also need to select a storageclass and size for the control plane nodes.

image-17.png

On the final screen, you can create a node pool which defines your worker nodes. You can select the storage class, quantity and size of the worker nodes. Click the CREATE CLUSTER button.

image-18.png

After the process beings you’ll get status reports about the stages from the TMC console.

image-19-1024x300.png

When you complete the deployment, the policies attached to your cluster group should begin being enforced, and data will start being collected.

image-21-1024x582.png

The steps above can be achieve through the following command line command.

tmc cluster create --management-cluster-name hollow-supervisor --provisioner-name utility --cluster-group shanks-group --high-availability --name hollow-tmc1 --version v1.18.5+vmware.1-tkg.1.c40d30d --template tkgs  --storage-class tanzu-storage --worker-instance-type best-effort-xsmall --instance-type best-effort-xsmall

Summary

Tanzu Mission Control might become a major part of managing the lifecycles of Kubernetes clusters, especially if those customers are already vSphere customers. TMC can now provision clusters on both AWS and vSphere 7 with Tanzu.


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK