Support systemd OSs

[flah00]

I'm running kubernetes on CoreOS, none of the paths in sources.kubernetes or sources.docker exist on my system. I've been told that there's a systemd plugin for fluent. How can this be folded into the current image? Should we create a new env var, should it try to be smart?

[frankreno]

@flah00 : right now we only use the tail plugin. Do the logs not exist on the file system at all? Perhaps they are in a different path, in which case, you would just need to update the configuration and mounts to the appropriate path.

[flah00]

@frankreno The logs exist, but systemd uses a binary log format, so the resulting files aren't readable by the tail.

[flah00]

The plugin, for systemd, depends on libsystemd. Alpine doesn't offer any support for systemd. It seems like the fluent folks have settled on building two images, one debian and one alpine, to work around this problem. How does this project feel about that route?

[nhoughto]

This is a problem for all new GKE users as google is deprecating their debian based node image and moving to COS which uses systemd. What is the status of your poc @flah00 ?

[flah00]

I've got a working poc, which the sumo folks need to review.

[nhoughto]

Yep seems to work, i've got it deployed and both systemd and file mode are going for me. Thanks for your work.

[philipbjorge]

@nhoughto -- Do you have 2 daemonsets deployed to get both file logs and systemd logs?

[nhoughto]

Hmm nope just systemd since all my nodes are running a systems host OS (GKE COOS). Am I missing some logs by not doing both?

…

On 1 Aug 2017, 4:22 AM +1000, Philip Bjorge ***@***.***>, wrote: @nhoughto -- Do you have 2 daemonsets deployed to get both file logs and systemd logs? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[philipbjorge]

@nhoughto -- Not sure. It seems like on our kops nodes, the kubelet logs are going to journald, so was wondering if you had to handle something similar.