Jaeger Operator

Jaeger Operator is a deprecated, archived Kubernetes operator for deploying the retired Jaeger v1 distributed tracing and monitoring system; new setups should…

  • Infrastructure
  • Monitoring & Logging
  • Tools & Utilities
Jaeger Operator is a deprecated, archived Kubernetes operator for deploying the retired Jaeger v1 distributed tracing and monitoring system; new setups should use the OpenTelemetry Collector Operator for Jaeger v2.

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.

23/100 Low

Maintained
0GitHub repository is archived
Popular
611,120 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
201 serious finding, 7 minor, CI, tests, OpenSSF Scorecard 4.6/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
1,120
Open issues
136
Last commit
2026-07-20
Latest release
v1.65.0
License
Apache-2.0
Activity
stale

Checked 14 days ago - source: GitHub (jaegertracing/jaeger-operator)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Check the ingress-nginx address If you are using the Kubernetes/OCI example, run kubectl get svc -n ingress-nginx and look for the LoadBalancer external IP, the outside-facing address the cluster assigns. That service exposes port 80 for web traffic and port 443 for HTTPS, so allow those if you need to reach Jaeger from outside. source
  • Start the reverse-proxy demo In the examples/reverse-proxy folder, run JAEGER_IMAGE=cr.jaegertracing.io/jaegertracing/jaeger:latest docker compose up to start all three example use cases together. Docker Compose is the tool that starts the whole stack from a file, and this command tells it to use the latest Jaeger image. source
  • Use the Badger config file Run ./jaeger-remote-storage --config-file config-badger.yaml to start the remote-storage example with Badger, a simple file-based trace store. If config-badger.yaml is missing or the path is wrong, Jaeger will not have the storage settings it needs and the example will not start. source
  • Deprecated Only supports retired Jaeger v1; use the OpenTelemetry Collector Operator for Jaeger v2. source
  • Ingress Deploy an ingress controller before using the operator's UI examples. source
  • Prerequisites Deploy an ingress-controller (e.g., ingress-nginx) before installing the operator; on minikube enable the ingress add-on first. source

Fetched 2 days ago - each note links to its source

Alternatives (4)

  • AppDynamics - The AppDynamics platform gives today’s software-defined businesses the ability to analyze and optimize digital business performance in real…
  • Netdata - Netdata is a real-time performance and health monitoring solution that collects per-second metrics from your servers, containers, networks,…
  • New Relic - Pinpoint and solve performance issues in your Ruby, Java, .NET, PHP and Python apps with real user, application and server monitoring.
  • jaeger - Jaeger v2 is an open-source, end-to-end distributed tracing platform based on the OpenTelemetry Collector.

Checked 40 days ago - source: AlternativeTo

Common questions

How do I run an all-in-one Jaeger in a test cluster with the operator?

Create a namespace, launch the Jaeger Operator, and deploy an all-in-one Jaeger instance.

Can one Jaeger Operator manage multiple namespaces?

Yes, it can watch for new Jaeger custom resources in specific namespaces or across the entire cluster. There is typically only one Jaeger Operator per cluster.

Which Jaeger version does a Jaeger Operator release track?

The operator follows the same versioning as the operand up to the minor part. For example, Jaeger Operator v1.22.2 tracks Jaeger 1.22.0.

How can clients outside the cluster send spans to Jaeger?

Expose the Jaeger Collector with your own Ingress, since the Jaeger Operator enhancement suggests creating an Ingress for this purpose.

What should I check if the Jaeger Operator installation fails on EKS?

Check the operator pod logs, CRD configuration, cluster resources, and Helm chart settings.

Answers sourced from github.com, stackoverflow.com, stackoverflow.com, stackoverflow.com, www.jaegertracing.io

Community

Collected 48 days ago - public community threads