KubernetesPodOperator check xcom sidecar running before trying to read xcom #60319
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.
Overview
We observed Kubernetes API errors in KubernetesPodOperator when a pod is evicted. In this state the xcom sidecar container has already terminated, so exec/read attempts fail. The previous exception did not clearly indicate that the sidecar was no longer running, making it hard to understand why no XCom output could be read. The new exception message explicitly states that the sidecar is not running, clarifying why XCom retrieval failed.
Change Summary