# 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 validated per-namespace ConfigMaps into one live configuration,. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/5601/kube-fluentd-operator

## Description

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.

## Health score

30/100 (Low), based on 5 of 5 factors.
- Maintained: 0 (GitHub repository is archived)
- Popular: 50 (321 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Light to run: 100 (50 MB minimum RAM, runs on ARM)
- Security check: 15 (2 serious findings, 6 minor, CI, tests, OpenSSF Scorecard 4.4/10)

## Security check

2 serious findings: Uses golang.org/x/crypto v0.31.0, which has a known critical vulnerability; Uses golang.org/x/crypto v0.31.0, which has a known critical vulnerability.
Automated checks on commit cf511bb, 3 Nov 2026. Not an audit.

## Links

- GitHub: https://github.com/vmware/kube-fluentd-operator
- Docker Hub: https://hub.docker.com/r/vmware/kube-fluentd-operator

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/5601/kube-fluentd-operator), the self-hosted and open-source app directory.
