Ensure deletion of pods is handled #2784
Merged
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.
/kind bug
When a watch pod deletion event was missed while disconnected from apiserver, delta fifo in informer will generate a new delete event, and a
DeletedFinalStateUnknown
obj will be enqueue and reprocessed, here is this logic:https://github.com/kubernetes/kubernetes/blob/297dc976b96895332f8e800c531f47d5cca68bfd/staging/src/k8s.io/client-go/tools/cache/delta_fifo.go#L665
We have considered the case in
DeletePod
event handler:volcano/pkg/scheduler/cache/event_handlers.go
Line 269 in bed4a04