> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/private-cloud-director/getting-started/self-hosted/availability-zones.md).

# 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

```bash
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

```yaml
# 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.platform9.com/private-cloud-director/getting-started/self-hosted/availability-zones.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
