o-nikolas commented on PR #49433: URL: https://github.com/apache/airflow/pull/49433#issuecomment-2825531848
I'd push back on this, perhaps I need to hear more about how Helm is operating differently than a normal airflow deployment. But in normal cases Airlfow expects to operate with the same configuration on all hosts (until multi-team of course). If a pod is being started as a result of an executor triggering a pod to run a task, the core.executor field will not do anything. In AF2 the `airflow tasks run ...` command will use the LocalTaskRunner, or in AF3 a workload will be executed via the correct execution_time module. If the context is something else than the above, I'd need to hear more. -- 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-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
