What it does
The OpenTelemetry Operator is a Kubernetes controller that manages OpenTelemetry Collector resources and automatic instrumentation for workloads. Teams declare collector and instrumentation configuration through Kubernetes resources; the operator reconciles that configuration in the cluster. It helps collect and export telemetry, but it is not a storage, query, dashboard, or alerting backend.
Let Kubernetes own collector configuration
The documented starting point is an existing Kubernetes cluster. The operator's guide says cert-manager is needed in most installations, after which the operator can be installed using its release manifest, Helm chart, or Operator Hub. A team can then create an OpenTelemetry Collector custom resource describing a collector deployment and its pipeline. The operator manages that collector resource; it does not replace the collector's receivers, processors, exporters, or the destination that stores and analyzes the data.
Instrument only the workloads you choose
The operator also supports injecting OpenTelemetry instrumentation libraries into .NET, Java, Node.js, Python, and Go services. Instrumentation is opt-in: teams configure an Instrumentation resource and annotate the workloads they want to instrument. The documentation notes that Go auto-instrumentation requires enabling a feature gate. Incorrect endpoints or environment variables can prevent data from reaching the intended destination, so validate the instrumentation configuration before relying on it.
This is a control-plane helper for Kubernetes observability, not a general monitoring application. It is most useful when a team wants to manage collector deployments and instrumentation through Kubernetes-native configuration. The repository is licensed under Apache 2.0. No cluster was configured and no deployment or instrumentation was tested for this record.
Strengths
- A Kubernetes Operator manages OpenTelemetry Collector resources instead of requiring each collector deployment to be configured independently.
- Automatic instrumentation is documented for .NET, Java, Node.js, Python, and Go workloads.
- The project documents installation by release manifest, Helm chart, or Operator Hub, plus opt-in workload annotations.
- The official repository is licensed under Apache 2.0.
Watch out for
- The Operator is specific to Kubernetes and does not provide telemetry storage, query, dashboards, or alerting by itself.
- Most installation paths require cert-manager; instrumentation must be enabled per workload, and Go injection requires a feature gate.
Best for
- Platform teams managing OpenTelemetry Collector deployments as Kubernetes resources.
- Kubernetes operators seeking opt-in instrumentation for supported application languages.
- Teams that already have a telemetry backend and want a Kubernetes-native collection and instrumentation control plane.
Sources
- LICENSE (Oct 26, 2026)
- OpenTelemetry Operator for Kubernetes (Oct 26, 2026)
- OpenTelemetry Operator for Kubernetes (Oct 26, 2026)
- Injecting Auto-instrumentation (Oct 26, 2026)