fluent/fluent-operator

Operate Fluent Bit and Fluentd in the Kubernetes way - Previously known as FluentBit Operator

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

fluent/fluent-operator has 650+ stars and 300+ forks on GitHub, is written in Go, and was last pushed on Oct 15, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 31 seconds ago
Added to GitGenius on October 15th, 2026
Created on February 14th, 2019
Open Issues & Pull Requests: 78 (+0)
GitHub issues: Enabled
Number of forks: 329
Total Stargazers: 686 (+0)
Total Subscribers: 16 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 27.7 hours
Mean response time: 96.8 days
90th percentile: 307.7 days
Tracked items: 246

Maintainer activity

3 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 16% of issues opened in the past year have never received a reply. 85% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "helm chart" is answered fastest, typically in about 15 hours, while "bug" waits about 4 weeks. 78% of issues opened in the past year have been closed, leaving a working backlog. Three people close 81% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 54
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 555 days
Stale 30+ days: 51
Stale 90+ days: 50

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • good first issue (39)
  • enhancement (35)
  • bug (16)
  • help wanted (15)
  • helm chart (11)
  • feature-request (5)
  • fluent-bit (5)
  • plugin (5)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Fluent Operator is a Kubernetes operator that facilitates the management of Fluent Bit and Fluentd in Kubernetes clusters.

The operator addresses the complexity of deploying and configuring log collection infrastructure in Kubernetes by automating the lifecycle management of both Fluent Bit DaemonSets and Fluentd StatefulSets. It allows operators to define logging pipelines declaratively using Kubernetes custom resources, selecting input, filter, and output plugins via labels. The tool supports dynamic configuration reloading, enabling updates to logging pipelines without requiring pod restarts, and provides multi-tenant log isolation capabilities through Fluentd's label-router plugin.

Teams should adopt this operator when they need flexible, Kubernetes-native log collection that can adapt to changing requirements without service disruption. It suits organizations running Kubernetes who want to leverage either Fluent Bit for lightweight edge collection or Fluentd for more complex processing, or both in a coordinated pipeline. The operator's pluggable architecture allows deploying these components separately based on specific needs, making it suitable for diverse logging architectures from simple single-destination setups to complex multi-tenant environments.

The project maintains active development with regular contributions addressing both new features and community-reported issues. The codebase demonstrates consistent quality standards and welcomes new contributors through clearly marked entry points. The project sustains an engaged community across multiple communication channels, indicating ongoing investment in supporting users and evolving the tool based on real-world logging requirements.