From 6ccc8319c418df3f119c880cf32702c02ca63056 Mon Sep 17 00:00:00 2001 From: hc-github-team-consul-core Date: Tue, 14 Nov 2023 11:28:24 -0600 Subject: [PATCH] Backport of [Docs] Update admin-partitions.mdx into release/1.16.x (#19631) * backport of commit 54ecfa6b93c4f66a05e87819cea6e6291dae1fd7 * backport of commit a5bc545f95b47c4c910e35ec21175cb443c2dd5d --------- Co-authored-by: am-ak <114914687+am-ak@users.noreply.github.com> --- website/content/docs/enterprise/admin-partitions.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/content/docs/enterprise/admin-partitions.mdx b/website/content/docs/enterprise/admin-partitions.mdx index 03a05c147..f9dc2f6b3 100644 --- a/website/content/docs/enterprise/admin-partitions.mdx +++ b/website/content/docs/enterprise/admin-partitions.mdx @@ -60,6 +60,8 @@ the lookup uses the admin partition of the Consul agent that received the query. Server agents always exist within the `default` admin partition. Client agents are configured to operate within a specific admin partition. +By default, Consul on Kubernetes uses [Consul dataplanes](/consul/docs/connect/dataplane) instead of client agents to manage communication between service instances. But to use the Consul DNS for service discovery, you must start a Consul client in client admin partitions. + ### Service Mesh Configurations The partition in which [`proxy-defaults`](/consul/docs/connect/config-entries/proxy-defaults) and [`mesh`](/consul/docs/connect/config-entries/mesh) configurations are created define the scope of the configurations. Services registered in a partition will use the `proxy-defaults` and `mesh` configurations that have been created in the partition.