-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add better handling for Kubernetes Update and Delete watcher events #18882
Conversation
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Pinging @elastic/integrations-platforms (Team:Platforms) |
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Reverted checks for input realted errors handling (see content 078c279). @exekias @jsoriano what do you think about adding these changes for now since we have found them, regardless of what we do for input related issues(maybe we need to wait for inputs' refactoring in order to completely resolve 11834). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree on adding these changes now that we can see that they can improve the situation. Added a couple of small suggestions.
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Thanks for the suggestions @jsoriano!, PR updated. |
Signed-off-by: chrismark <chrismarkou92@gmail.com>
…lastic#18882) (cherry picked from commit d573e8c)
…lastic#18882) (cherry picked from commit d573e8c)
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