Setting resources for containers¶

It is possible to set resources for the containers managed by the chart. You can define different resources for various Airflow containers. By default the resources are not set.

Note

The Kubernetes scheduler can use resources to decide which node to place the pod on. Since a pod resource request/limit is the sum of the resource requests/limits for each container in the pod, it is advised to specify resources for each container in the pod.

Possible containers where resources can be configured include:

dags.gitSync.resources
pgbouncer.metricsExporterSidecar.resources
pgbouncer.resources
apiServer.resources
scheduler.resources
workers.celery.kerberosInitContainer.resources
workers.celery.kerberosSidecar.resources
workers.celery.logGroomerSidecar.resources
workers.celery.resources
workers.kerberosInitContainer.resources
workers.kerberosSidecar.resources
workers.kubernetes.kerberosInitContainer.resources
workers.kubernetes.kerberosSidecar.resources
workers.kubernetes.resources
workers.logGroomerSidecar.resources
workers.resources
triggerer.resources
dagProcessor.resources
flower.resources
redis.resources
statsd.resources
otelCollector.resources
cleanup.resources
createUserJob.resources
databaseCleanup.resources
migrateDatabaseJob.resources

For example, specifying resources for scheduler container:

values.yaml¶

scheduler:
   resources:
   limits:
      cpu: 1
      memory: 1Gi
   requests:
      cpu: 500m
      memory: 512Gi