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.
The challenge is easy – vSAN datastore is running out of space and need to be expanded.
The whole process is a quite obvious. If there are free disk slots in a ESXi hosts, get a new drives, install in the servers and reconfigure vSAN capacity pool from the vCenter.
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.
Copyright vmattroman.com © 2023
