Unique tags for docker images about fluentd-kubernetes-daemonset

[ritasker]

This has also caused me issues today.
A node on GKE was restarted last night and fluentd wont start on that node.
With a different error though
sed: can't move '/fluentd/etc/fluent.confPHNfhN' to '/fluentd/etc/fluent.conf': Resource busy.

[edsiper]

the enhancement request for tagging is associated to #53

would you please log into the Fluentd container that's working now and send us the output of the following command:

$ gem list fluent-plugin-kubernetes_metadata_filter

since I see a permission issue when accessing the API server and the newer images likely picked an updated version of the filter, I would like to check the main differences.

[gtrafimenkov]

@edsiper , here is the output:

# gem list fluent-plugin-kubernetes_metadata_filter

*** LOCAL GEMS ***

fluent-plugin-kubernetes_metadata_filter (0.29.0)

[mihailgmihaylov]

Hello,

We are using your fluentd-kubernetes-daemonset:v0.12-alpine-elasticsearch image which we pull from https://hub.docker.com/r/fluent/fluentd-kubernetes-daemonset/builds/ .
Long time ago, we had an issue in which a change in the underlying image that the fluentd-kubernetes-daemonset alpine image depends on was changed and the change was backported into the image with tag v0.12-alpine-elasticsearch.
Yesterday, we had maybe the same issue in which all new instances of the containers had a configurational issue. The image name and tag was not change and this creates a inconsistency in our infrastructure.

Although, we appreciate the service and that you create and store the docker images for us, I was wondering if there you can somehow add an incremental tag on the image tag so that you are still able to backport new functionalities into the old versions of fluentd but have the ability for us to opt-out of them.

For example: fluentd-kubernetes-daemonset:v0.12-alpine-elasticsearch-1.23.4 or something similar.

[repeatedly]

Forgot to close. This issue has been resolved.