# kube-logging/logging-operator

Logging operator for Kubernetes

Repository: https://github.com/kube-logging/logging-operator
Canonical: https://ross.abutalabs.com/products/logging-operator
Homepage: https://kube-logging.dev
Language: Go
License: Apache-2.0
License Family: permissive
Topics: cloud-native, kubernetes, kubernetes-operator, logging, operator
Last push: 2026-08-26T15:07:21+00:00

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 97, longevity 100
- inputs: {"age_days": 2990, "days_push": 7, "days_rel": 22, "gap_med": 16.5, "n_releases_24m": 33}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1704, forks 368 (observed 2026-08-28T04:05:24.629706+00:00)

## What it is
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
- artifact type: service
- maturity: active
- function: logging, monitoring, deployment, configuration-management
- domain: monitoring, cloud-computing, self-hosted
- platform: cloud, self-hosted, go
- tags: kubernetes-operator, fluent-bit, fluentd, syslog-ng, log-routing, cncf-sandbox, helm-chart, log-collector, log-forwarder, devops, containers, kubernetes, docker

## Member repositories
- kube-logging/logging-operator (main) score 98

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:24.629706+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:37:35.449835+00:00, confidence not recorded.
  - readme: https://github.com/kube-logging/logging-operator (fetched 2026-08-28T04:05:24.629706+00:00, sha 96d6a4ef2404)
  - homepage: https://kube-logging.dev (fetched 2026-08-29T11:11:54.814283+00:00, sha 7aed9d38ceb6)
  - site_page: https://kube-logging.dev/docs (fetched 2026-08-29T11:11:54.816574+00:00, sha ffad29397ea8)
  - site_page: https://kube-logging.dev/docs/community (fetched 2026-08-29T11:11:54.818563+00:00, sha 42f49f983ab3)
  - site_page: https://kube-logging.dev/docs/install (fetched 2026-08-29T11:11:54.820239+00:00, sha 7e437f9d4048)
- Data as of 2026-08-30T08:39:29.467469+00:00.