jason810496 opened a new pull request, #68713:
URL: https://github.com/apache/airflow/pull/68713

   - Depends on #68694. Stacked on top of it.
   - **Early-review diff (this PR's changes only, without #68694):**
   - 
https://github.com/jason810496/airflow/compare/feature/lang-sdk/coordinator-pod-template-file...feature/lang-sdk/k8s-coordinator-pod-template-file
   
   ## Why
   
   A queue routed to a non-Python coordinator (`[sdk] queue_to_coordinator`) 
needs a worker pod whose image carries that runtime (e.g. the JVM for a Java 
coordinator), but the KubernetesExecutor had no way to pick a 
coordinator-specific pod template or base image short of setting 
`executor_config` on every task.
   
   ## What
   
   - Add `KubernetesExecutor._coordinator_pod_template_file` (reads 
`pod_template_file` from `extra`, import-guarded for 3.3+) and apply it with 
**precedence over `executor_config`** in `execute_async`.
     - `pod_template_file` -- applied with precedence over per-task 
`executor_config` (a queue's coordinator carries the runtime requirement, so it 
must win). Python queues resolve to `None` and are unaffected.
     - `worker_container_repository` + `worker_container_tag` -- compose a 
per-queue base image (both required), since the base image is never carried by 
a pod template. Plumbed through `KubernetesJob.kube_image` to the pod request.
   - A malformed `[sdk]` config is logged and ignored rather than crashing the 
scheduler.
   
   ## Next
   
   - https://github.com/apache/airflow/pull/68709
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [x] Yes, with help of Claude Code (Opus 4.8) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   


-- 
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]

Reply via email to