Skip to content

[v3-2-test] Fix pod_override serialization in DAG details and executor path (#65407)#66898

Open
vatsrahul1001 wants to merge 1 commit into
v3-2-testfrom
backport-322-65407
Open

[v3-2-test] Fix pod_override serialization in DAG details and executor path (#65407)#66898
vatsrahul1001 wants to merge 1 commit into
v3-2-testfrom
backport-322-65407

Conversation

@vatsrahul1001
Copy link
Copy Markdown
Contributor

@vatsrahul1001 vatsrahul1001 commented May 14, 2026

Cherry-pick of #65407


Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Opus 4.7)

Generated-by: Claude Code (Opus 4.7) following the guidelines

Sanitize default_args["executor_config"]["pod_override"] in DAG
details responses without changing other default_args values,
and make V1Pod serialization force the Kubernetes import path
so executor config no longer falls back to stringification.

This fixes two related Kubernetes serialization bugs: one where
the DAG details API could fail when pod_override was present in
default_args, and another where V1Pod objects could be flattened
into strings before reaching the Kubernetes executor. The updated
tests cover both the API response behavior and the serializer
regression with real Kubernetes pod objects.

(cherry picked from commit ff15983)
@vatsrahul1001 vatsrahul1001 added this to the Airflow 3.3.0 milestone May 14, 2026
@vatsrahul1001 vatsrahul1001 added the type:bug-fix Changelog: Bug Fixes label May 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:API Airflow's REST/HTTP API area:DAG-processing type:bug-fix Changelog: Bug Fixes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants