Add Horizontal Pod Autoscaler (HPA) Support for Airflow API Server #52392
+258
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This pull request introduces Horizontal Pod Autoscaler (HPA) support for the Airflow API server in the Helm chart, enabling automatic scaling of API server pods based on resource utilization or custom metrics. The changes enhance the chart's flexibility and scalability, allowing users to configure autoscaling for the API server to handle varying workloads efficiently.
Changes:
Created
chart/templates/api-server/api-server-hpa.yaml
to define the HPA resource for the API server.Modified
chart/values.schema.json
to include a new hpa section under apiServer.Added HPA configuration in
chart/values.yaml
under apiServer.hpa with sensible defaultsIntroduced
helm-tests/tests/helm_tests/apiserver/test_hpa_apiserver.py
to validate HPA behaviorHow to Test:
apiServer.hpa.enabled=true
and verify the HPA resource is created with default settings.minReplicaCount
,maxReplicaCount
,metrics
, orbehavior
in values.yaml and confirm the HPA resource reflects the changes.helm-tests/tests/helm_tests/apiserver/test_hpa_apiserver.py
to validate logic.Additional Notes:
Included deployment and HPA status screenshot from kubectl displaying an Airflow API server deployment with 4 pods running.
Related Issues:
#51935
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in airflow-core/newsfragments.