Use our multi-arch Helm chart to streamline your Kubernetes monitoring by creating a DaemonSet on your Kubernetes cluster using the Helm package manager.
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: <coralogix_endpoint> logLevel: error
--- # fluentbit-override.yaml: static_metadata: app_name: MyApplication sub_system: MySubsystem fluent-bit: endpoint: <coralogix_endpoint> logLevel: error
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
STEP 6. Remove the DaemonSet.
helm uninstall fluent-bit-http \ -n coralogix-logger
Notes:
podsecuritypolicy
has been deprecated for Kubernetes v1.25+.podSecurityPolicy: create: false
Review and make suggestions for improvement for our Helm chart in our Integrations Repository.
Need help?
Our world-class customer success team is available 24/7 to walk you through your setup and answer any questions that may come up.
Feel free to reach out to us via our in-app chat or by sending us an email at [email protected].