Fluent Bit Helm chart for Kubernetes

Open in ChatGPTOpen in Claude

Note

The Fluent Bit Coralogix Helm chart is no longer supported. We recommend using the official Fluent Bit Helm chart instead.

Warning

Security advisory: On October 20, 2026, the private keys for 8 intermediate certificate authorities operated by eMudhra were reported compromised. This is an industry-wide issue, not specific to Coralogix. Pull the updated coralogixrepo/coralogix-fluent-bit-multiarch:v3.2.10 image and restart. Force a re-pull if you already run this tag, since a cached image won't be replaced. Coralogix endpoints and internal services do not use eMudhra or emSign certificates, and we have not identified any impact to customer data.

See the eMudhra security advisory for full upgrade guidance and breaking-change details.

If you have any questions or need help upgrading, our Support team is here to help. Reach out through in-app chat and mention "Security advisory eMudhra" and the required component.

Use our multi-arch Helm chart to streamline your Kubernetes monitoring by creating a DaemonSet on your Kubernetes cluster using the Helm package manager.

Prerequisites

• Kubernetes 1.20+ with Beta APIs enabled

• Helm 2.9+ package manager installed

Installation

STEP 1. Create a namespace for the DaemonSet. The following example adopts the namespace coralogix-logger.

kubectl create namespace coralogix-logger

STEP 2. Create a secret key using your Coralogix Send-Your-Data API key.

kubectl create secret generic coralogix-keys \
        -n coralogix-logger \
        --from-literal=PRIVATE_KEY=<Send-Your-Data API Key>

STEP 3. Add the Helm Chart Repo and run an update to fetch it.

helm repo add coralogix-charts-virtual https://cgx.jfrog.io/artifactory/coralogix-charts-virtual &&
helm repo update

STEP 4. Create an override.yaml to override particular settings.

• endpoint: Input the OpenTelemetry endpoint associated with your Coralogix domain.

• dynamic_metadata: You may change the dynamic field from which we extract the application and subsystem name or a static value to overwrite these names.

---
# fluentbit-override.yaml:
dynamic_metadata:
  app_name: kubernetes.namespace_name
  sub_system: kubernetes.container_name
fluent-bit:
  endpoint: ingress.eu2.coralogix.com:443
  logLevel: error

---
# fluentbit-override.yaml:
static_metadata:
  app_name: MyApplication
  sub_system: MySubsystem
fluent-bit:
  endpoint: ingress.eu2.coralogix.com:443
  logLevel: error

• If a dynamic variable includes special characters, it must be declared in a different notation, such as the following. Failure to do so will result in LUA exceptions and failure to process properly.

  app_name: kubernetes.labels["k8s-app"]
  app_name: kubernetes.labels["app.kubernetes.io/name"]

STEP 5. Deploy the Helm Chart.

helm upgrade fluent-bit-http coralogix-charts-virtual/fluent-bit-http \
  --install \
  --namespace=coralogix-logger \
  -f fluentbit-override.yaml

Remove the Daemonset

STEP 6. Remove the DaemonSet.

helm uninstall fluent-bit-http \
     -n coralogix-logger

Notes:

• podsecuritypolicy has been deprecated for Kubernetes v1.25+.

• Disable this by adding the following to your override file:

podSecurityPolicy:
  create: false

Additional Resources

Review and make suggestions for improvement for our Helm chart in our Integrations Repository.