OpenTelemetry Operator

OpenTelemetry Operator is a Kubernetes operator that manages OpenTelemetry Collector deployments and the automatic instrumentation of your workloads.

  • Cloud
  • Infrastructure
  • Monitoring & Logging
  • Tools & Utilities
OpenTelemetry Operator is a Kubernetes operator that manages OpenTelemetry Collector deployments and the automatic instrumentation of your workloads. It lets platform engineers standardise how observability agents are installed and configured across a cluster from a single declarative API.

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.

63/100 Good

Maintained
100last commit 15 days ago
Popular
651,775 GitHub stars
Easy to install
251 install platform, install notes
Light to run
1016 GB minimum RAM

Availability: platform listings confirmed today

GitHub stars
1,775
Open issues
298
Last commit
2026-11-05
Latest release
v0.162.0
License
Apache-2.0
Activity
steady

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

Resources & Compatibility

Minimum requirements: 16 GB RAM.

Checked 2 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Give your test cluster enough memory If you use Minikube (a small local Kubernetes cluster), start it with about 10 GB of RAM using the documented command. MinIO needs headroom; too little memory can make the installed MinIO parts crash or restart. source
  • Install the operator before any tenants Use the documented Helm command (Helm is Kubernetes' package installer) to place the MinIO Operator in its own namespace. The operator is the control part that watches your cluster and starts or keeps MinIO tenants running; without it, a tenant has no manager to bring it up. source
  • Create a tenant to actually run MinIO Apply the example tenant kustomization (a set of Kubernetes configuration files) with kubectl (the Kubernetes command-line tool) so Kubernetes creates the real MinIO storage instance. The operator alone is just the manager; the tenant is what stores data and exposes the S3 service. source
  • Create a collector resource After installing the operator, create an OpenTelemetryCollector custom resource to actually deploy and run an OpenTelemetry Collector in your cluster. source

Fetched 2 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How is the operator installed on OpenShift?

OperatorHub is used to discover Operators, and it works with Operator Lifecycle Manager to install and manage them. A cluster administrator can install an operator from OperatorHub using the OpenShift web console.

Answers sourced from docs.redhat.com

Community

Collected 47 days ago - public community threads