Charts: [stable/fluentd] stop enforcing elasticsearch as standart output

Created on 28 Jun 2019  路  6Comments  路  Source: helm/charts

This chart uses the 'fluentd-elasticsearch' docker image.
These image and chart don't allow to use other input / output plugins when they are not built-in with basic fluentd. I'm thinking about the list of available plugin to download and install via (fluent-)gem CLI.

For example, if I want to use the plugin 'fluent-plugin-amqp', I have start from scratch, ie. from the official fluent/fluentd image, gem install this plugin, then I have to build my own Helm chart.
That's not what I was expecting when I first saw this stable/fluentd chart. This one should replace the current stable/fluentd-elasticsearch, as this latter is now deprecated.

So, I think this fluent chart should not be so much opinionated with elasticsearch and let people use other plugins easily.

Maybe I'm missing something, let me know.

lifecyclstale

Most helpful comment

Well, this is what I actually did.
I was just not expecting so strong relationship with elasticsearch, given the name of this chart.

Also, still in my case, I have an output with the "file" plugin. So I'm transforming this deployment into a statefulset.
Good luck to everyone in similar situation.

All 6 comments

If I am understanding you correctly, you should be able to create a "drop-in replacement" docker image and overwrite .Values.image.repository. You will still need to replace some of the elasticsearch-specific configuration, but at least you get the rest of the stuff without having to start from scratch.

Well, this is what I actually did.
I was just not expecting so strong relationship with elasticsearch, given the name of this chart.

Also, still in my case, I have an output with the "file" plugin. So I'm transforming this deployment into a statefulset.
Good luck to everyone in similar situation.

FWIW, I do agree that this chart should probably be renamed to better convey it's tight coupling with Elasticsearch, maybe if I have some time I can create a PR.

The chart becomes a lot less useful when it can't auto install plugins.
Even if your backend is elasticsearch there are numerous other plugins (Thousands). for input and output that one one would still want to use to integrate everything.
Why not just add some code to allow for plugin install when the container launches.
Other charts do this kind of thing. I guess this is a bit dependant on the image though.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

This issue is being automatically closed due to inactivity.

Was this page helpful?
0 / 5 - 0 ratings