Issue
This PR adds to tempo-k8s the possibility to relate to any number of tempo-k8s-worker charms thereby taking a clustered tempo coordinator role.
It adds a config option for whether the charm should ALSO be running the worker process as a monolith even if it's clustered, or whether it should stop running tempo as soon as it starts operating in coordinator mode.
Issue This PR adds to tempo-k8s the possibility to relate to any number of tempo-k8s-worker charms thereby taking a clustered tempo coordinator role.
It adds a config option for whether the charm should ALSO be running the worker process as a monolith even if it's clustered, or whether it should stop running tempo as soon as it starts operating in coordinator mode.
Based on top of https://github.com/canonical/tempo-k8s-operator/pull/127