Fluent Bit Kubernetes DaemonSet
Fluent Bit Kubernetes DaemonSet is a prebuilt Fluent Bit DaemonSet image for Kubernetes that collects container logs, enriches them with Kubernetes API…
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.
37/100 Low
- Maintained
- 0GitHub repository is archived
- Popular
- 53467 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 10050 MB minimum RAM
- Security check
- 55no serious findings, OpenSSF Scorecard 2.6/10
- GitHub stars
- 467
- Open issues
- 46
- Last commit
- 2022-09-26
- License
- Apache-2.0
- Activity
- stale
Checked 15 days ago - source: GitHub (fluent/fluent-bit-kubernetes-logging)
Resources & Compatibility
Minimum requirements: 50 MB RAM. ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Point Fluent Bit at the right destination Set the output plugin's host, port, or full URL to the place you actually want logs or metrics sent. If it is wrong, Fluent Bit can run normally but your data will go nowhere or to the wrong server. source
- Know the monitoring HTTP port When the HTTP server is enabled, Fluent Bit listens on TCP port 2020. If you want health checks or metrics, make sure that port is reachable; if not, keep it local to avoid exposing an extra network endpoint. source
- Upstream deprecation This repository is no longer maintained; deploy Fluent Bit for Kubernetes through the official Fluent Bit Helm chart instead. source
- Use the official Fluent Bit Helm chart This repository is no longer maintained; use the official Fluent Bit Helm chart from fluent/helm-charts for new Kubernetes logging deployments. source
Fetched 5 days ago - each note links to its source
Variants
Alternatives (2)
- fluent-bit - Fluent Bit is an open source and multi-platform Log Forwarder which allows you to collect data/logs from different sources, unify and send…
- telegraf - Telegraf is a standalone, statically compiled agent for collecting, processing, aggregating, and writing system metrics, logs, and arbitrar…
Checked 40 days ago - source: AlternativeTo
Common questions
How should Fluent Bit be installed in a Kubernetes cluster?
Deploy it as a DaemonSet so it runs on every node. The official manual recommends using the official Helm chart.
Why can Fluent Bit be running but logs still do not arrive?
The output plugin host, port, or full URL may point to the wrong destination. If that is incorrect, Fluent Bit can run normally while data goes nowhere or to the wrong server.
Which port should I use for Fluent Bit metrics or health checks?
When the HTTP server is enabled, Fluent Bit listens on TCP port 2020. Expose it only if you need health checks or metrics; otherwise keep it local.
What security consideration applies to running Fluent Bit as a DaemonSet?
A DaemonSet is easy to configure and has a low footprint, but it gives node-level access to logs. That node-level log access can raise security considerations.
Answers sourced from docs.fluentbit.io, github.com, github.com, www.reddit.com
Community
- fluentbit as the default Log Processor on GKE - Reddit (reddit)
- Can someone explain me about pros and cons of Sidecar vs daemonset - Reddit (reddit)
Collected 48 days ago - public community threads