Support HPA and topologySpreadConstraints for apiServer
#51,935 opened on 2025年6月19日
Repository metrics
- Stars
- (44,809 stars)
- PR merge metrics
- (平均マージ 7d 18h) (30d で 834 merged PRs)
説明
Official Helm Chart version
1.16.0 (latest released)
Apache Airflow version
3.0.2
Kubernetes Version
v1.30.12
Helm Chart configuration
No response
Docker Image customizations
Add GIT for bundles
What happened
We would like to enhance the official Apache Airflow Helm chart v1.16.0 by adding first‑class support for HorizontalPodAutoscaler (HPA) and topologySpreadConstraints on the apiServer component. Currently, enabling these settings in values.yaml has no effect on the generated manifests.
What you think should happen instead
HPA for apiServer
When apiServer.hpa.enabled: true in values.yaml, render a HorizontalPodAutoscaler resource for airflow-api
Honor standard HPA parameters (minReplicas, maxReplicas, metrics) analogous to other components
TopologySpreadConstraints for apiServer
When apiServer.topologySpreadConstraints is defined, inject that block into Deployment.spec.template.spec of airflow-api
Use the same schema as elsewhere in the chart (e.g. scheduler, webserver)
How to reproduce
Add HPA or TopologySpreadConstraints parameter will trigger the error "apiServer: Additional property topologyKey is not allowed".
Anything else
No response
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct