Skip to content

docs: Document sidecarContainers for Fluent Bit #352

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
promptless-for-oss wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

docs: Document sidecarContainers for Fluent Bit #352

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions content/docs/logging-infrastructure/fluentbit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -288,6 +288,24 @@ spec:
my-annotations/enable: true
```

## Sidecar containers

To run your own helper containers next to Fluent Bit on every node, list them in the `sidecarContainers` field. For example, you might run a container that checks whether Fluent Bit is still shipping logs and restarts it when it stops. Each entry is a standard Kubernetes [Container](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#Container) definition. The Logging operator adds these containers to the Fluent Bit DaemonSet pods after its own containers: `fluent-bit`, and `config-reloader` and `buffer-metrics-sidecar` when they're enabled. Give each sidecar a name that differs from these.
Comment thread
promptless-for-oss marked this conversation as resolved.
Comment thread
promptless-for-oss marked this conversation as resolved.

```yaml
apiVersion: logging.banzaicloud.io/v1beta1
kind: FluentbitAgent
metadata:
name: default-logging-simple
spec:
sidecarContainers:
- name: fluentbitsidecar
image: alpine
command: ["sleep", "infinity"]
```

You can set the same field in the `spec.fluentbit` section of a Logging resource. For details, see the [`sidecarContainers` field reference]({{< relref "/docs/configuration/crds/v1beta1/fluentbit_types.md#fluentbitspec-sidecarcontainers" >}}).
Comment thread
promptless-for-oss marked this conversation as resolved.

## KubernetesStorage

Define Kubernetes storage.
Expand Down
4 changes: 4 additions & 0 deletions content/docs/whats-new/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,10 @@ title: What's new
weight: 50
---

## Unreleased

- You can now run your own [sidecar containers]({{< relref "/docs/logging-infrastructure/fluentbit.md#sidecar-containers" >}}) in the Fluent Bit pods. Set the `sidecarContainers` field in the FluentbitAgent resource or in the `spec.fluentbit` section of the Logging resource. For example, a sidecar can restart Fluent Bit when it stops shipping logs.
Comment thread
promptless-for-oss marked this conversation as resolved.

## Version 6.5

- The Fluentd image now includes [Typhoeus](https://github.com/typhoeus/typhoeus) as an alternative HTTP backend. Typhoeus supports connection keepalive, which can improve throughput when sending logs to HTTP-based outputs like [Elasticsearch]({{< relref "/docs/configuration/plugins/outputs/elasticsearch.md#elasticsearch-http_backend" >}}) and [OpenSearch]({{< relref "/docs/configuration/plugins/outputs/opensearch.md#opensearch-http_backend" >}}). To use it, set `http_backend: typhoeus` in your output configuration.
Expand Down
Loading