Kube Fluentd Operator

Kube Fluentd Operator is an archived Kubernetes operator that gives cluster operators a single Fluentd log collector for all container logs by compiling…

  • Infrastructure
  • Monitoring & Logging
  • Tools & Utilities
Kube Fluentd Operator is an archived Kubernetes operator that gives cluster operators a single Fluentd log collector for all container logs by compiling validated per-namespace ConfigMaps into one live configuration, with label-based routing and no restarts.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

30/100 Low

Maintained
0GitHub repository is archived
Popular
50321 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
10050 MB minimum RAM, runs on ARM
Security check
152 serious findings, 6 minor, CI, tests, OpenSSF Scorecard 4.4/10
GitHub stars
321
Open issues
58
Last commit
2025-03-10
Latest release
v1.18.2
Activity
stale

Checked 3 days ago - source: GitHub (vmware/kube-fluentd-operator)

Resources & Compatibility

Minimum requirements: 50 MB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start with the recommended DaemonSet Use the kubectl command (Kubernetes' command-line tool) to apply the recommended DaemonSet file (which starts one pod on each node). This is the easiest way to avoid pods that cannot reach each other. source
  • Keep the CNI network file in place Put the 10-kuberouter.conf file in /etc/cni/net.d/ and keep it there, because CNI (Kubernetes' pod-network setup file) tells the node how to give pods network addresses. If that file is missing or edited wrong, new pods may fail to start or lose network access. source
  • Choose the features you want to run Set the startup flags (the on/off switches for Kube-router's jobs), such as --run-router=true, --run-firewall=true, and --run-service-proxy=true. Leaving a needed feature off can make pods or services unreachable, while picking the right mix avoids extra overhead. source
  • Per-namespace configuration Create one Fluentd ConfigMap per namespace; the operator compiles those ConfigMaps into a single validated configuration for the shared Fluentd instance. source
  • Log routing Use Kubernetes labels on workloads to filter and route logs into the configured Fluentd outputs. source
  • Archived upstream Upstream repository is archived; use the latest available release image. source

Fetched 30 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I install kube-fluentd-operator in a cluster?

Use the Helm chart and set rbac.create=true. You must also pass image.repository and image.tag manually because official images are not published yet.

How do I point a namespace to its log destination?

Create a ConfigMap in that namespace with a fluent.conf entry. If the ConfigMap is not named fluentd-config, annotate the namespace with logging.csp.vmware.com/fluentd-configmap to point to it.

Do I need to restart Fluentd after changing a namespace ConfigMap?

No, KFO compiles the Fluentd configuration from per-namespace ConfigMaps and reconfigures Fluentd accordingly. It is built to avoid needing a restart when configuration changes.

Can I select log streams by pod labels or container names?

Yes, KFO extends the Fluentd configuration language to refer to pods by labels and container name patterns. This allows fine-grained targeting of log streams for preprocessing before shipping.

Can kube-fluentd-operator collect logs written to files in a container?

Yes, it can ingest logs from a file on the container filesystem. This is not recommended and is mainly intended for legacy or misconfigured apps that log locally.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads