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.

Sign up for GitHub

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

Jump to bottom

Create Fluentd image that can be easily used as a sidecar container for collecting log files #7006

Closed
a-robinson opened this issue Apr 17, 2015 · 3 comments · Fixed by #7149
Closed

Create Fluentd image that can be easily used as a sidecar container for collecting log files #7006

a-robinson opened this issue Apr 17, 2015 · 3 comments · Fixed by #7149
Assignees
@a-robinson
Labels
priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@a-robinson
Copy link
Contributor

We should provide a dockerfile for a pre-configured Fluentd image that can be passed file paths to collect logs from. We'll likely want one for exporting to elasticsearch and one for exporting to Google Cloud Logging, as we have today for the per-node stdout/stderr collectors.

How to collect log files from within a container is a question that comes up occasionally (including a couple days ago), and it provides a strong example of the usefulness of sidecar containers.

cc @satnam6502 @mr-salty
@a-robinson a-robinson added priority/backlog Higher priority than priority/awaiting-more-evidence. team/cluster labels Apr 17, 2015
@satnam6502
Copy link
Contributor

A controller that keeps one instance of a pod alive on each node would be useful for this. Shall I go ahead and write such a controller?

@a-robinson
Copy link
Contributor Author

Would it be? This is intended to run as a sidecar container in a pod with the user's actual application. I think a pod-per-node controller is orthogonal (and is being discussed in #1518 and #3058).

I'll create the actual Dockerfile, and a quick example of how to use it.

@a-robinson a-robinson self-assigned this Apr 18, 2015
@satnam6502
Copy link
Contributor

Sorry, my rush to catch up I think I mis-understood this thread.

@a-robinson a-robinson mentioned this issue Apr 22, 2015
Merged
@a-robinson a-robinson mentioned this issue Apr 23, 2015
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@a-robinson a-robinson

Labels
priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
2 participants
@satnam6502 @a-robinson