--- title: Charmhub | Deploy Tempo Worker K8s using Charmhub - The Open Operator Collection description: Deploy the latest version of Tempo Worker K8s as a Kubernetes Operator on any cloud. url: https://charmhub.io/tempo-worker-k8s/configurations --- # Tempo Worker K8s [Canonical Observability](https://charmhub.io/publisher/observability "View all packages from Canonical Observability") * [Canonical Observability](https://charmhub.io/publisher/observability "View all packages from Canonical Observability") Platform: 2.10/stable 117 ``` juju deploy tempo-worker-k8s --channel 2.10/stable ``` [Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications) * [cpu\_limit](https://charmhub.io/tempo-worker-k8s/configurations#cpu_limit) * [memory\_limit](https://charmhub.io/tempo-worker-k8s/configurations#memory_limit) * [role-all](https://charmhub.io/tempo-worker-k8s/configurations#role-all) * [role-compactor](https://charmhub.io/tempo-worker-k8s/configurations#role-compactor) * [role-distributor](https://charmhub.io/tempo-worker-k8s/configurations#role-distributor) * [role-ingester](https://charmhub.io/tempo-worker-k8s/configurations#role-ingester) * [role-metrics-generator](https://charmhub.io/tempo-worker-k8s/configurations#role-metrics-generator) * [role-querier](https://charmhub.io/tempo-worker-k8s/configurations#role-querier) * [role-query-frontend](https://charmhub.io/tempo-worker-k8s/configurations#role-query-frontend) [Learn about configurations >](https://juju.is/docs/juju/configuration#heading--application-configuration) * cpu\_limit | string K8s cpu resource limit, e.g. "1" or "500m". Default is unset (no limit). This value is used for the "limits" portion of the resource requirements. See https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ * memory\_limit | string K8s memory resource limit, e.g. "1Gi". Default is unset (no limit). This value is used for the "limits" portion of the resource requirements. See https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ * role-all | boolean Default: True Configure the application to run with all roles enabled. This is the default configuration. This is a meta-role that configures the application to enable all other roles. Under the hood, the `all` role is mapped to Tempo's `scalable-single-binary`. Each Tempo application can only have exactly one `role-X` config set to `true` at any given time. So if you want to configure this app to run with a role other than `all`, remember to set `all` to `false`. Invalid configurations will result in the component to stop working and the app to set blocked status. Note that for a tempo deployment as a whole to be consistent, each role (except the optional 'metrics-generator') needs to be assigned to at least one worker node. If this condition is not met, the coordinator charm will set blocked status and the deployment will shut down. * role-compactor | boolean Configure the application to run as this Tempo role. Each Tempo application can only have exactly one `role-X` config set to `true`. So if you want to enable a role, remember to set all other roles to `false`. Invalid configurations will result in the component to stop working and the app to set blocked status. Note that for a tempo deployment as a whole to be consistent, each role (except the optional 'metrics-generator') needs to be assigned to at least one worker node. If this condition is not met, the coordinator charm will set blocked status and the deployment will shut down. * role-distributor | boolean Configure the application to run as this Tempo role. Each Tempo application can only have exactly one `role-X` config set to `true`. So if you want to enable a role, remember to set all other roles to `false`. Invalid configurations will result in the component to stop working and the app to set blocked status. Note that for a tempo deployment as a whole to be consistent, each role (except the optional 'metrics-generator') needs to be assigned to at least one worker node. If this condition is not met, the coordinator charm will set blocked status and the deployment will shut down. * role-ingester | boolean Configure the application to run as this Tempo role. Each Tempo application can only have exactly one `role-X` config set to `true`. So if you want to enable a role, remember to set all other roles to `false`. Invalid configurations will result in the component to stop working and the app to set blocked status. Note that for a tempo deployment as a whole to be consistent, each role (except the optional 'metrics-generator') needs to be assigned to at least one worker node. If this condition is not met, the coordinator charm will set blocked status and the deployment will shut down. * role-metrics-generator | boolean Configure the application to run as this Tempo role. Each Tempo application can only have exactly one `role-X` config set to `true`. So if you want to enable a role, remember to set all other roles to `false`. Invalid configurations will result in the component to stop working and the app to set blocked status. Note that for a tempo deployment as a whole to be consistent, each role (except the optional 'metrics-generator') needs to be assigned to at least one worker node. If this condition is not met, the coordinator charm will set blocked status and the deployment will shut down. * role-querier | boolean Configure the application to run as this Tempo role. Each Tempo application can only have exactly one `role-X` config set to `true`. So if you want to enable a role, remember to set all other roles to `false`. Invalid configurations will result in the component to stop working and the app to set blocked status. Note that for a tempo deployment as a whole to be consistent, each role (except the optional 'metrics-generator') needs to be assigned to at least one worker node. If this condition is not met, the coordinator charm will set blocked status and the deployment will shut down. * role-query-frontend | boolean Configure the application to run as this Tempo role. Each Tempo application can only have exactly one `role-X` config set to `true`. So if you want to enable a role, remember to set all other roles to `false`. Invalid configurations will result in the component to stop working and the app to set blocked status. Note that for a tempo deployment as a whole to be consistent, each role (except the optional 'metrics-generator') needs to be assigned to at least one worker node. If this condition is not met, the coordinator charm will set blocked status and the deployment will shut down.