Cherry-pick #18882 to 7.x: Add better handling for Kubernetes Update and Delete watcher events #19232
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.
Cherry-pick of PR #18882 to 7.x branch. Original message:
Improvements for #11834 described on #11834 (comment)
Changes:
Retry on configCheck failures in order to cover stop/start events.Update
events when status of Pod isPending
.delete
anywayeven if the obj cannot be found in the
store` atbeats/libbeat/common/kubernetes/watcher.go
Line 202 in 95626b8