Layouts and configuration

Standard

The Standard layout is intended for deploying a cluster within the vSphere infrastructure with full control over resources, networking, and storage.

Key features:

• Uses a vSphere Datacenter as a region.
• Uses a vSphere Cluster as a zone.
• Supports multiple zones and node placements across zones.
• Supports using different datastores for disks and volumes.
• Supports network connectivity including additional network isolation (for example, MetalLB + BGP).

Example configuration:

apiVersion: deckhouse.io/v1
kind: VsphereClusterConfiguration
layout: Standard
provider:
  server: '<SERVER>'
  username: '<USERNAME>'
  password: '<PASSWORD>'
vmFolderPath: dev
regionTagCategory: k8s-region
zoneTagCategory: k8s-zone
region: X1
internalNetworkCIDR: 192.168.199.0/24
masterNodeGroup:
  replicas: 1
  zones:
    - ru-central1-a
    - ru-central1-b
  instanceClass:
    numCPUs: 4
    memory: 8192
    template: dev/golden_image
    datastore: dev/lun_1
    mainNetwork: net3-k8s
nodeGroups:
  - name: khm
    replicas: 1
    zones:
      - ru-central1-a
    instanceClass:
      numCPUs: 4
      memory: 8192
      template: dev/golden_image
      datastore: dev/lun_1
      mainNetwork: net3-k8s
sshPublicKey: "<SSH_PUBLIC_KEY>"
zones:
  - ru-central1-a
  - ru-central1-b

Required parameters:

• region: Tag assigned to the Datacenter object.
• zoneTagCategory and regionTagCategory: Tag categories used to identify regions and zones.
• internalNetworkCIDR: Subnet for assigning internal IP addresses.
• vmFolderPath: Path to the folder where cluster virtual machines will be placed.
• sshPublicKey: Public SSH key used to access the nodes.
• zones: List of zones available for node placement.

List of required privileges

A detailed list of privileges required for Deckhouse Kubernetes Platform to work in vSphere: