Worker pool management

OSC Dashboard

1. Click Settings button as shown on picture below. Continue in pop-up window as shown on image below

2. Click + sign to add worker group.

3. Configure your worker pool by setting these characteristics

• Group Name: enter here name of new worker pool
• Machine Type: select from drop-down menu of currently supported Machine Types, according to your needs
• Machine Image: select from drop-down menu of currently supported Machine Images, according to your needs
• Container Runtime: select from drop-down menu of currently supported Container Runtime, according to your needs
• Volume Size: enter here volume size in GiB
• Autoscaling configuration:
  • Autoscaling Min.: enter here minimum number of worker nodes
  • Autoscaling Max.: enter here maximum number of worker nodes
  • Max. Surge: enter here maximum number of nodes that can be created exceeding the maximum size during updates
  • Max. Unavailable: enter here maximum number of nodes that can be unavailable during updates
• Zone: select Availability Zones

Garden Cluster

On the Garden cluster level the Shoot object can be edited (using kubectl edit or kubectl patch) to update worker pool configuration.

Example worker group setup:

apiVersion: core.gardener.cloud/v1beta1
kind: Shoot
spec:
  provider:
    type: onmetal
    # Please note that workers is a list of worker pool configurations.
    workers:
    - name: idp
      cri:
        name: containerd
      machine:
        architecture: amd64
        image:
          name: gardenlinux
          version: 1061.0.20
        type: <machine-class>
      maxSurge: 1
      maxUnavailable: 0
      maximum: 12
      minimum: 12
      systemComponents:
        allow: true
      volume:
        size: 100Gi
        type: fast
      zones:
      - mdb1-pool1
      - mdb2-pool1
      - mdb3-pool1
    # Here an another worker pool configuration can be added