Monitoring Kubernetes with Managed ClickStack

This guide walks you through collecting logs, infrastructure metrics, and Kubernetes events from a cluster into Managed ClickStack, then viewing them in the built-in Kubernetes dashboard. The pattern is the standard OpenTelemetry one: two collectors deployed via the OpenTelemetry Helm chart, each forwarding to your ClickStack gateway collector via OTLP. A DaemonSet runs on every node to collect container logs and kubelet metrics. A Deployment with a single replica collects Kubernetes events and cluster-wide metrics. For background on the gateway role, see Collector roles. This guide assumes you’ve completed Setting up your OpenTelemetry Collector and have a ClickStack gateway collector running. For a Kubernetes-resident workload, the gateway collector itself should be deployed inside the same cluster using the upstream OpenTelemetry Helm chart with the ClickStack collector image. Follow the Helm path in Deploying the collector to install it. Ensure you have recorded this OTLP endpoint.

Gather your prerequisites

You’ll need:

A Kubernetes cluster (v1.20+ recommended) with kubectl configured against it.
Helm v3+.
The OTLP endpoint of your ClickStack gateway collector, reachable from inside the cluster, for example http://clickstack-otel-collector.observability.svc.cluster.local:4318. The collector should be deployed somewhere your DaemonSets and Deployment can reach it, typically in the same cluster or via a service of type LoadBalancer.
The OTLP_AUTH_TOKEN value you set when deploying the gateway collector. If you didn’t secure the collector, you can skip the secret step below and drop the authorization header from the manifests.

Where the gateway runsFor a cluster-local deployment, run the gateway collector as a Kubernetes Deployment or StatefulSet inside the same cluster and address it through its in-cluster service DNS. For a gateway running outside the cluster, use its externally reachable URL.

Create the auth secret and ConfigMap

Pick the namespace you want the collectors to live in, then create a secret holding the OTLP_AUTH_TOKEN and a ConfigMap pointing at your gateway:

export OTLP_AUTH_TOKEN="a-strong-shared-secret"
export OTEL_COLLECTOR_ENDPOINT="http://clickstack-otel-collector.observability.svc.cluster.local:4318"
export NAMESPACE=observability

kubectl create namespace ${NAMESPACE} --dry-run=client -o yaml | kubectl apply -f -

kubectl create secret generic clickstack-otlp-secret \
  --from-literal=OTLP_AUTH_TOKEN=${OTLP_AUTH_TOKEN} \
  -n ${NAMESPACE}

kubectl create configmap otel-config-vars \
  --from-literal=YOUR_OTEL_COLLECTOR_ENDPOINT=${OTEL_COLLECTOR_ENDPOINT} \
  -n ${NAMESPACE}

Both collectors below read these values via extraEnvs, so the same secret and ConfigMap are reused across them.

Add the OpenTelemetry Helm repo

helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts
helm repo update

Deploy the cluster collector

This is a single-replica Deployment that collects Kubernetes events and cluster-wide metrics (node counts, pod phases, deployment status, and so on). Running more than one replica would produce duplicates.Save the following as k8s_deployment.yaml:

k8s_deployment.yaml

# k8s_deployment.yaml
mode: deployment

image:
  repository: otel/opentelemetry-collector-contrib
  tag: 0.123.0

# We only want one of these collectors - any more and we'd produce duplicate data
replicaCount: 1

presets:
  kubernetesAttributes:
    enabled: true
    extractAllPodLabels: true
    extractAllPodAnnotations: true
  # Collects Kubernetes events via the k8sobject receiver.
  kubernetesEvents:
    enabled: true
  # Collects cluster-level metrics via the k8s_cluster receiver.
  clusterMetrics:
    enabled: true

extraEnvs:
  - name: OTLP_AUTH_TOKEN
    valueFrom:
      secretKeyRef:
        name: clickstack-otlp-secret
        key: OTLP_AUTH_TOKEN
        optional: true
  - name: YOUR_OTEL_COLLECTOR_ENDPOINT
    valueFrom:
      configMapKeyRef:
        name: otel-config-vars
        key: YOUR_OTEL_COLLECTOR_ENDPOINT

config:
  exporters:
    otlphttp:
      endpoint: "${env:YOUR_OTEL_COLLECTOR_ENDPOINT}"
      compression: gzip
      headers:
        authorization: "${env:OTLP_AUTH_TOKEN}"
  service:
    pipelines:
      logs:
        exporters:
          - otlphttp
      metrics:
        exporters:
          - otlphttp

Install it:

helm install k8s-otel-deployment open-telemetry/opentelemetry-collector \
  -f k8s_deployment.yaml \
  -n ${NAMESPACE}

Deploy the node collector

This is a DaemonSet that runs on every node to collect container logs, host metrics, and kubelet metrics (per-pod and per-container CPU and memory utilisation against requests and limits).Save the following as k8s_daemonset.yaml:

k8s_daemonset.yaml

# k8s_daemonset.yaml
mode: daemonset

image:
  repository: otel/opentelemetry-collector-contrib
  tag: 0.123.0

