This is documentation for the next version of Grafana Tempo documentation. For the latest stable release, go to the latest version.

Documentation Grafana Tempo Set up for tracing Set up Tempo Deploy your Tempo instance Deploy Tempo on Kubernetes

Deploy Tempo on Kubernetes

Kubernetes manages distributed deployments and provides orchestration for containerized applications.

Kubernetes offers several deployment options for Tempo:

• Helm charts: Package manager approach for installation and configuration
• Tempo Operator: Kubernetes-native operator for managing Tempo deployments
• Tanka/Jsonnet: Configuration management using Jsonnet templating
• Kubernetes manifests: Direct YAML configuration files

Choose the method that best fits your Kubernetes workflow and operational requirements.

Helm

Helm charts are available in the grafana/helm-charts repository:

• monolithic mode
• microservices mode and tempo-distributed chart documentation

In addition, several Helm chart examples are available in the Tempo repository.

Kubernetes Tempo Operator

The operator is available in grafana/tempo-operator repository. The operator reconciles TempoStack resource to deploy and manage Tempo microservices installation.

Refer to the operator documentation for more details.

Tanka/Jsonnet

The Jsonnet files that you need to deploy Tempo with Tanka are available here:

• monolithic mode
• microservices mode

Here are a few examples that use official Jsonnet files. They display the full range of configurations available to Tempo.

Refer to Deploy on Kubernetes with Tanka for an example installation using Tanka.

Kubernetes manifests

You can find a collection of Kubernetes manifests to deploy Tempo in the operations/jsonnet-compiled folder. These are generated using the Tanka/Jsonnet.