Recipe

fluent-bit

Fluent Bit log forwarder on Kubernetes via the helm provider's Workload synthesis, running the official upstream fluent/fluent-bit image directly (no external Helm chart). The sink host and port resolved from the `forward_target` uses-edge arrive on .context.inject.env and are written into a minimal fluent-bit.conf `forward` output at start-up, so the forwarder ships records to that sink; Fluent Bit is then exec'd against that config with its monitoring endpoint bound to the infra port, which also serves its metrics in the Prometheus format at /api/v2/metrics/prometheus, published as provides.metrics_endpoint. Fluent Bit holds no persistent state, so it renders as a stateless Deployment. provides.host is the bare, self-contained in-cluster service name of the synthesized ClusterIP Service — it carries no namespace, so the recipe is independent of where it is deployed; a consumer in another namespace qualifies the host with the target namespace on its own side (caller-side routing). Reach for this realization where the build must complete with nothing fetched, or where a single forwarding pod with its own declared input is what is wanted; reach for `fluent-bit-chart`, which renders the official Fluent chart, where a chart repository is reachable and records are to be collected from the cluster's own nodes — that realization carries the per-node collector shape and the cluster read grants this one does not carry. The Fluent Bit server is Apache-2.0.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:d64348bfccdc60e4a90d63620667b9b42db76e240d1827919b405822608477e8
Published
2026-11-10T10:23:45Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:45c731c24baff92503ce69f3fd81a99199eebb3a6c487360d33629f107c88e56

Reference at this version

oci://hub.aggrega.ai/recipe/helm/fluent-bit:1.0.0
Target
—
Implements
core/observability/fluent-bit:1.0.0

Provides

Deterministic pointer templates this recipe wires for consumers.

NameTemplate
host{{ .context.rendered_name }}-default
port{{ .infra.port }}
protocolhttp
metrics_endpointhttp://{{ .context.rendered_name }}-default:{{ .infra.port }}/api/v2/metrics/prometheus
metrics_service
metrics_service_port
metrics_path

Workload

Workload · replicas: 1 · containers: main

Locals

NameTemplate
check_socketforward_target
check_protocolforward
check_reasonFluent Bit ships its records through a forward output, which speaks the Fluentd forward protocol a sink publishes as the protocol forward
check_examplecore/observability/fluentd

Values mapping

No values mapping declared.

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

  • implementsimplementscontract compatible

    core/observability/fluent-bit:1.0.0

    All required outputs are satisfied and every provided output is named in the contract.

Used by

Nothing in the catalog depends on this entity.

Recipe concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy