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

Cherry-pick #5084 to 6.0: Keep docker & k8s pod annotations while they are needed #5133

Merged
merged 1 commit into from
Sep 8, 2017

Conversation

exekias
Copy link
Contributor

@exekias exekias commented Sep 8, 2017

Cherry-pick of PR #5084 to 6.0 branch. Original message:

In some cases pod annotations are neede after the container/pod is deleted, for
instance when filebeat is reading the log behind the container.

This change makes sure we keep metadata after a pod is gone. By storing
access times we ensure that it's available as long as it's being used

fixes #4986

In some cases pod annotations are neede after the pod is deleted, for
instance when filebeat is reading the log behind the container.

This change makes sure we keep metadata after a pod is gone. By storing
access times we ensure that it's available as long as it's being used
(cherry picked from commit a49463c)
@tsg tsg merged commit 53bffc1 into elastic:6.0 Sep 8, 2017
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
elastic#5133)

In some cases pod annotations are neede after the pod is deleted, for
instance when filebeat is reading the log behind the container.

This change makes sure we keep metadata after a pod is gone. By storing
access times we ensure that it's available as long as it's being used
(cherry picked from commit d24a88a)
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