Tempo Worker K8s
Platform:
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 2.10/stable | 117 | 06 Jul 2026 | |
| 2.10/candidate | 117 | 03 Jul 2026 | |
| 2.10/beta | 117 | 03 Jul 2026 | |
| 2.10/edge | 117 | 02 Jul 2026 | |
| dev/edge | 113 | 30 Jun 2026 | |
| 2/stable | 93 | 25 Jun 2026 | |
| 2/candidate | 93 | 31 Mar 2026 | |
| 2/beta | 93 | 31 Mar 2026 | |
| 2/edge | 93 | 13 Mar 2026 | |
| 1/stable | 59 | 16 May 2025 | |
| 1/candidate | 59 | 16 May 2025 | |
| 1/beta | 59 | 16 May 2025 | |
| 1/edge | 59 | 08 May 2025 |
juju deploy tempo-worker-k8s --channel 2.10/stableTempo is a distributed tracing backend by Grafana.
Tempo Worker K8s is a Juju charm that runs Grafana Tempo components on Kubernetes as part of a horizontally scalable deployment. It works together with the Tempo Coordinator charm, following the coordinated-workers pattern. It is a component of the Canonical Observability Stack (COS): https://documentation.ubuntu.com/observability
Each worker unit receives its configuration from the coordinator and executes exactly one Tempo role, enabling flexible scaling of individual components independently.
Key features:
- Configurable roles: querier, query-frontend, ingester, distributor, compactor, metrics-generator, or the all meta-role (scalable-single-binary mode).
- Horizontal scaling by adding more worker units with the desired role.
- Automatic configuration received from the Tempo Coordinator via the tempo-cluster relation.
- Persistent WAL storage for trace data durability across container restarts.
- Configurable Kubernetes resource limits for CPU and memory.