Tempo Coordinator K8s
Platform:
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 2.10/stable | 162 | 06 Jul 2026 | |
| 2.10/candidate | 166 | 13 Aug 2026 | |
| 2.10/beta | 166 | 13 Aug 2026 | |
| 2.10/edge | 166 | 12 Aug 2026 | |
| dev/edge | 169 | 02 Oct 2026 | |
| 2/stable | 143 | 25 Jun 2026 | |
| 2/candidate | 143 | 31 Mar 2026 | |
| 2/beta | 143 | 31 Mar 2026 | |
| 2/edge | 143 | 19 Mar 2026 | |
| 1/stable | 79 | 16 May 2025 | |
| 1/candidate | 79 | 16 May 2025 | |
| 1/beta | 79 | 16 May 2025 | |
| 1/edge | 79 | 08 May 2025 |
juju deploy tempo-coordinator-k8s --channel 2/edgeIn order to configure CPU and memory limits for tempo-worker charm, you need to set the new limit values via juju config. By default, the configuration properties are unset which means no limits are set. Assuming your application is deployed as tempo-worker and you want to set your CPU limit to 500m and memory limit to 1Gi:
juju config tempo-worker cpu_limit=500m
juju config tempo-worker memory_limit=1Gi
Same configuration properties are available in the tempo-coordinator charm, assuming your coordinator is called tempo:
juju config tempo cpu_limit=500m
juju config tempo memory_limit=1Gi
See Tempo HA resource consumption to estimate values you might need in your setup. For an explanation of resource limits, see Resource Management for Pods and Containers.