Jaeger Operator for Kubernetes

Juraci Paixão Kröhling
JaegerTracing
Published in
1 min readSep 12, 2018

The first version of the Jaeger Operator for Kubernetes is now available!

Kubernetes Operators are a set of components that can be installed in a given cluster to make it easier to manage a group of resources (deployments, services, …) as if they were native Kubernetes resources. In case of the Jaeger Operator, we can create a simple Jaeger instance by simply specifying a “custom resource” like this:

Under the covers, the above configuration will simply deploy the Jaeger ‘all-in-one’ container with in-memory storage. However it is also possible to define a ‘production’ strategy where the Jaeger collector, query and agent components will be deployed independently and make use of a persistent storage option.

For example, a Jaeger instance using an existing Elasticsearch at http://elasticsearch:9200as the backing storage can be specified as:

Check out the README from the repository for more information about it. Try it out and share your feedback, either via GitHub issues or via Gitter.

--

--

JaegerTracing
JaegerTracing

Published in JaegerTracing

Open source distributed tracing platform at Cloud Native Computing Foundation (graduated). https://jaegertracing.io

Juraci Paixão Kröhling
Juraci Paixão Kröhling

Written by Juraci Paixão Kröhling

Juraci Paixão Kröhling is a software engineer at Grafana Labs, a maintainer on the Jaeger project, and a contributor to the OpenTelemetry project.

Responses (4)