Improve doc for containerd/cri-o setup #1485
Open
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
Avoid lots of time to look at fluent#434 and fluent#571 Signed-off-by: Sébastien P <[email protected]>
|
This PR has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this PR will be closed in 30 days |
|
Hi robot, just waiting an answer. PR is still ready forme. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi,
I have just started to deploy EFK for an internal K3S in my company.
We meet issues like:
[in_tail_container_logs] pattern not matched;[in_tail_container_logs] *** invalid time format.These issues are known as #434 and #571 and deserve a better documentation for developers. I spent around 2hours yesterday to read/understand/test.
That's why I propose this PR to update README.md and Elastic/OS examples.