The Tempo K8s charms together form a scaleable Tempo deployment. As these charms are maintained as a monorepo, I’ve opted for creating one review request for both charms. The assumption is that this will lead to a better review that is easier to overview both for the reviewer and us as the individual charms are never meant to be deployed in isolation.
Charms
tempo-worker-k8s
The worker is running the actual Tempo workload, allowing users to assign it a role and make it part of their scaled-out deployment.
tempo-coordinator-k8s
The coordinator is running an nginx reverse proxy, and is responsible for generating the configuration used by the workers based on configured roles.