This page provides a comprehensive reference for all available configuration options in vCluster’sDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/loft-sh/vcluster/llms.txt
Use this file to discover all available pages before exploring further.
values.yaml. These values control the behavior of your virtual cluster deployment.
Configuration Structure
vCluster configuration is organized into several main sections:- sync: Resource synchronization between virtual and host clusters
- controlPlane: Control plane components and deployment settings
- networking: Network configuration and DNS settings
- rbac: Role-Based Access Control configuration
- policies: Resource quotas, limits, and network policies
- integrations: Third-party operator integrations
- deploy: Additional components to deploy
- privateNodes: Private nodes mode configuration
- experimental: Experimental features
Top-Level Configuration Options
Configure how vCluster exports the kubeconfig file.
Define which vCluster plugins to load. This is a map of plugin configurations.
Configuration related to telemetry gathered about vCluster usage.
Structured logging options for vCluster.
Example: Basic Configuration
Example: Service Account Authentication
Global Values
Global values shared across all Helm (sub)charts. These values are passed to all sub-charts and can be used for consistent configuration across the deployment.
Related Configuration
- See Sync Configuration for resource synchronization options
- See Control Plane for control plane settings
- See Networking Options for network configuration
- See RBAC Configuration for access control settings
Validation
vCluster validates the configuration on startup. Common validation rules include:- Backing store type cannot be changed after initial deployment
- Namespace sync settings cannot be modified after enabling
- VPN settings cannot be toggled after initial configuration