From aaf63f63735fa64f32b4c20e073e8ff516368f31 Mon Sep 17 00:00:00 2001 From: Mike Morris Date: Wed, 26 Apr 2023 12:45:07 -0400 Subject: [PATCH] docs: fixup note about node scope for admin partitions --- website/content/docs/enterprise/admin-partitions.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/enterprise/admin-partitions.mdx b/website/content/docs/enterprise/admin-partitions.mdx index 230b3d60150b9..9be5a70d2e7e8 100644 --- a/website/content/docs/enterprise/admin-partitions.mdx +++ b/website/content/docs/enterprise/admin-partitions.mdx @@ -23,7 +23,7 @@ Admin partitions exist a level above namespaces in the identity hierarchy. They As of Consul v1.11, every _datacenter_ contains a single administrative partition named `default` when created. With Consul Enterprise, operators have the option of creating multiple partitions within a single datacenter. --> **Preexisting resource nodes and namespaces**: Admin partitions were introduced in Consul 1.11. Resource nodes were not namespaced prior to 1.11. After upgrading to Consul 1.11 or later, all resource nodes will be namespaced. +-> **Preexisting nodes**: Admin partitions were introduced in Consul 1.11. Nodes existed in global scope prior to 1.11. After upgrading to Consul 1.11 or later, all nodes will be scoped to an admin partition, which will be the `default` partition when initially upgrading an existing deployment or for OSS versions. There are tutorials available to help you get started with admin partitions.