Re: [I] Launch Pod/job in separate namespace and support in helm chart [airflow]

["Miretpl (via GitHub)" <gi...@apache.org>]

Miretpl commented on issue #25222:
URL: https://github.com/apache/airflow/issues/25222#issuecomment-2790804363

   Hi, I can work on this issue if no one is interested.
   
   I would like to ask one question before I will start working on it: if I understand correctly how Airflow and the current implementation of the Helm Chart work it is not possible to support the creation of Airflow job pods in multiple different namespaces - it would require the change in the KubernetesExecutor itself, but a separation of Airflow core services like scheduler, webserver, triggerer, etc. from the pods of Task Instances would require only change in the Helm Chart (probably the addition of the flag under the workers configuration), right? If I'm missing something, please let me know.
   
   Also @mikebell90 and @tomastoggle, could you elaborate if simple separation of core Airflow components from jobs would meet your requirements?


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org