As a vSphere administrator, you can add a VM class to one or more namespaces on a Supervisor Cluster. When you add a VM class to a namespace, you make the class available to DevOps users, so that they can start self-servicing VMs in the Kubernetes namespace environment. The VM classes you assign to the namespace are also used by the VMs that make up Tanzu Kubernetes clusters.
You can add multiple VM classes to a single namespace. Different VM classes serve as indicators of different levels of service. If you publish multiple VM classes, DevOps users can select between all custom and default classes when creating and managing virtual machines in the namespace.
To be able to deploy a Tanzu Kubernetes cluster in a newly created namespace, DevOps engineers need to have access to VM classes. As a vSphere administrator, you must explicitly associate default or custom VM classes to any new namespace where the Tanzu Kubernetes cluster is deployed. Existing namespaces, where Tanzu Kubernetes clusters have been already provisioned, continue to have automatic access to default VM classes. But you can also associate custom VM classes with any existing namespace.
Use default VM classes that VMware provides or create new classes. See Create a VM Class in vSphere with Tanzu.
- In the vSphere Client, go to the namespace.
- From the vSphere Client home menu, select Workload Management.
- Click the Namespaces tab and click the namespace.
- Add a VM class.
- On the VM Service pane, click Add VM Class.
- Select one or several VM classes and click OK.
The VM classes you added become available in the namespace for the DevOps to self-service VMs. These classes can also be used by the VMs that make up Tanzu Kubernetes clusters.
What to do next
After you associate a VM class with a namespace, you can add more VM classes or remove the class to unpublish it from the namespace. See Manage VM Classes on a Namespace in vSphere with Tanzu.