-
Notifications
You must be signed in to change notification settings - Fork 980
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
Add debian based images #12
Conversation
853c4c1
to
c20a15c
Compare
The 1st commit updates the Makefile + templates, the 2nd commit is the result of re-running The 3rd commit updates the Makefile + templates to install and configure the systemd plugin for debian images. |
I've got the ES debian image built here: https://quay.io/repository/coreos/fluentd-kubernetes?tab=tags in case you would like to try/look. I've tested this on my Kubernetes cluster and it works great so far. I'm seeing systemd logs, and fluentd is running as expected. |
@so0k @c-knowles : since you helped to put in place #4, would you please help to review these changes ? |
I'll have a look |
Sorry, didn't have time yet to review - glancing over https://github.com/coreos/fluentd-kubernetes-daemonset/tree/add_debian_image - seems README is not updated yet? |
0f04bab
to
b95edcc
Compare
@so0k Updated the README. |
Thanks @chancez - I've merged your changes to my fork (which has automated docker hub builds as well...). Unfortunately, relative links in the Apart from that, LGTM. @edsiper - when these changes are merged, it is needed to update the build settings on the Docker Hub repository as follows:
Final result looks like: NOTE: I Have a typo in the screenshot above (should be EDIT: Added clarification on typo in Screenshot |
@so0k I can update the URLs then. One moment. |
I removed the last commit which used relative URLs. I think it should be correct now. (Urls will be broken since the locations of files changed, and the links point to master). |
@edsiper - I believe this can be merged (as well as need to update the docker hub builds) |
thanks for the review. @so0k how the build settings should looks like ? |
There's a picture here but small mistake, see note |
what do you think about to get rid of Alpine based images ? @chancez I see the Alpine images don't use Jemalloc, to support Alpine we need Jemalloc on it, otherwise memory fragmentation on Fluentd side will be high. |
@edsiper I didn't touch alpine, so that's irrelevant to this PR IMO. |
@chancez actually this PR adds Alpine based images:
|
@edsiper no, it merely moves the existing alpine generated files to a different directory structure to accommodate multiple base images. The current images use alpine, I'm adding debian. |
Thanks for the clarification, my fault! |
@chancez would you please check the conflict ?, once fixed I will merge it. |
…mages Note: this changes directory structure, so automated builds need to be updated to handle the new names of the folders.
…ian based images.
#20 merged |
@edsiper Rebased. |
I can fix readme links and loook into alpine issues after this is merged |
@edsiper are you referring to this https://bugs.alpinelinux.org/issues/5389? |
@so0k that one and others. Personally I have to stop working with Alpine with https://github.com/fluent/fluent-bit because of jemalloc and other Musl compatibility issues. |
Also adds the fluentd-plugin-systemd gem + config for debian based images
Note that this PR changes the folder layout in
docker-images/
, so it mayrequire updating automated docker builds if it depends on the folder structure.