Skip to main content
The control plane configuration defines how vCluster’s core components are deployed and managed, including the Kubernetes distribution, backing store, networking, and resource allocation.

Distro Configuration

controlPlane.distro.k8s
object
Kubernetes distribution configuration. Only one distro can be enabled at a time.

Backing Store

controlPlane.backingStore
object
Configure which backing store to use for the virtual cluster.

StatefulSet Configuration

controlPlane.statefulSet
object
Configure the vCluster control plane StatefulSet.

CoreDNS Configuration

controlPlane.coredns
object
CoreDNS deployment configuration.

Service and Ingress

controlPlane.service
object
Control plane service configuration.
controlPlane.ingress
object
Control plane ingress configuration.

Example: External Database

controlPlane:
  backingStore:
    database:
      external:
        enabled: true
        dataSource: postgres://vcluster:[email protected]:5432/vcluster
        certFile: /certs/client-cert.pem
        keyFile: /certs/client-key.pem
        caFile: /certs/ca.pem

Example: High Availability

controlPlane:
  statefulSet:
    highAvailability:
      replicas: 3
      leaseDuration: 60
      renewDeadline: 40
      retryPeriod: 15
    resources:
      limits:
        cpu: 2
        memory: 8Gi
      requests:
        cpu: 500m
        memory: 1Gi

Example: Custom Kubernetes Version

controlPlane:
  distro:
    k8s:
      enabled: true
      version: v1.30.0
      image:
        registry: ghcr.io
        repository: loft-sh/kubernetes
        tag: v1.30.0
      scheduler:
        enabled: true

Build docs developers (and LLMs) love