Skip to main content

Microsoft Azure cluster settings

Unless otherwise specified, new clusters on Microsoft Azure are created with a set of default resources that are considered appropriate for most use cases.

Default cluster values

ResourceDescriptionQuantity/Default Size
Azure Kubernetes Service (AKS) ClusterRuns the Astro Data Plane, which hosts the resources and data required to execute Airflow tasks.1x
Resource GroupA container for cluster resources.1x
Worker node poolA node pool that runs all workers across Deployments in the cluster. The number of nodes in the pool auto-scales based on the demand for workers in your cluster. You can configure multiple worker node pools to run tasks on different worker types. This node pool is fully managed by Astronomer.1x pool of Standard_D4d_v5 nodes
Airflow node poolA node pool that runs all core Airflow components, including the scheduler and webserver. This node pool is fully managed by Astronomer.1x pool of Standard_D4d_v5 nodes
Astro system node poolA node pool that runs all other system components required in Astro. The availability zone determines how many nodes are created. This node pool is fully managed by Astronomer.1x pool of Standard_D4d_v5 nodes
Azure Virtual Network (VNet)A virtual network that hosts Azure resources.1x /19
SubnetsCreated in the VNet and used for the backing database, Pod, node, and private endpoints.
/28 for database
/21 for pods
/21 for nodes
/22 for private endpoints
Azure Database for PostgreSQL Flexible ServerA private database instance and the Astro data plane primary database. Hosts a metadata database for each hosted Airflow Deployment.Standard_D4ds_v4
Private DNS Zone for DatabaseProvides access to the private database instance.1x
Azure Storage Account (Standard)Stores Azure Blobs.1x
Azure Blob StorageStores Airflow task logs.1x
Private Endpoint for Blob StorageProvides access to Azure Blob storage task logs.1x
Private DNS Zone for Blob StorageProvides access to Azure Blob storage task logs.1x
Public IP AddressRequired for connectivity to the control plane and other services.1x
Maximum Node CountThe maximum number of worker nodes that your Astro cluster can support. When this limit is reached, your cluster can't auto-scale and worker Pods may fail to schedule.20

Supported cluster configurations

Depending on the needs of your organization, you may be interested in modifying certain configurations of a new or existing cluster on Astro.

To create a new cluster on Astro with a specified configuration, see Install Astro on Azure or Create a cluster. To make changes to an existing cluster, see Modify a cluster.

Supported regions

Astro supports the following Azure regions:

  • Australia East
  • Canada Central
  • Central US
  • East US
  • Japan East
  • South Africa North
  • South Central US
  • West Europe
  • West US 3

Modifying the region of an existing Astro cluster isn't supported. If you're interested in a region that isn't on this list, contact Astronomer support.

Worker node pools

Node pools are a scalable collection of worker nodes with the same instance type. These nodes are responsible for running the Pods that execute Airflow tasks. If your cluster has a node pool for a specific instance type, you can configure tasks to run on those instance types using worker queues. To make an instance type available in a cluster, contact Astronomer support with a request to create a new node pool for the specific instance type. Not all instance types are supported in all AWS regions.

Astronomer monitors your usage and the number of nodes deployed in your cluster. As your usage of Airflow increases, Astronomer support might contact you and provide recommendations for updating your node pools to optimize your infrastructure spend or increase the efficiency of your tasks.

For detailed information on each instance type, see Virtual machines in Azure. If you're interested in a machine type that isn't on this list, contact Astronomer support. Not all machine types are supported in all regions.

Worker node size resource reference

Each worker node in a pool runs a single worker Pod. A worker Pod's actual available size is equivalent to the total capacity of the instance type minus Astro’s system overhead.

The following table lists all available instance types for worker node pools, as well as the Pod size that is supported for each instance type. As the system requirements of Astro change, these values can increase or decrease.

Node Instance TypeCPUMemory
Standard_D4_v52.5 CPUs9.3 GiB MEM
Standard_D8_v56.4 CPUs24 GiB MEM
Standard_D4d_v52.5 CPUs9.3 GiB MEM
Standard_D8d_v56.4 CPUs24 GiB MEM

If your Organization needs an instance type that supports a larger worker size, contact Astronomer support. For more information about configuring worker size on Astro, see Configure a Deployment.

Maximum node count

Each Astro cluster has a limit on how many nodes it can run at a time. This limit includes the worker nodes and system nodes managed by Astronomer.

The default maximum node count for all nodes across your cluster is 20. A cluster's node count is most affected by the number of worker Pods that are executing Airflow tasks. See Worker autoscaling logic.

If the node count for your cluster reaches the maximum node count, new tasks might not run or get scheduled. Astronomer support monitors the maximum node count and will contact your organization if it is reached. To check your cluster's current node count, contact Astronomer Support.