Private nodes
| Enterprise | ||||
|---|---|---|---|---|
| Available in these plans | Free | Dev | Prod | Scale |
| Private Nodes | ||||
| Private Nodes VPN | ||||
Free, Dev, Prod, and Scale are vCluster Platform license plans. Open source does not need a license or a Platform connection. See Compare open source and free tiers.
The privateNodes section of vcluster.yaml configures a cluster whose workloads run on dedicated worker nodes. To choose private nodes and join your first nodes, start with Private nodes in Deploy. This section covers the settings you tune after that.
- Auto Nodes: node pools, node type selectors, disruption, and limits for nodes that vCluster Platform provisions on demand.
- vCluster VPN: connect private nodes to the control plane through vCluster Platform when they can't reach it directly.
- Default node profile: apply a node profile to every node that joins without one.
Default node profile​
Set privateNodes.defaultProfile to a node profile name to apply it to any node that joins the clusterClusterA fully isolated Kubernetes environment provisioned for a single tenant. Each cluster has its own API server, controller manager, and resource namespace, backed by a virtualized control plane hosted on a control plane cluster. From the tenant's perspective it behaves exactly like a standard Kubernetes cluster. without an explicit profile:
privateNodes:
enabled: true
defaultProfile: general-compute
This takes precedence over the project's default node profile, if the project also has one configured. See Assignment and precedence for the full resolution order.
Config reference​
For every field under privateNodes, see the privateNodes reference.