jedcunningham commented on PR #34633: URL: https://github.com/apache/airflow/pull/34633#issuecomment-1934466574
Hey @Leoduv! The documentation is right. You can use KPO, regardless of what executor you choose. KubernetesPodOperator doesn't use the KubernetesExecutor pod_template_file, the one pointed to with [this config](https://airflow.apache.org/docs/apache-airflow-providers-cncf-kubernetes/stable/configurations-ref.html#pod-template-file). That pod_template_file, and the one `podTemplate` in the chart controls, is only used by KubernetesExecutor (at least by default :sweat_smile:). > (FYI it is possible that we are just in a niche use case because we are helm-templating our pod templates, so we can't just add them in the dag folder or something like that) Yeah, kinda, I'd say that's the case unfortunately. Not that you want to template the KE pod_template_file, but that you want to have an extra templated yaml file that so happens to also be a pod template. One option would be to use the OSS chart as a subchart and put your KPO pod template into a configmap yourself. Another would be to move the stuff requiring templating into pod_mutation_hook, which you can template via the charts `airflowLocalSettings`. -- 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]
