kimminw00 opened a new issue, #34298:
URL: https://github.com/apache/airflow/issues/34298
### Official Helm Chart version
1.10.0 (latest released)
### Apache Airflow version
2.6.3
### Kubernetes Version
1.24.10
### Helm Chart configuration
```yaml
cleanup:
enabled: true
securityContexts:
container:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
```
### Docker Image customizations
No
### What happened
Although securityContext value of the cleanup container was set in the
values.yaml file, the value was not set in container.
### What you think should happen instead
_No response_
### How to reproduce
```bash
helm template airflow . --set cleanup.enabled=true --set
cleanup.securityContexts.container.allowPrivilegeEscalation=false | grep "#
Source: airflow/templates/cleanup/cleanup-cronjob.yaml" -A100
```
### Anything else
There is no <code>containerSecurityContext</code> in cleanup-cronjob.yaml.
https://github.com/apache/airflow/blob/eed2901e877b32a211e0e74bc9d69fc11e552f2a/chart/templates/cleanup/cleanup-cronjob.yaml#L23-L28C6
But we can see <code>containerSecurityContext</code> in
webserver-deployment.yaml
https://github.com/apache/airflow/blob/eed2901e877b32a211e0e74bc9d69fc11e552f2a/chart/templates/webserver/webserver-deployment.yaml#L29C1-L29C1
### 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]
