Fix deferred mode KubernetesPodOperator: fast-fail pod start errors (ErrImagePull/ImagePullBackOff) #59010
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 found an issue with deferred mode and ErrImagePull handling. When the Triggerer emits an error event and the pod enters ErrImagePull, the KubernetesPodOperator continues waiting in await_pod_completion even though the pod will never start (image does not exist). This PR applies the same fast-fail logic used during startup to await_pod_completion, aborting the wait when image pull errors are detected. It also includes ImagePullBackOff so long check intervals don’t cause unnecessary retries and timeouts.
Change Summary