github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Backport of [Docs] Update admin-partitions.mdx into release/1.17.x (#19632) 

* backport of commit 54ecfa6b93

* backport of commit a5bc545f95

---------

Co-authored-by: am-ak <114914687+am-ak@users.noreply.github.com>
pull/19637/head
hc-github-team-consul-core 2023-11-14 11:28:44 -06:00 committed by GitHub
parent a99d2f67ef
commit 7cb1a9bd9c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/docs/enterprise/admin-partitions.mdx
View File

@ -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.