Pausing or resuming an Apache Airflow™ cluster
Written by
Updated at October 30, 2026
Pausing stops the main Apache Airflow™ components. The cluster configuration, metadata database, buckets, and credentials are saved.
A weekly cleanup of metadata older than 90 days continues during suspension.
Warning
Pausing terminates the active pods of the main components. Do not use it when running critical tasks.
Pausing a cluster
-
Install
spec.pause: true:kubectl patch airflowcluster <cluster_name> \ -n <namespace> \ --type=merge \ -p '{"spec":{"pause":true}}' -
Wait for the
Pausedstatus:kubectl get airflowcluster <cluster_name> \ -n <namespace> \ -w
Resuming a cluster
-
Install
spec.pause: false:kubectl patch airflowcluster <cluster_name> \ -n <namespace> \ --type=merge \ -p '{"spec":{"pause":false}}' -
Wait for the
Readystatus:kubectl get airflowcluster <cluster_name> \ -n <namespace> \ -w
After resuming, the scheduler resumes processing DAG files. Check the schedules and task statuses in the web UI.