From 8ea3764cb61aefcc7d8e91bfb7e33cbaef92ea55 Mon Sep 17 00:00:00 2001 From: trujillo-adam Date: Tue, 14 Dec 2021 17:36:25 -0800 Subject: [PATCH] applying final feedback --- website/content/docs/enterprise/admin-partitions.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/enterprise/admin-partitions.mdx b/website/content/docs/enterprise/admin-partitions.mdx index 8683f2d059..f2c4deedce 100644 --- a/website/content/docs/enterprise/admin-partitions.mdx +++ b/website/content/docs/enterprise/admin-partitions.mdx @@ -22,9 +22,9 @@ Admin partitions exist a level above namespaces in the identity hierarchy. They ### Default Admin Partition -Each Consul cluster will have a default admin partition named `default`. The `default` admin partition is special because it can contain namespaces and other resources that are replicated between datacenters. The `default` partition must also contain the Consul servers. +Each Consul cluster will have a default admin partition named `default`. The `default` partition must contain the Consul servers. The `default` admin partition is different from other partitions that may be created because the namespaces and resources in this partition are replicated between datacenters when they are federated. -Any resource created without specifying an admin partition will inherit the partition of the ACL token. +Any resource created without specifying an admin partition will inherit the partition of the ACL token used to create the resource. -> **Preexisting resources and the `default` partition**: Admin partitions were introduced in Consul 1.11. After upgrading to Consul 1.11 or later, the `default` partition will contain all resources created in previous versions.