base on Fluentd daemonset for Kubernetes and it Docker image # Fluentd Daemonset for Kubernetes > [!CAUTION] > README.md is generated from templates/README.md.erb [](https://hub.docker.com/r/fluent/fluentd-kubernetes-daemonset) [](https://hub.docker.com/r/fluent/fluentd-kubernetes-daemonset) [](https://hub.docker.com/r/fluent/fluentd-kubernetes-daemonset) [](https://hub.docker.com/r/fluent/fluentd-kubernetes-daemonset) ## Supported tags and respective `Dockerfile` links See also dockerhub tags page: https://hub.docker.com/r/fluent/fluentd-kubernetes-daemonset/tags ### Debian #### Current stable > [!TIP] > Since v1.17.0, the container image build process has been migrated from automated builds on hub.docker.com to GitHub Actions. > This is because there were limitation about the number of automated builds on hub.docker.com. > Now, there is no limitation about the number of build pipelines. > > Note that there were some restrictions to ship daemonset images for v1.16.5 or older ones before: > * `papertrail`, `syslog` images (x86_64/arm64) won't be published anymore > * `logentries`, `loggly`, `logzio`, `s3` arm64 images won't be published anymore (x86_64 only supported) > If you want to use above non published images, build it by yourself. Dockerfile itself is still maintained in this repository. ##### Multi-Arch images - `Azureblob` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-azureblob-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-azureblob-1` - `Elasticsearch8` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-elasticsearch8-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-elasticsearch8-1` - `Elasticsearch7` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-elasticsearch7-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-elasticsearch7-1` - `docker pull fluent/fluentd-kubernetes-daemonset:v1-debian-elasticsearch` - `Opensearch` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-opensearch-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-opensearch-1` - `Cloudwatch` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-cloudwatch-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-cloudwatch-1` - `Forward` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-forward-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-forward-1` - `Gcs` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-gcs-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-gcs-1` - `Graylog` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-graylog-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-graylog-1` - `Kafka` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-kafka-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-kafka-1` - `Kafka2` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-kafka2-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-kafka2-1` - `Kinesis` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-kinesis-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-kinesis-1` ##### x86_64 images - `Azureblob` [Dockerfile](docker-image/v1.18/debian-azureblob/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-azureblob-amd64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-azureblob-amd64-1` - `Elasticsearch8` [Dockerfile](docker-image/v1.18/debian-elasticsearch8/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-elasticsearch8-amd64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-elasticsearch8-amd64-1` - `Elasticsearch7` [Dockerfile](docker-image/v1.18/debian-elasticsearch7/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-elasticsearch7-amd64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-elasticsearch7-amd64-1` - `docker pull fluent/fluentd-kubernetes-daemonset:v1-debian-elasticsearch-amd64` - `Opensearch` [Dockerfile](docker-image/v1.18/debian-opensearch/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-opensearch-amd64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-opensearch-amd64-1` - `Loggly` [Dockerfile](docker-image/v1.18/debian-loggly/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-loggly-amd64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-loggly-amd64-1` - `Logentries` [Dockerfile](docker-image/v1.18/debian-logentries/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-logentries-amd64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-logentries-amd64-1` - `Cloudwatch` [Dockerfile](docker-image/v1.18/debian-cloudwatch/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-cloudwatch-amd64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-cloudwatch-amd64-1` - `S3` [Dockerfile](docker-image/v1.18/debian-s3/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-s3-amd64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-s3-amd64-1` - `Syslog` [Dockerfile](docker-image/v1.18/debian-syslog/Dockerfile) - `Forward` [Dockerfile](docker-image/v1.18/debian-forward/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-forward-amd64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-forward-amd64-1` - `Gcs` [Dockerfile](docker-image/v1.18/debian-gcs/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-gcs-amd64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-gcs-amd64-1` - `Graylog` [Dockerfile](docker-image/v1.18/debian-graylog/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-graylog-amd64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-graylog-amd64-1` - `Papertrail` [Dockerfile](docker-image/v1.18/debian-papertrail/Dockerfile) - `Logzio` [Dockerfile](docker-image/v1.18/debian-logzio/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-logzio-amd64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-logzio-amd64-1` - `Kafka` [Dockerfile](docker-image/v1.18/debian-kafka/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-kafka-amd64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-kafka-amd64-1` - `Kafka2` [Dockerfile](docker-image/v1.18/debian-kafka2/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-kafka2-amd64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-kafka2-amd64-1` - `Kinesis` [Dockerfile](docker-image/v1.18/debian-kinesis/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-kinesis-amd64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-kinesis-amd64-1` ##### arm64 images - `Azureblob` [Dockerfile](docker-image/v1.18/arm64/debian-azureblob/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-azureblob-arm64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-azureblob-arm64-1` - `Elasticsearch8` [Dockerfile](docker-image/v1.18/arm64/debian-elasticsearch8/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-elasticsearch8-arm64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-elasticsearch8-arm64-1` - `Elasticsearch7` [Dockerfile](docker-image/v1.18/arm64/debian-elasticsearch7/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-elasticsearch7-arm64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-elasticsearch7-arm64-1` - `docker pull fluent/fluentd-kubernetes-daemonset:v1-debian-elasticsearch-arm64` - `Opensearch` [Dockerfile](docker-image/v1.18/arm64/debian-opensearch/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-opensearch-arm64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-opensearch-arm64-1` - `Loggly` [Dockerfile](docker-image/v1.18/arm64/debian-loggly/Dockerfile) - `Logentries` [Dockerfile](docker-image/v1.18/arm64/debian-logentries/Dockerfile) - `Cloudwatch` [Dockerfile](docker-image/v1.18/arm64/debian-cloudwatch/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-cloudwatch-arm64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-cloudwatch-arm64-1` - `S3` [Dockerfile](docker-image/v1.18/arm64/debian-s3/Dockerfile) - `Syslog` [Dockerfile](docker-image/v1.18/arm64/debian-syslog/Dockerfile) - `Forward` [Dockerfile](docker-image/v1.18/arm64/debian-forward/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-forward-arm64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-forward-arm64-1` - `Gcs` [Dockerfile](docker-image/v1.18/arm64/debian-gcs/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-gcs-arm64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-gcs-arm64-1` - `Graylog` [Dockerfile](docker-image/v1.18/arm64/debian-graylog/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-graylog-arm64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-graylog-arm64-1` - `Papertrail` [Dockerfile](docker-image/v1.18/arm64/debian-papertrail/Dockerfile) - `Logzio` [Dockerfile](docker-image/v1.18/arm64/debian-logzio/Dockerfile) - `Kafka` [Dockerfile](docker-image/v1.18/arm64/debian-kafka/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-kafka-arm64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-kafka-arm64-1` - `Kafka2` [Dockerfile](docker-image/v1.18/arm64/debian-kafka2/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-kafka2-arm64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-kafka2-arm64-1` - `Kinesis` [Dockerfile](docker-image/v1.18/arm64/debian-kinesis/Dockerfile) - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18.0-debian-kinesis-arm64-1.0` - `docker pull fluent/fluentd-kubernetes-daemonset:v1.18-debian-kinesis-arm64-1` You can also use `v1-debian-PLUGIN` tag to refer latest v1 image, e.g. `v1-debian-elasticsearch`. On production, strict tag is better to avoid unexpected update. See dockerhub's tags page for older tags. #### Old stable v0.12 development has been ended. These images are never updated. - `v0.12-debian-elasticsearch` [archived-image/v0.12/debian-elasticsearch/Dockerfile](archived-image/v0.12/debian-elasticsearch/Dockerfile) - `v0.12-debian-loggly` [archived-image/v0.12/debian-loggly/Dockerfile](archived-image/v0.12/debian-loggly/Dockerfile) - `v0.12-debian-logentries` [archived-image/v0.12/debian-logentries/Dockerfile](archived-image/v0.12/debian-logentries/Dockerfile) - `v0.12-debian-cloudwatch` [archived-image/v0.12/debian-cloudwatch/Dockerfile](archived-image/v0.12/debian-cloudwatch/Dockerfile) - `v0.12-debian-stackdriver` [archived-image/v0.12/debian-stackdriver/Dockerfile](archived-image/v0.12/debian-stackdriver/Dockerfile) - `v0.12-debian-s3` [archived-image/v0.12/debian-s3/Dockerfile](archived-image/v0.12/debian-s3/Dockerfile) - `v0.12-debian-gcs` [archived-image/v0.12/debian-gcs/Dockerfile](archived-image/v0.12/debian-gcs/Dockerfile) - `v0.12-debian-papertrail` [archived-image/v0.12/debian-papertrail/Dockerfile](archived-image/v0.12/debian-papertrail/Dockerfile) - `v0.12-debian-syslog` [archived-image/v0.12/debian-syslog/Dockerfile](archived-image/v0.12/debian-syslog/Dockerfile) - `v0.12-debian-graylog` [archived-image/v0.12/debian-graylog/Dockerfile](archived-image/v0.12/debian-graylog/Dockerfile) - `v0.12-debian-logzio` [archived-image/v0.12/debian-logzio/Dockerfile](archived-image/v0.12/debian-logzio/Dockerfile) - `v0.12-debian-kafka` [archived-image/v0.12/debian-kafka/Dockerfile](archived-image/v0.12/debian-kafka/Dockerfile) - `v0.12-debian-splunkhec` [archived-image/v0.12/debian-splunkhec/Dockerfile](archived-image/v0.12/debian-splunkhec/Dockerfile) - `v0.12-debian-kinesis` [archived-image/v0.12/debian-kinesis/Dockerfile](archived-image/v0.12/debian-kinesis/Dockerfile) ### Alpine Linux (This is deprecated. Use Debian images instead) - `v0.12-alpine-elasticsearch` [archived-image/v0.12/alpine-elasticsearch/Dockerfile](archived-image/v0.12/alpine-elasticsearch/Dockerfile) - `v0.12-alpine-loggly` [archived-image/v0.12/alpine-loggly/Dockerfile](archived-image/v0.12/alpine-loggly/Dockerfile) - `v0.12-alpine-logentries` [archived-image/v0.12/alpine-logentries/Dockerfile](archived-image/v0.12/alpine-logentries/Dockerfile) - `v0.12-alpine-cloudwatch` [archived-image/v0.12/alpine-cloudwatch/Dockerfile](archived-image/v0.12/alpine-cloudwatch/Dockerfile) - `v0.12-alpine-stackdriver` [archived-image/v0.12/alpine-stackdriver/Dockerfile](archived-image/v0.12/alpine-stackdriver/Dockerfile) - `v0.12-alpine-s3` [archived-image/v0.12/alpine-s3/Dockerfile](archived-image/v0.12/alpine-s3/Dockerfile) - `v0.12-alpine-gcs` [archived-image/v0.12/alpine-gcs/Dockerfile](archived-image/v0.12/alpine-gcs/Dockerfile) - `v0.12-alpine-papertrail` [archived-image/v0.12/alpine-papertrail/Dockerfile](archived-image/v0.12/alpine-papertrail/Dockerfile) - `v0.12-alpine-syslog` [archived-image/v0.12/alpine-syslog/Dockerfile](archived-image/v0.12/alpine-syslog/Dockerfile) - `v0.12-alpine-graylog` [archived-image/v0.12/alpine-graylog/Dockerfile](archived-image/v0.12/alpine-graylog/Dockerfile) - `v0.12-alpine-logzio` [archived-image/v0.12/alpine-logzio/Dockerfile](archived-image/v0.12/alpine-logzio/Dockerfile) - `v0.12-alpine-kafka` [archived-image/v0.12/alpine-kafka/Dockerfile](archived-image/v0.12/alpine-kafka/Dockerfile) - `v0.12-alpine-kinesis` [archived-image/v0.12/alpine-kinesis/Dockerfile](archived-image/v0.12/alpine-kinesis/Dockerfile) - `v0.12-alpine-splunkhec` [archived-image/v0.12/alpine-splunkhec/Dockerfile](archived-image/v0.12/alpine-splunkhec/Dockerfile) ## What is Fluentd?  Fluentd is an open source data collector, which lets you unify the data collection and consumption for a better use and understanding of data. > [www.fluentd.org](http://www.fluentd.org/) ## Image versions Fluentd versioning is as follows: | Series | Description | |--------|-------------------------------------| | v1.x | current stable | | v0.12 | Old stable, no longer updated | ## Settings ### Default image version Default YAML uses latest v1 images like `fluent/fluentd-kubernetes-daemonset:v1-debian-kafka`. If you want to avoid unexpected image update, specify exact version for `image` like `fluent/fluentd-kubernetes-daemonset:v1.8.0-debian-kafka-1.0`. ### Run as root This is for v0.12 images. In Kubernetes and default setting, fluentd needs root permission to read logs in `/var/log` and write `pos_file` to `/var/log`. To avoid permission error, you need to set `FLUENT_UID` environment variable to `0` in your Kubernetes configuration. ### Use your configuration These images have default configuration and support some environment variables for parameters but it sometimes doesn't fit your case. If you want to use your configuration, use ConfigMap feature. Each image has following configurations: - fluent.conf: Destination setting, Elaticsearch, kafka and etc. - kubernetes.conf: k8s specific setting. `tail` input for log files and `kubernetes_metadata` filter - tail_container_parse.conf: parser setting for `/var/log/containers/*.log`. See also "Use CRI parser for containerd/cri-o" logs section - prometheus.conf: prometheus plugin for fluentd monitoring - systemd.conf: systemd plugin for collecting systemd-journal log. See also "Disable systemd input" section. Overwrite conf file via ConfigMap. See also several examples: - [Cluster-level Logging in Kubernetes with Fluentd](https://medium.com/kubernetes-tutorials/cluster-level-logging-in-kubernetes-with-fluentd-e59aa2b6093a) - https://github.com/fluent/fluentd-kubernetes-daemonset/pull/349#issuecomment-579097659 ### Use CRI parser for containerd/cri-o logs This feature is available since v1.12.0-xxx-1.1. By default, these images use `json` parser for `/var/log/containers/` files because docker generates json formatted logs. On the other hand, containerd/cri-o use different log format. To parse such logs, you need to use [`cri` parser](https://github.com/fluent/fluent-plugin-parser-cri) instead. You can use `cri` parser by overwriting `tail_container_parse.conf` via ConfigMap. ``` # configuration example <parse> @type cri </parse> ``` See also [CRI parser README](https://github.com/fluent/fluent-plugin-parser-cri#log-and-configuration-example) ### Use FLUENT_CONTAINER_TAIL_PATH to change container logs folder You can update the default path for the container logs i.e /var/log/container/*.log and also one can add multiple path as defined in this fluentd document https://docs.fluentd.org/input/tail#path ### Use FLUENT_CONTAINER_TAIL_EXCLUDE_PATH to exclude specific container logs Since v1.9.3 or later images. You can exclude container logs from `/var/log/containers/` with `FLUENT_CONTAINER_TAIL_EXCLUDE_PATH`. If you have a trouble with specific log, use this envvar, e.g. `["/var/log/containers/logname-*"]`. - `exclude_path` parameter document: https://docs.fluentd.org/input/tail#exclude_path - Fluentd log issue with backslash: https://github.com/fluent/fluentd/issues/2545 ### Use LD_PRELOAD to enable jemalloc memory allocator Since v1.17.0-1.3/v1.16.5-1.3, jemalloc memory allocator is disabled by default. This is because that combination of systemd plugin and jemalloc memory allocator causes [a crash bug](https://github.com/fluent/fluentd-docker-image/issues/378). (`free(): invalid pointer` in typical) If you don't use systemd plugin at all, you can enable jemalloc memory allocator explicitly via env: parameter. ``` env: ... LD_PRELOAD="/usr/lib/libjemalloc.so.2" ``` ### Disable systemd input If you don't setup systemd in the container, fluentd shows following messages by default configuration. ``` [warn]: #0 [in_systemd_bootkube] Systemd::JournalError: No such file or directory retrying in 1s [warn]: #0 [in_systemd_kubelet] Systemd::JournalError: No such file or directory retrying in 1s [warn]: #0 [in_systemd_docker] Systemd::JournalError: No such file or directory retrying in 1s ``` You can suppress these messages by setting `disable` to `FLUENTD_SYSTEMD_CONF` environment variable in your kubernetes configuration. ### Disable prometheus input plugins By default, latest images launch `prometheus` plugins to monitor fluentd. You can disable prometheus input plugin by setting `disable` to `FLUENTD_PROMETHEUS_CONF` environment variable in your kubernetes configuration. ### Disable sed execution on elasticsearch image This is for older images. Latest elasticsearch images don't use sed. By historical reason, elasaticsearch image executes `sed` command during startup phase when `FLUENT_ELASTICSEARCH_USER` or `FLUENT_ELASTICSEARCH_PASSWORD` is specified. This sometimes causes a problem with read only mount. To avoid this problem, set "true" to `FLUENT_ELASTICSEARCH_SED_DISABLE` environment variable in your kubernetes configuration. ### Running on OpenShift This daemonset setting mounts `/var/log` as service account `fluentd` so you need to run containers as privileged container. Here is command example: ``` oc project kube-system oc create -f https://raw.githubusercontent.com/fluent/fluentd-kubernetes-daemonset/master/fluentd-daemonset-elasticsearch-rbac.yaml oc adm policy add-scc-to-user privileged -z fluentd oc patch ds fluentd -p "spec: template: spec: containers: - name: fluentd securityContext: privileged: true" oc delete pod -l k8s-app=fluentd-logging ``` This is from [nekop's japanese article](https://nekop.hatenablog.com/entry/2018/04/20/170257). ### Multiple fluentd When you want to have multiple fluentd. For example push to multiple destination like: elsticsearch + S3. You need to use `FLUENT_POS_EXTRA_DIR` add additional directory for pos file. Otherwise they share same pos file. You may found some log only on one destination. ## Note ### kafka image doesn't support zookeeper parameters zookeeper gem doesn't work on Debian 10, so kafka image doesn't include zookeeper gem. ### Windows k8s daemonset not supported in this repository Maintainers don't have k8s experience on Windows. Some users create k8s daemonset on Windows: - https://github.com/bgsilvait/k8s-fluentd-windows - https://github.com/k1nger/fluentd-windows-daemon Please check them out. ### kafka image suggestion Using debian-kafka2/debian-kafka2-arm64 images are better than using debian-kafka/debian-kafka-arm64 images. Because debian-kafka2/debian-kafka2-arm64 images use `out_kafka2` plugin but debian-kafka/debian-kafka-arm64 images use deprecated `out_kafka_buffered` plugin. ## Maintainers Some images are contributed by users. If you have a problem/question for following images, ask it to contributors. - azureblob : @elsesiy - papertrail : @alexouzounis - kafka : @erhudy - graylog : @rtnpro - gcs : @andor-pierdelacabeza - Amazon Kinesis : @shiftky - logz.io : @SaMnCo / @jamielennox - splunkhec: @FutureSharks Currently, we don't accept new destination request without contribution. See https://github.com/fluent/fluentd-kubernetes-daemonset/issues/293 ### References [Kubernetes Logging with Fluentd][fluentd-article] ## Issues We can't notice comments in the DockerHub so don't use them for reporting issues or asking question. If you have any problems with or questions about this image, please contact us through a [GitHub issue](https://github.com/fluent/fluentd-kubernetes-daemonset/issues). ## Pull Request Update `templates` files instead of `docker-image` files. `docker-image` files are automatically generated from `templates`. _Note: This file is generated from [templates/README.md.erb](templates/README.md.erb)_ [alpine-home]: http://alpinelinux.org [alpine-dockerhub]: https://hub.docker.com/_/alpine [debian-dockerhub]: https://hub.docker.com/_/debian [fluentd-article]: https://docs.fluentd.org/container-deployment/kubernetes ", Assign "at most 3 tags" to the expected json: {"id":"6370","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"