Skip to content

Fix jwt-secret checksum annotation condition in dag-processor, triggerer, and worker deployments #63027

Open
shashbha14 wants to merge 1 commit intoapache:mainfrom
shashbha14:fix/jwt-secret-checksum-annotation
Open

Fix jwt-secret checksum annotation condition in dag-processor, triggerer, and worker deployments #63027
shashbha14 wants to merge 1 commit intoapache:mainfrom
shashbha14:fix/jwt-secret-checksum-annotation

Conversation

@shashbha14
Copy link
Contributor

  1. What this PR does
    Adds the 'checksum/jwt-secret' pod annotation to the dag-processor, triggerer, and worker deployments.

These components communicate with the API server and need to restart automatically when the JWT secret changes. The
annotation was already present in the scheduler and api-server deployments but was missing from these three.

The same conditional is used as in the scheduler:

  • Only applies for Airflow >= 3.0.0
  • Only when 'apiServer.enabled=true'
  • Skipped when 'jwtSecretName' is set (external secret)
  1. Related

…orker deployments

Fixes missing jwt-secret checksum annotations in dag-processor, triggerer,
and worker deployments. These components communicate with the API server and
need to restart when the JWT secret changes. Matches the same conditional
logic already present in scheduler and api-server deployments:
only include the annotation when airflowVersion >= 3.0.0, apiServer is enabled,
and no external jwtSecretName is provided.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@jscheffl
Copy link
Contributor

jscheffl commented Mar 7, 2026

Why is there a second PR open and not a correct made in #62178 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:helm-chart Airflow Helm Chart

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants