[v3-3-test] Decide pod_template and image based on Coordinator for lang-SDK tasks on KubernetesExecutor (#68713)#69536
Merged
jason810496 merged 1 commit intoJul 7, 2026
Conversation
… on KubernetesExecutor (apache#68713)
Member
Author
|
This seems to be something that blocks #69532 |
jason810496
approved these changes
Jul 7, 2026
jason810496
left a comment
Member
There was a problem hiding this comment.
Ah, yes this is one of the version-aware example I mentioned.
I will make this reference upstream/main as follow up.
potiuk
approved these changes
Jul 7, 2026
1 task
Member
|
The only fail CI (chicken-egg problem, we have to merge this PR to solve this CI failure) to I will merge this right away. |
Contributor
|
Hi maintainer, this PR was merged without a milestone set.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.