This a second part of the deployment vSphere IaaS Control Plane with Avi Load Balancer and VDS. In this post, we will enable Workload Management, create vSphere namespace and a cluster. Also, I’m going to deploy 3 tier app inside the Kubernetes workload cluster.
vSphere IaaS Control Plane with VMware Avi Load Balancer and vSphere Distributed Switch (VDS) provides a robust architecture for managing and delivering containerized applications in a virtualized environment. This setup, enables unified environment where Kubernetes applications can run alongside with traditional virtual machines. Administrators can deploy K8S workload clusters directly on vSphere environment. For some time, this product was know as vSphere with Tanzu or Tanzu Kubernetes Grid Service, aka TKGs.
VMware Aria Operations (ex vROps Operations) is a powerful tool for monitoring infrastructure, virtual machines, predict resource demands or costs. Use cases is much more. One of them is ability to visualize, provide logs and information from the Tanzu Kuberentes Grid clusters. To obtain insightful data from the nodes you need to use dedicated addon – Management Pack for Kubernetes.
Troubleshooting of the cluster failure can be very demanding. After numerous unsuccessful attempts to fix the fault, we often report it to the support. VMware support, usually want from us to generate log bundle from that cluster.
TKG cluster can be deployed in a many ways. You can use simple YAML file and run it from the Supervisor. You can use some automation tool like Jenkins or create Kubernetes nodes from the TMC.
Apart from that, Terraform has a dedicated Tanzu Mission Control provider (plugin) to automate many processes.
Between Cluster v1beta1 API and earlier APIs are lot of configuration changes. One of them, is introduced in TKG 2.0 a new resource pool called ClusterClass.
Some time ago, I received a message from users, that they can’t create new services on TKG clusters. The new services had an unusual “pending” status. We didn’t make any major changes to the infrastructure, no upgrades etc…situation like: it worked before, now it doesn’t work.
Last time, I deployed a new cluster. For this task, I used Tanzu Mission Control. Everything goes well, machines was created. Than, I connect to dedicated vSphere namespace and try to list tkc clusters. And a new cluster was not visible…Why?
If you’re using vSphere with Tanzu based on vSphere 7 and vSphere 8, you’ve probably noticed a lot of differences. From enabling Workload Management wizard to a separated section to editing the Supervisor cluster.
In some situations, we need to check network connections, node configuration, dubug failures, problems or check something from the TKGs control plane or worker node.
Copyright vmattroman.com © 2024