Inspect container state rather than last_state when deciding whether to skip #33702
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.
closes: #33697
Looking at the Kubernetes API Docs for containerStatus, it looks like
lastState
provides the state of the previous run of the container, whereasstate
should provide information on the most recent termination (which is the relevant one in this case)I also added an integration test under
kubernetes_tests
to verify that this works as expected.