A vSphere Namespace provides the runtime environment for TKG clusters on Supervisor . To provision a TKG cluster on Supervisor , you first configure a vSphere Namespace with users, roles, compute, storage, content library, and virtual machine classes. This configuration is inherited by TKG clusters that run in that namespace.
What to read next
Using vSphere Namespaces with TKG Clusters on Supervisor A vSphere Namespace is a network-scoped tenancy on Supervisor . vSphere Namespaces are used to host TKG clusters, and provide networking, role permissions, persistent storage, resource quota, and content library and VM class integration.
Create a vSphere Namespace for Hosting TKG Clusters on Supervisor You provision a TKG cluster in a vSphere Namespace on Supervisor .
Configure a vSphere Namespace for TKG Clusters on Supervisor You deploy one or more TKG clusters to a vSphere Namespace . Configuration settings applied to the vSphere Namespace are inherited by each TKG cluster deployed there.
Override Supervisor Network Settings for a vSphere Namespace If you have enabled Supervisor with NSX networking, you can specify different network settings when you create a vSphere Namespace . Overridden Supervisor network settings apply only to this vSphere Namespace segment.
Using Virtual Machine Classes with TKG Clusters on Supervisor To size TKG cluster nodes, you specify the virtual machine class. TKG provides default classes, and you can create your own. To use a class, associate it with the target vSphere Namespace and reference the class in the TKG cluster manifest.
Verify vSphere Namespace Configuration for TKG Cluster Provisioning Once you have configured a vSphere Namespace , log in to Supervisor and verify that it is ready for provisioning TKG clusters.
Enable vSphere Namespace Creation Using Kubectl You can enable the vSphere Namespace Service to let developers manage the lifecycle of vSphere Namespaces using kubectl
.
Remove a vSphere Namespace from Supervisor You can remove a vSphere Namespace from Supervisor . Before doing so you should delete any TKG clusters provisioned there.