jason810496 opened a new issue, #61432:
URL: https://github.com/apache/airflow/issues/61432
### Body
The new `gunicorn` server type provides rolling worker restarts, but for
users who continue to use the default `uvicorn` mode on Kubernetes, it’s
useful to have a first‑class mechanism in the Helm chart to periodically
restart the API server pods.
This gives users an out‑of‑the‑box, supported way to manage long‑running API
server processes when deploying Airflow to Kubernetes via the Helm chart.
We should enhance the official Airflow Helm chart to:
- Add an optional Kubernetes `CronJob` (or equivalent mechanism) that:
- Periodically runs `kubectl rollout restart
deployment/airflow-api-server` (or the appropriate resource name).
- Has configurable schedule (cron expression), target deployment name, and
enabled/disabled flag.
### Committer
- [x] I acknowledge that I am a maintainer/committer of the Apache Airflow
project.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
