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.
Provenance
- Empreinte du contenu
- sha256:9b2a018cae7914a4688a151380e923acaea0dfa309fe5d72ca0ff7ec05b3142f
- Publié
- 2026-11-10T10:23:44Z
- Identité de signature
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Signature
- Officielapplication/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
Référence à cette version
oci://hub.aggrega.ai/recipe/helm/fluent-bit-chart:1.0.0- Cible
- —
- Implémente
- core/observability/fluent-bit:1.0.0
Fournit
Modèles de pointeurs déterministes que cette recette câble pour les consommateurs.
| Nom | Modèle |
|---|---|
| host | {{ .context.rendered_name }} |
| port | {{ .infra.port }} |
| protocol | http |
| metrics_endpoint | |
| metrics_service | {{ .context.rendered_name }} |
| metrics_service_port | http |
| metrics_path | /api/v2/metrics/prometheus |
Workload
Aucun modèle de charge de travail déclaré.
Variables locales
| Nom | Modèle |
|---|---|
| check_socket | forward_target |
| check_protocol | forward |
| check_reason | Fluent Bit ships its records through a forward output, which speaks the Fluentd forward protocol a sink publishes as the protocol forward |
| check_example | core/observability/fluentd |
Correspondance des valeurs
Aucune correspondance des valeurs déclarée.
Relations
Arêtes typées vers et depuis d’autres entités publiées. Une référence sans cible publiée s’affiche comme une arête rompue plutôt que comme un lien.
Utilise
- implémenteimplémentecontrat compatible
core/observability/fluent-bit:1.0.0
Toutes les sorties obligatoires sont satisfaites et chaque sortie fournie est nommée dans le contrat.
Utilisé par
Rien dans le catalogue ne dépend de cette entité.