Add checksum for JWT secret in API server and scheduler deployments i… #60111
Conversation
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
arjav1528
requested review from
hussein-awala,
jedcunningham and
jscheffl
as code owners
jscheffl
reviewed
Jan 5, 2026
…f conditions are met
…ksum based on jwtSecretName value
jscheffl
approved these changes
Jan 5, 2026
chirodip98
pushed a commit
to chirodip98/airflow-contrib
that referenced
this pull request
Jan 8, 2026
apache#60111) * Add checksum for JWT secret in API server and scheduler deployments if conditions are met * Update API server deployment to conditionally include JWT secret checksum based on jwtSecretName value
chirodip98
pushed a commit
to chirodip98/airflow-contrib
that referenced
this pull request
Jan 9, 2026
apache#60111) * Add checksum for JWT secret in API server and scheduler deployments if conditions are met * Update API server deployment to conditionally include JWT secret checksum based on jwtSecretName value
stegololz
pushed a commit
to stegololz/airflow
that referenced
this pull request
Jan 9, 2026
apache#60111) * Add checksum for JWT secret in API server and scheduler deployments if conditions are met * Update API server deployment to conditionally include JWT secret checksum based on jwtSecretName value
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Root Cause
The JWT secret checksum annotation was missing from both deployment templates. Other secrets (metadata-secret, pgbouncer-config-secret, etc.) had checksum annotations that trigger pod restarts when secrets change, but the JWT secret did not.
When Helm values change:
The API server redeploys (due to other checksum changes) and picks up the new JWT secret
The scheduler doesn't redeploy (no JWT secret checksum) and continues using the old secret
Tokens generated by the scheduler fail validation at the API server
Solution
Added checksum/jwt-secret annotations to both:
chart/templates/api-server/api-server-deployment.yaml
chart/templates/scheduler/scheduler-deployment.yaml
This ensures both components redeploy together when the JWT secret changes, keeping them synchronized.
Changes
Added JWT secret checksum annotation to API server deployment template
Added JWT secret checksum annotation to scheduler deployment template
Conditional logic matches the JWT secret template (only for Airflow 3.0+ when API server is enabled and chart manages the secret)
closes: #60040