kube-logging/logging-operator

Health v2 · maintenance only

Adoption not part of the score

1704 stars · 368 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

A CNCF Sandbox Kubernetes operator that automates deployment and configuration of a complete logging pipeline, managing Fluent Bit log collectors and Fluentd or syslog-ng log forwarders via custom resources. It routes, filters, and transforms container and application logs to multiple destinations such as Elasticsearch, Loki, S3, and GCS over TLS-secured channels.

Use cases

• automate logging pipeline deployment on kubernetes
• collect container logs with fluent bit daemonset
• route pod logs to elasticsearch or loki
• ship kubernetes logs to s3 or gcs
• filter and transform logs with flows and outputs
• set up centralized cluster-wide log aggregation
• manage multiple fluentd deployments on one cluster

When to choose

• you run workloads on Kubernetes and want declarative, CRD-driven log collection and routing
• you need to fan out logs to multiple destinations like Elasticsearch, Loki, S3, or GCS
• you want TLS-secured log transport and namespace-isolated logging configuration
• you prefer managing logging infrastructure as part of your Helm charts and GitOps workflow

When to avoid

• you are not on Kubernetes (requires Kubernetes v1.22+)
• you need a lightweight single-agent setup without an operator or forwarder tier
• you rely on log shippers other than Fluent Bit, Fluentd, or syslog-ng

Facets

service · maturity active

logging monitoring deployment configuration-management monitoring cloud-computing self-hosted cloud self-hosted go kubernetes-operator fluent-bit fluentd syslog-ng log-routing cncf-sandbox helm-chart log-collector log-forwarder devops containers kubernetes docker

Member repositories

For agents

markdown · JSON · MCP: product_card(name="kube-logging/logging-operator")