vSphere with Tanzu workloads, including vSphere Pods, VMs, and Tanzu Kubernetes clusters, are deployed to a vSphere Namespace. You define a vSphere Namespace on a Supervisor Cluster and configure it with resource quota and user permissions. Depending on the DevOps needs and workloads they plan to run, you might also assign storage policies, VM classes, and content libraries for fetching the latest Tanzu Kubernetes releases and VM images.
Create and Configure a vSphere Namespace As a vSphere administrator, you create a vSphere Namespace on the Supervisor Cluster. You set resources limits to the namespace and permissions so that DevOps engineers can access it. You provide the URL of the Kubernetes control plane to DevOps engineers where they can run Kubernetes workloads on the namespaces for which they have permissions.
Set Default Memory and CPU Reservations and Limits for vSphere Pod Containers You can set the default memory and CPU reservations and limits for containers on a namespace through the vSphere Client. DevOps engineers can later override these values in the pod specifications they define. Container requests translate to resource reservations on vSphere Pods.
Configure Limitations on Kubernetes Objects in a vSphere Namespace You can configure limitations for pods running in the vSphere Namespace as well as limitations for various Kubernetes objects. The limitations that you configure for an object depend on the specifics of your applications and the way you want them to consume resources within a vSphere Namespace.
Monitor and Manage Resources in a vSphere Namespace You can monitor and manage different aspects of a vSphere Namespace, such as resource consumption for the namespace as well as the number of different Kubernetes objects that exist in a namespace and they states.
Configure a vSphere Namespace for Tanzu Kubernetes releases Configure the vSphere Namespace where you plan to provision Tanzu Kubernetes clusters by associating the namespace with the content library for Tanzu Kubernetes releases and with the VM classes you want to use.
Provision a Self-Service Namespace Template As a vSphere administrator, you can create a Supervisor Namespace, set CPU, memory, and storage limits to the namespace, assign permissions, and activate the namespace service on a cluster as a template. As a result, DevOps engineers can create a Supervisor Namespace in a self-service manner and deploy workloads within it.