# Required to use the kubeletstats cpu/memory utilization metrics
clusterRole:
  create: true
  rules:
    - apiGroups:
        - ''
      resources:
        - nodes/proxy
      verbs:
        - get

presets:
  logsCollection:
    enabled: true
  hostMetrics:
    enabled: true
  kubernetesAttributes:
    enabled: true
    extractAllPodLabels: true
    extractAllPodAnnotations: true
  kubeletMetrics:
    enabled: true

extraEnvs:
  - name: OTLP_AUTH_TOKEN
    valueFrom:
      secretKeyRef:
        name: clickstack-otlp-secret
        key: OTLP_AUTH_TOKEN
        optional: true
  - name: YOUR_OTEL_COLLECTOR_ENDPOINT
    valueFrom:
      configMapKeyRef:
        name: otel-config-vars
        key: YOUR_OTEL_COLLECTOR_ENDPOINT

config:
  receivers:
    # Additional kubelet metrics expressed as utilisation against requests and limits.
    kubeletstats:
      collection_interval: 20s
      auth_type: 'serviceAccount'
      endpoint: '${env:K8S_NODE_NAME}:10250'
      insecure_skip_verify: true
      metrics:
        k8s.pod.cpu_limit_utilization:
          enabled: true
        k8s.pod.cpu_request_utilization:
          enabled: true
        k8s.pod.memory_limit_utilization:
          enabled: true
        k8s.pod.memory_request_utilization:
          enabled: true
        k8s.pod.uptime:
          enabled: true
        k8s.node.uptime:
          enabled: true
        k8s.container.cpu_limit_utilization:
          enabled: true
        k8s.container.cpu_request_utilization:
          enabled: true
        k8s.container.memory_limit_utilization:
          enabled: true
        k8s.container.memory_request_utilization:
          enabled: true
        container.uptime:
          enabled: true

  exporters:
    otlphttp:
      endpoint: "${env:YOUR_OTEL_COLLECTOR_ENDPOINT}"
      compression: gzip
      headers:
        authorization: "${env:OTLP_AUTH_TOKEN}"

  service:
    pipelines:
      logs:
        exporters:
          - otlphttp
      metrics:
        exporters:
          - otlphttp

Install it:

helm install k8s-otel-daemonset open-telemetry/opentelemetry-collector \
  -f k8s_daemonset.yaml \
  -n ${NAMESPACE}

Confirm both releases are healthy:

kubectl get pods -n ${NAMESPACE} -l app.kubernetes.io/name=opentelemetry-collector

You should see one Deployment pod and one DaemonSet pod per node, all in Running state.

Forward Kubernetes attributes to your apps (recommended)

To correlate your application logs, metrics, and traces with Kubernetes metadata (pod name, namespace, node, deployment), forward the metadata into your application via OTEL_RESOURCE_ATTRIBUTES. The DaemonSet’s k8sattributes processor will then enrich incoming telemetry with the matching pod and node attributes.

# my_app_deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: app-deployment
spec:
  replicas: 1
  selector:
    matchLabels:
      app: app
  template:
    metadata:
      labels:
        app: app
        service.name: <MY_APP_NAME>
    spec:
      containers:
        - name: app-container
          image: my-image
          env:
            - name: POD_NAME
              valueFrom:
                fieldRef:
                  fieldPath: metadata.name
            - name: POD_UID
              valueFrom:
                fieldRef:
                  fieldPath: metadata.uid
            - name: POD_NAMESPACE
              valueFrom:
                fieldRef:
                  fieldPath: metadata.namespace
            - name: NODE_NAME
              valueFrom:
                fieldRef:
                  fieldPath: spec.nodeName
            - name: DEPLOYMENT_NAME
              valueFrom:
                fieldRef:
                  fieldPath: metadata.labels['deployment']
            - name: OTEL_RESOURCE_ATTRIBUTES
              value: k8s.pod.name=$(POD_NAME),k8s.pod.uid=$(POD_UID),k8s.namespace.name=$(POD_NAMESPACE),k8s.node.name=$(NODE_NAME),k8s.deployment.name=$(DEPLOYMENT_NAME)

Confirm in the ClickStack UI

Open your service in the ClickHouse Cloud console and select ClickStack from the left menu.In the Search view, switch the source to Logs and set the time range to Last 15 minutes. Container logs from across the cluster should appear within a few seconds, enriched with attributes like k8s.namespace.name, k8s.pod.name, and k8s.node.name.To see infrastructure metrics and events in context, open the built-in Kubernetes dashboard by navigating to Dashboards -> Kubernetes. The Pods, Nodes, and Namespaces tabs should all be populated.If nothing shows up:

Verify the DaemonSet and Deployment pods are Running and tail their logs with kubectl logs -n ${NAMESPACE} <pod>.
Confirm YOUR_OTEL_COLLECTOR_ENDPOINT is reachable from inside the cluster (kubectl exec into one of the collector pods and curl it).
Check that the OTLP_AUTH_TOKEN in the secret matches the value set on the gateway collector.

Get started

Features

Managing ClickStack

Guides

Integration partners

Monitoring Kubernetes with Managed ClickStack