From dc0525919c2c0d08d0be5ed44546f679653b6737 Mon Sep 17 00:00:00 2001 From: Karl Cardenas Date: Wed, 9 Feb 2022 07:45:44 -0700 Subject: [PATCH] adding new tutorial --- website/content/docs/enterprise/admin-partitions.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/website/content/docs/enterprise/admin-partitions.mdx b/website/content/docs/enterprise/admin-partitions.mdx index 732a1ab0c8..e635ea2f85 100644 --- a/website/content/docs/enterprise/admin-partitions.mdx +++ b/website/content/docs/enterprise/admin-partitions.mdx @@ -20,9 +20,10 @@ Admin partitions exist a level above namespaces in the identity hierarchy. They -> **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. -Learn resources are available to help you get started with admin partitions. +There are Learn tutorials available to help you get started with admin partitions. - [Multi-Tenancy with Administrative Partitions](https://learn.hashicorp.com/tutorials/consul/consul-admin-partitions?in=consul/enterprise) +- [Multi Cluster Applications with Consul Enterprise Admin Partitions](https://learn.hashicorp.com/tutorials/consul/kubernetes-admin-partitions?in=consul/kubernetes) ### Default Admin Partition