Skip to content

TRACING-5851: Clarify tenancy model in Distributed Tracing #103733

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
andreasgerstmayr wants to merge 1 commit into
base: main
Choose a base branch
from
Open

TRACING-5851: Clarify tenancy model in Distributed Tracing #103733

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion observability/distr_tracing/distr-tracing-tempo-installing.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,10 @@ include::modules/distr-tracing-tempo-object-storage-setup-ibm-storage.adoc[level
[id="configuring-permissions-and-tenants_{context}"]
== Configuring the permissions and tenants

Before installing a `TempoStack` or `TempoMonolithic` instance, you must define one or more tenants and configure their read and write access. You can configure such an authorization setup by using a cluster role and cluster role binding for the Kubernetes Role-Based Access Control (RBAC). By default, no users are granted read or write permissions. For more information, see "Configuring the read permissions for tenants" and "Configuring the write permissions for tenants".
Before installing a `TempoStack` or `TempoMonolithic` instance, you must define one or more tenants and configure their read and write access.
Tenant access is configured globally, not individually for each instance.
Therefore, granting access to a tenant provides access to that tenant across all TempoStack and TempoMonolithic instances where the tenant is configured in the corresponding CR.
You can configure such an authorization setup by using a cluster role and cluster role binding for the Kubernetes Role-Based Access Control (RBAC). By default, no users are granted read or write permissions. For more information, see "Configuring the read permissions for tenants" and "Configuring the write permissions for tenants".

[NOTE]
====
Expand Down