Open vaalkor opened 1 year ago
The issue had no activity for 30 days, mark with Stale label.
After reading the document and code I have the same impression that namespace instead of the tenant is the admin unit for these configurations.
tenants updates
provides -
--admin-roles
Comma separated list of auth principal allowed to administrate the tenant. If empty the current set of roles won't be modified.--allowed-clusters
Comma separated allowed clusters. If omitted, the current set of clusters will be preserved.So it can be still an auth unit.
cc @nodece @michaeljmarshall do we need to update the related docs?
The issue had no activity for 30 days, mark with Stale label.
Search before asking
What issue do you find in Pulsar docs?
In the multi tenancy section of the docs it says "They [tenants] are also the administrative unit at which storage quotas, message TTL, and isolation policies can be managed.".
After I read this I expected to see commands on the admin CLI for configuring these things for a particular tenant, but I only found commands for single namespaces.
For example
set-message-ttl
,set-backlog-quota
,set-persistence
are all namespace level configuration.Is there some method of configuring tenant wide policies, or am I just interpreting the documentation wrong?
Thanks!
What is your suggestion?
I don't currently have one. I am asking a question.
Any reference?
https://pulsar.apache.org/docs/2.11.x/concepts-multi-tenancy/
Are you willing to submit a PR?