-
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
Use CRI paths in kubernetes manifests #12632
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
exekias
added
enhancement
in progress
Pull request is currently in progress.
needs_backport
PR is waiting to be backported to other branches.
Team:Integrations
Label for the Integrations team
v7.2.0
labels
Jun 21, 2019
Note: I'm still in the process of testing this |
exekias
added
review
and removed
in progress
Pull request is currently in progress.
labels
Jun 21, 2019
We added a new `container` input in elastic#12162, this change makes use of it to read logs from their CRI paths. Making Filebeat work with deployments that are not using Docker runtime.
exekias
force-pushed
the
manifests_use_cri_paths
branch
from
June 21, 2019 15:01
ec175d3
to
6b41d99
Compare
Tested this with |
jsoriano
approved these changes
Jul 1, 2019
exekias
pushed a commit
to exekias/beats
that referenced
this pull request
Jul 1, 2019
We added a new `container` input in elastic#12162, this change makes use of it to read logs from their CRI paths. Making Filebeat work with deployments that are not using Docker runtime. (cherry picked from commit 4933680)
exekias
added
v7.2.1
and removed
needs_backport
PR is waiting to be backported to other branches.
labels
Jul 1, 2019
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…ts (elastic#12742) * Use CRI paths in kubernetes manifests (elastic#12632) We added a new `container` input in elastic#12162, this change makes use of it to read logs from their CRI paths. Making Filebeat work with deployments that are not using Docker runtime. (cherry picked from commit 32c3b21) * Update CHANGELOG.next.asciidoc
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
We added a new
container
input in #12162, this change makes use of itto read logs from their CRI paths. Making Filebeat work with deployments that
are not using Docker runtime.