fix(kubernetes): do not fail task when xcom sidecar kill fails after successful XCom read

[waterWang]

Issue

Closes #71369

Problem

When KubernetesPodOperator is used with do_xcom_push=True, the XCom sidecar container starts and the XCom value is read successfully from /airflow/xcom/return.json. However, the subsequent extract_xcom_kill step attempts to terminate the sidecar via kill -2 over kubectl exec, which fails with Permission denied on certain container runtimes (e.g., k3s/containerd).

Because extract_xcom_kill is called in the finally block of extract_xcom, the PodCommandException propagates and discards the already-retrieved XCom value, causing the task to be marked as Failed despite the payload being successfully read.

Fix

Wrap extract_xcom_kill in an inner try/except in the finally block. Since the XCom value has already been successfully retrieved, a failure to clean up the sidecar is a non-fatal issue — the sidecar will be cleaned up when the pod is deleted (per on_finish_action). The exception is logged as a warning instead of failing the task.

Test

Added test_extract_xcom_kill_failure_does_not_fail_task which verifies that when extract_xcom_kill raises PodCommandException, the extract_xcom method still returns the successfully-read XCom value.

[kaxil]

Closing this as part of a cleanup of a large batch of PRs opened in quick succession from this account.

18 PRs have been opened here in the past two weeks and none have merged. Several show signs of being generated and submitted without review: #71432 and #71433 are the same change across the same five files, opened two minutes apart, and several titles carry a leaked agent identifier that other contributors already flagged as garbled text on #70629 and #71322.

Airflow is maintained by volunteers. Every PR costs reviewer time and CI capacity, so a high volume of unvetted submissions has a real cost to the project.

You are welcome to keep contributing. Please open one change at a time, run it locally against the tests, and read the contributors' guide before submitting. If you think a specific change here is correct, comment with the reasoning and a maintainer can reopen it.

[vinay-kumar-uppala]

@waterWang I am testing with the above suggested changes.