Helm: Add API server rollout restart CronJob#69808
Open
Subham-KRLX wants to merge 1 commit into
Open
Conversation
Subham-KRLX
requested review from
Miretpl,
bugraoz93,
hussein-awala,
jedcunningham and
jscheffl
as code owners
Subham-KRLX
force-pushed
the
feat/api-server-rollout-restart-cronjob
branch
from
0f5d85c to
f694b8b
Compare
Subham-KRLX
changed the title
Subham-KRLX
force-pushed
the
feat/api-server-rollout-restart-cronjob
branch
from
f694b8b to
86dffc7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR adds Helm chart support for periodic API server rollout restarts on Kubernetes.
Problem:
Long-running uvicorn processes in the API server can accumulate stale resources. Kubernetes provides kubectl rollout restart as a native mechanism, but the Airflow Helm chart has no built in support for scheduling this.
Fix:
Adds a new apiServer.rolloutRestart configuration section with a CronJob, ServiceAccount, Role, and RoleBinding following the exact same pattern as the existing databaseCleanup CronJob.
closes: #61432
Was generative AI tooling used to co-author this PR?