Fix pod_override serialization in DAG details and executor path

[ephraimbuddy]

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.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  Generated-by: claude sonnet 4.6

closes: #57743

[jason810496]

Thanks for the fix, LGTM overall.

[Copilot]

Pull request overview

Fixes Kubernetes V1Pod (pod_override) serialization issues affecting both the DAG details FastAPI response and Airflow’s internal serialization path, preventing API 500s and avoiding accidental stringification before the Kubernetes executor consumes the config.

Changes:

• Sanitize default_args["executor_config"]["pod_override"] in DAGDetailsResponse to avoid Pydantic serialization failures.
• Ensure BaseSerialization.serialize() forces a Kubernetes import attempt when encountering V1Pod, so it serializes to a structured dict instead of falling back to str().
• Add unit tests covering the DAG details API behavior and the V1Pod serialization regression.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
airflow-core/src/airflow/api_fastapi/core_api/datamodels/dags.py	Adds default_args sanitizer for executor_config.pod_override to keep DAG details responses JSON-serializable.
airflow-core/src/airflow/serialization/serialized_objects.py	Forces _has_kubernetes(attempt_import=True) for V1Pod serialization to avoid stringification.
airflow-core/tests/unit/api_fastapi/core_api/routes/public/test_dags.py	Adds a DAG details endpoint test asserting pod_override is sanitized in the response.
airflow-core/tests/unit/api_fastapi/core_api/datamodels/test_dags.py	Adds unit tests for _sanitize_pod_override and the default_args validator.
airflow-core/tests/unit/serialization/test_serialized_objects.py	Adds regression test ensuring V1Pod serialization triggers _has_kubernetes(attempt_import=True).

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

[Lee-W]

I think we're good to merge it after resolving the conflict. thanks!

[github-actions]

Hi maintainer, this PR was merged without a milestone set.
We've automatically set the milestone to Airflow 3.2.2 based on: backport label targeting v3-2-test
If this milestone is not correct, please update it to the appropriate milestone.

This comment was generated by Milestone Tag Assistant.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-2-test

You can attempt to backport this manually by running:

cherry_picker ff15983 v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.