For the complete documentation index, see llms.txt. This page is also available as Markdown.

Availability Zones

Starting from this release, you can configure availability zones for your Private Cloud Director deployment.

Overview

By default, the nodes were neither labeled nor was the workload distributed across them. With this enhancement, nodes can now be labeled through a YAML configuration, ensuring workloads are scheduled correctly based on geo-location or any other deployment-specific requirements.

This also improves high availability by ensuring that workloads are evenly distributed across all zones during deployment. As a result, even if certain nodes fail, the services remain available and continue operating without disruption.

Configure AZ's

The AZ's need to be configured before setup creation while running the configure command

airctl configure \ 
  --master-ips <master-ips> \ 
  --master-vip4 <master-vip4> \ 
  --master-vip-interface <master-vip-interface> \ 
  --ipv4 <type> \ 
  --external-ip4 <external-ip4> \ 
  --du-fqdn <fqdn> \ 
  --storage-provider <storage-provider> \ 
  --node-az-labels /path/to/node-az-labels.yaml

The node-az-labels.yaml file should have values in this type

# node IP: zone name example
10.10.11.173: asia
10.10.15.162: asia
10.10.15.173: europe
10.10.15.63: europe
10.10.20.11: us

Once the above steps are completed, create the cluster. You will then be able to observe that the workload is distributed across the nodes as expected.

Was this helpful?