Skip to main content

GCP Hybrid cluster settings


This document applies only to Astro Hybrid. To see whether you're an Astro Hybrid user, click the Astronomer logo in the upper left corner of the Cloud UI and go to Settings > General. Your Astro product type is listed under Product Type.

To create a Deployment on Astro Hosted, see Astro resource reference.

Unless otherwise specified, new Clusters on Google Cloud Platform (GCP) are created with a set of default resources that our team has deemed appropriate for most use cases.

Read the following document for a reference of our default resources as well as supported cluster configurations.

Default cluster values

ResourceDescriptionQuantity/ Default SizeConfigurable
GKE ClusterA GKE cluster is required to run the Astro data plane, which hosts the resources and data required to execute Airflow tasks. Workload Identity is enabled on this cluster.1x, IP Ranges are for cluster IPs and for cluster services
Worker node poolA node pool that hosts all workers with the default worker type for all 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 additional worker node pools to run tasks on different worker types.1x pool of e2-standard-4 nodesYes. See Manage worker node pools.
Airflow node poolA node pool that runs all core Airflow components, including the scheduler and webserver, for all Deployments in the cluster. This node pool is fully managed by Astronomer.1x pool of e2-standard-4 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 n2-standard-2 nodes
Cloud SQL for PostgreSQLThe Cloud SQL instance is the primary database for the Astro data plane. It hosts the metadata database for each Airflow Deployment hosted on the GKE cluster. All Cloud SQL instances are multi-AZ.1x regional instance with 4 vCPUs, 16GB memoryYes. See Configure your relational database.
VPCVirtual private network for hosting GCP resources1x /19Yes. See Connect Astro to GCP data sources.
SubnetA single subnet is provisioned in the VPC.1, IP Range is
Service Network PeeringThe Astro VPC is peered to the Google Service Networking VPC.1, IP Range is
NAT Router (External)Required for connectivity with the Astro control plane and other public services1.
Workload Identity PoolAstro uses the fixed Workload Identity Pool for your cluster. One is created if it does not
Google Cloud Storage (GCS) BucketStores Airflow task logs.1 bucket with name airflow-logs-<clusterid>

Supported cluster regions

You can host Astro Hybrid clusters in the following GCP regions:

asia-east1Taiwan, Asia
asia-northeast1Tokyo, Asia
asia-northeast2Osaka, Asia
asia-northeast3Seoul, Asia
asia-south1Mumbai, Asia
asia-south2Delhi, Asia
asia-southeast1Singapore, Asia
asia-southeast2Jakarta, Asia
australia-southeast1Sydney, Australia
australia-southeast2Melbourne, Australia
europe-central2Warsaw, Europe
europe-north1Finland, Europe
europe-southwest1Madrid, Europe
europe-west1Belgium, Europe
europe-west2England, Europe
europe-west3Frankfurt, Europe
europe-west4Netherlands, Europe
europe-west6Zurich, Europe
europe-west8Milan, Europe
europe-west9Paris, Europe
northamerica-northeast1Montreal, North America
northamerica-northeast2Toronto, North America
southamerica-east1Sau Paolo, South America
southamerica-west1Santiago, South America
us-central1Iowa, North America
us-east1South Carolina, North America
us-east4Virginia, North America
us-east5Columbus, North America
us-south1Dallas, North America
us-west1Oregon, North America
us-west2Los Angeles, North America
us-west3Salt Lake City, North America
us-west4Nevada, North America

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

Supported Cloud SQL instance types

The following Cloud SQL instance types are supported on Astro:

  • Small General Purpose (2 CPU, 8 GiB MEM)
  • Medium General Purpose (4 CPU, 16 GiB MEM)
  • Small Memory Optimized (2 CPU, 12 GiB MEM)
  • Medium Memory Optimized (4 CPU, 24 GiB MEM)

For detailed information about each instance type, see the Cloud SQL documentation. If you're interested in an Cloud SQL instance type that is not on this list, contact Astronomer support.

Supported worker node pool instance types

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
e2-standard-43 CPUs13 GiB MEM
e2-standard-87 CPUs29 GiB MEM
e2-standard-1615 CPUs61 GiB MEM
e2-highmem-43 CPUs29 GiB MEM
e2-highmem-87 CPUs61 GiB MEM
e2-highmem-1615 CPUs125 GiB MEM
e2-highcpu-43 CPUs1 GiB MEM
e2-highcpu-87 CPUs5 GiB MEM
e2-highcpu-1615 CPUs13 GiB MEM
n2-standard-43 CPUs13 GiB MEM
n2-standard-87 CPUs29 GiB MEM
n2-standard-1615 CPUs61 GiB MEM
n2-highmem-43 CPUs29 GiB MEM
n2-highmem-87 CPUs61 GiB MEM
n2-highmem-1615 CPUs125 GiB MEM
n2-highcpu-43 CPUs1 GiB MEM
n2-highcpu-87 CPUs5 GiB MEM
n2-highcpu-1615 CPUs13 GiB MEM
c2-standard-43 CPUs13 GiB MEM
c2-standard-87 CPUs29 GiB MEM

If your Organization is interested in using 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.

Sign up for Developer Updates

Get a summary of new Astro features once a month.

You can unsubscribe at any time.
By proceeding you agree to our Privacy Policy, our Website Terms and to receive emails from Astronomer.