The authoritative region is used to provide a single source of truth for ACL Policies, ACL Tokens and Namespaces in multi-region, federated Nomad clusters. When used, all servers should have this configuration parameter set and non-authoritative regions will have the data replicated to them from the authoritative region.
To answer the questions you posted directly:
If used, all servers should have this configuration item set
This is not related in any way to leadership election
No, as mentioned previously, this parameter only needs to be set in multi-region federated Nomad deployments where you wish to use this functionality.
Thanks for sharing the details. But I’m unable to understand its use case.
I’m trying to relate its working if I host it in an organization. If I have 1 region then no need to add this item. On the flip side, with multi region we have to add this configuration in all the server nodes of any one region. But, in both the cases, there will be only one type of acl policies replicate to all the servers in every the region.
If I’m sitting in an organization then definitely I will setup nomad only for the user belonging to my organization which raises a question that why I’ll create this segregation. Could you please share any scenario which clarifies its use case.