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
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