Skip to content
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

Fix cleanup when autodiscover pods are terminated #14259

Conversation

jsoriano
Copy link
Member

In some cases pods termination doesn't originate a delete event in the
API watchers. Detect termination also by checking if a deletion
timestamp exists in update events.

In some cases pods termination doesn't originate a delete event in the
API watchers. Detect termination also by checking if a deletion
timestamp exists in update events.
@jsoriano jsoriano added needs_backport PR is waiting to be backported to other branches. v7.4.2 v7.5.0 labels Oct 26, 2019
@jsoriano
Copy link
Member Author

Similar change will be needed in add_kubernetes_metadata.

@jsoriano
Copy link
Member Author

Added changes to add_kubernetes_metadata too.

@exekias
Copy link
Contributor

exekias commented Oct 28, 2019

very good catch here @jsoriano!

@jsoriano jsoriano merged commit 1c36118 into elastic:master Oct 28, 2019
@jsoriano jsoriano deleted the kubernetes-autodiscover-handle-pod-termination branch October 28, 2019 10:04
jsoriano added a commit to jsoriano/beats that referenced this pull request Oct 28, 2019
In some cases pods termination doesn't originate a delete event in the
API watchers. Detect termination also by checking if a deletion
timestamp exists in update events.

(cherry picked from commit 1c36118)
@jsoriano jsoriano removed the needs_backport PR is waiting to be backported to other branches. label Oct 28, 2019
jsoriano added a commit to jsoriano/beats that referenced this pull request Oct 28, 2019
In some cases pods termination doesn't originate a delete event in the
API watchers. Detect termination also by checking if a deletion
timestamp exists in update events.

(cherry picked from commit 1c36118)
jsoriano added a commit that referenced this pull request Oct 28, 2019
…minated (#14265)

In some cases pods termination doesn't originate a delete event in the
API watchers. Detect termination also by checking if a deletion
timestamp exists in update events.

(cherry picked from commit 1c36118)
jsoriano added a commit that referenced this pull request Nov 5, 2019
In some cases pods termination doesn't originate a delete event in the
API watchers. Detect termination also by checking if a deletion
timestamp exists in update events.

(cherry picked from commit 1c36118)
jorgemarey pushed a commit to jorgemarey/beats that referenced this pull request Jun 8, 2020
In some cases pods termination doesn't originate a delete event in the
API watchers. Detect termination also by checking if a deletion
timestamp exists in update events.
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…are terminated (elastic#14265)

In some cases pods termination doesn't originate a delete event in the
API watchers. Detect termination also by checking if a deletion
timestamp exists in update events.

(cherry picked from commit 9de0061)
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…astic#14268)

In some cases pods termination doesn't originate a delete event in the
API watchers. Detect termination also by checking if a deletion
timestamp exists in update events.

(cherry picked from commit 9de0061)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants