Repository navigation
helm checksums support in Helm Chart #62698
Copy link
Copy link
Closed
Labels
area:helm-chartAirflow Helm ChartAirflow Helm Chartkind:featureFeature RequestsFeature Requestsneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yet
Description
Activity
- addedkind:featureFeature RequestsFeature Requestsneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yet
on Mar 2, 2026 The chart actually already has checksums. For example, for scheduler: https://github.com/apache/airflow/blob/main/chart/templates/scheduler/scheduler-deployment.yaml#L99-L104
Are you referring to any more specific cases? May need some elaborations here.
The values.yaml does not support annotating the scheduler/dag processor/api server pods with checksum evaluated from custom secret/configmaps. For example. Imagine you create a configmap for airflow listeners plugin mounted on scheduler pod, If the configmap changes the scheduler pod still continues to run with the old configmap.
- added a commit that references this issue
on Mar 6, 2026 Maybe this #63019 can make what you expect happen? Let me know if this is what you desired or not ;-)
- added a commit that references this issue
on Mar 9, 2026 - added a commit that references this issue
on Mar 9, 2026 - added a commit that references this issue
on Mar 10, 2026 - added a commit that references this issue
on Mar 10, 2026 - added a commit that references this issue
on Mar 11, 2026 - added a commit that references this issue
on Mar 13, 2026
Metadata
Metadata
Assignees
Labels
area:helm-chartAirflow Helm ChartAirflow Helm Chartkind:featureFeature RequestsFeature Requestsneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yet
Description
No response
Use case/motivation
Presently its not possible to annotate airflow pods with helm checksums of the dependent secrets/configmaps so that when the secrets/configmaps change then the airflow control plane pod (scheduler, api server or dag processor) automatically restart with the updated dependent secret/configmap. The reason is because the chart does not support tpl evaluations from values yaml in these sections.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct