[KubernetesPodOperator] Added detection of terminated pod during reattach #51158
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
During working with the KubernetesPodOperator we found the issue that sometimes the POD was already in terminated state and then KubernetesPodOperator tries to reconnect to this pod. But if the xcom sidecar is not running any more it makes no sense to work with this pod. Idea is to check if the pod is terminated then then delete the POD and create a new POD to run the task.
Details of change: