Esta página se tradujo automáticamente. Leer el original en inglés.

Recipe

fluent-bit-chart

Fluent Bit log processor and forwarder on Kubernetes via the official Fluent Helm chart, served from that project's HTTPS chart repository. The chart deploys Fluent Bit in its node-collector shape: one pod per node reading the container log files that node writes, a filter that enriches every record with the pod, namespace and label metadata it reads back from the cluster, and the ServiceAccount, ClusterRole and ClusterRoleBinding that filter needs to do so — a grant a forwarder assembled as a plain workload lacks, so it can neither read the node's log files nor enrich a record with the workload it came from. The sink wired on the `forward_target` uses-socket becomes the `forward` output, exactly as in the workload-synthesis realization. Reach for this realization where a chart repository is reachable at build time and log records are to be collected from the cluster itself; reach for `fluent-bit`, the workload-synthesis realization, where the build must complete with nothing fetched, or where a single forwarding pod with its own inputs is what is wanted rather than a per-node collector. The forwarder image tag is pinned. Default chart version in source.version; override via infra.source_version. provides.host and provides.metrics_service name the in-cluster Service, with no namespace, for a scraper to discover every node's collector behind it; metrics_endpoint stays empty, as one address reaches one node per scrape. That Service carries the monitoring port alone, which checks no caller, so it stays inside the cluster: an `infra.overrides.service_type` other than ClusterIP halts the build. The Fluent Bit server is Apache-2.0.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:9b2a018cae7914a4688a151380e923acaea0dfa309fe5d72ca0ff7ec05b3142f
Publicado
2026-11-10T10:23:44Z
Identidad de firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

  • Oficialapplication/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:17fd620b8438e55b9d5bad8ea60ee4e508b3b33f1033afc7057ab814b3ef0c60

Referencia en esta versión

oci://hub.aggrega.ai/recipe/helm/fluent-bit-chart:1.0.0
Destino
—
Implementa
core/observability/fluent-bit:1.0.0

Proporciona

Plantillas de punteros deterministas que esta receta cablea para los consumidores.

NombrePlantilla
host{{ .context.rendered_name }}
port{{ .infra.port }}
protocolhttp
metrics_endpoint
metrics_service{{ .context.rendered_name }}
metrics_service_porthttp
metrics_path/api/v2/metrics/prometheus

Workload

No se declaró ninguna plantilla de carga de trabajo.

Variables locales

NombrePlantilla
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

Mapeo de valores

No se declaró ningún mapeo de valores.

Relaciones

Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.

Usa

  • implementaimplementacontrato compatible

    core/observability/fluent-bit:1.0.0

    Todas las salidas obligatorias se satisfacen y cada salida proporcionada está nombrada en el contrato.

Usado por

Nada en el catálogo depende de esta entidad.

Referencia del concepto Recipe →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad