jeff-cook opened a new issue, #62146:
URL: https://github.com/apache/airflow/issues/62146

   ### Official Helm Chart version
   
   1.19.0 (latest released)
   
   ### Apache Airflow version
   
   3.1.7
   
   ### Kubernetes Version
   
   v1.33.7-eks-ac2d5a0
   
   ### Helm Chart configuration
   
   Can duplicate issue with default `values.yaml` file.
   
   ### Docker Image customizations
   
   None
   
   ### What happened
   
   Not all manifests include `checksum/jwt-secret` annotation. This means when 
this value is updated the pods will not automatically be recreated. 
   
   I show following files use the secret with including the checksum annotation.
    
   - `dag-processor/dag-processor-deployment.yaml`
   - `triggerer/triggerer-deployment.yaml`
   - `workers/worker-deployment.yaml`
   
   The following jobs also don't have the annotation, but not sure it's an 
issue, due to it being a job. 
   
   - `jobs/migrate-database-job.yaml`
   - `jobs/create-user-job.yaml`
   
   ### What you think should happen instead
   
   A `Deployment` and `StatefulSet` that use the `jwt-secret` `Secret` should 
include `spec.template.metadata.annotation.checksum/jwt-secret`
   
   ### How to reproduce
   
   Run in the `chart/`
   
   ```
   helm template . --output-dir tmp 
   find tmp/ -type f | xargs grep jwt-secret
   ```
   
   This will show all the places the `jwt-secret` is used and where the 
`checksum/jwt-secret` annotation is. 
   
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to