Configuring a Tenancy Model
vCluster supports multiple tenancy models and configuring the tenancy models starts how you select the worker node pool.
Worker node pool​
You decide what infrastructure is used for the vCluster's worker node pool.
Deciding which type of nodes you want to use for your vCluster must be determined upon vCluster creation. There is no migration/upgrade between the different worker node pool types.
Host nodes​
The following tenancy models use worker nodes from the host cluster that the vCluster is deployed on.
- Shared Nodes - (Default) All worker nodes of the host cluster can be used by the virtual cluster. All resources are synced to the single namespace that the vCluster is deployed on.
- Dedicated Nodes - A set of worker nodes of the host cluster are selected based on node labels. That set of worker nodes can be used by the virtual cluster. By default, all resources are synced to the single namespace that the vCluster is deployed on.
Resource syncing​
After selecting which set of worker nodes to use from the host cluster, you decide how you want resources synced from the virtual cluster to the host cluster.
- Single Namespace - (Default) - All resources are synced to a single namespace, specifically the namespace that the virtual cluster control plane pod is deployed in. Names of the resources are translated to new names on the host cluster to eliminate any naming conflicts.
- Namespace Syncing - Advanced - Enable syncing namespaces between the virtual cluster and host cluster allows the specified namespaces and its resources to be synced from the virtual cluster onto the host cluster. There is no translation of resources, so if you enable this feature, you must be aware of other virtual clusters deploying onto the host cluster to avoid naming conflicts.
Virtual nodes​
The following tenancy model uses virtual nodes which are deployed onto one of the worker nodes from the host cluster that the vCluster is deployed on.
- Virtual Nodes - A set of virtual nodes deployed on a worker node of the host cluster.
Private nodes​
The following tenancy models use individual nodes that are joined to the vCluster. Each node can only be used by one virtual cluster. One benefit of using private nodes is that vCluster can automatically manage the lifecycle of the worker nodes.
- Private Nodes
- Manually Provisioned - Nodes are provisioned outside of vCluster and added to the vCluster individually.
- Automatically Provisioned - Nodes are automatically provisioned and joined by vCluster and vCluster Platform. Node providers are managed inside vCluster Platform.
Worker node comparison​
The following table outlines the differences between using host nodes and private nodes:
| Feature | Host Nodes | Private Nodes |
|---|---|---|
| Isolated control plane | Yes | Yes |
| Ability to install custom CNI | No | Yes |
| Ability to install custom CSI drivers | No | Yes |
| Isolated network | No | Yes |
| Ability to re-use host controllers | Yes | No |
| Ability to view vCluster resources in the host cluster | Yes | No |
| Ability to automatically provision and add nodes based on resource requirements | No | Yes |