Tempo Coordinator K8s
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 2/stable | 134 | 13 Nov 2025 | |
| 2/candidate | 134 | 13 Nov 2025 | |
| 2/edge | 135 | 13 Nov 2025 | |
| dev/edge | 136 | 08 Dec 2025 | |
| 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/stable
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
-
always_enable_jaeger_grpc | boolean
Enable routing to the receiver for the 'jaeger_grpc' protocol in Tempo, even if there is no integration currently requesting it. The receiver is always enabled but will not accessible otherwise.
-
always_enable_jaeger_thrift_http | boolean
Enable routing to the receiver for the 'jaeger_thrift_http' protocol in Tempo, even if there is no integration currently requesting it. The receiver is always enabled but will not accessible otherwise.
-
always_enable_otlp_grpc | boolean
Enable routing to the receiver for the 'otlp_grpc' protocol in Tempo, even if there is no integration currently requesting it. The receiver is always enabled but will not accessible otherwise.
-
always_enable_otlp_http | boolean
Enable routing to the receiver for the 'otlp_http' protocol in Tempo, even if there is no integration currently requesting it. The receiver is always enabled but will not accessible otherwise.
-
always_enable_zipkin | boolean
Enable routing to the receiver for the 'zipkin' protocol in Tempo, even if there is no integration currently requesting it. The receiver is always enabled but will not accessible otherwise.
-
cpu_limit | string
K8s cpu resource limit for the nginx container deployed by the coordinator, e.g. "1" or "500m". Default is unset (no limit). This is DEPRECATED and will be removed in track 3. The right way to do this now is to set constraints using the juju API.
-
memory_limit | string
K8s memory resource limit for the nginx container deployed by the coordinator, e.g. "1Gi". Default is unset (no limit). This is DEPRECATED and will be removed in track 3. The right way to do this now is to set constraints using the juju API.
-
retention-period | int
Default: 720
Maximum trace retention period, in hours. This will be used to configure the compactor to clean up trace data after this time. Defaults to 720 hours, which is equivalent to 30 days. Per-stream retention limits are currently not supported.