OpenTelemetry-kube-stack

OpenTelemetry Quickstart chart for Kubernetes.

  • Infrastructure
  • Monitoring & Logging
  • Tools & Utilities
OpenTelemetry Quickstart chart for Kubernetes. Installs an operator and collector for an easy way to get started with Kubernetes observability.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

69/100 Good

Maintained
100last commit 16 days ago
Popular
55581 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
581
Open issues
82
Last commit
2026-11-04
Latest release
opentelemetry-operator-0.129.0
License
Apache-2.0
Activity
rising

Checked 14 days ago - source: GitHub (open-telemetry/opentelemetry-helm-charts)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install the Collector with kubectl Run the provided kubectl apply command; kubectl is the command-line tool used to manage a Kubernetes cluster. This creates the collector helper containers and a single gateway that gather and forward telemetry; without them, your apps have nowhere to send traces, metrics, or logs. source
  • Check auto-instrumentation events After install, run kubectl get events and look for lines saying the opentelemetry-auto-instrumentation container was Created and Started. If you don't see those, the automatic instrumentation isn't working, so your app's signals won't be collected. source

Fetched 40 days ago - each note links to its source

Alternatives (1)

  • dash0 - Full-Stack Infrastructure Monitoring without Limits.

Checked 40 days ago - source: AlternativeTo

Common questions

Which components are included in the opentelemetry-kube-stack Helm chart?

The chart installs an OpenTelemetry Operator and a suite of collectors for metrics, traces, and logs.

What resource issue can occur on larger Kubernetes clusters?

The default Kubernetes resource limits may be insufficient.

Has livenessProbe configuration for collector pods been reported as missing?

Yes, an issue reports that livenessProbe did not show up in collector pods even when set in CRconfig with the healthcheckv2 extension.

Can OpenTelemetry data be sent to multiple destinations?

OpenTelemetry can ship data to a dedicated backend or collector and distribute it to multiple open-source destinations such as Jaeger.

Answers sourced from github.com, github.com, www.elastic.co, www.reddit.com

Community

Collected 48 days ago - public community threads