andscoop opened a new issue, #27577: URL: https://github.com/apache/airflow/issues/27577
### Description I've been researching how one can template out the pod-template.yaml. Airflow provides a few control points for this but none of them seem quite right for our use case - Helm charts: our k8s environment does not support helm - pod overrides: called for every pod creation, requires existing defaults and extends some fields instead of overwriting We're currently "templating" via `sed` find and replace at service start time. This works fine, but it is not as elegant as I think it could be. ### Use case/motivation Not all kubernetes environments support helm. Additionally, since the K8sExecutor is responsible for pod creation, it should have the ability to render templates closer to pod creation. This would allow for a single jinja templated `pod-template.yaml` file to be reused across multiple pipeline clusters or in multi-cluster deployments environments. If I am missing something, please point me in the right direction. Thanks! ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] 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]
