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>
This commit is contained in:
parent
4c10c7ef58
commit
6ccc8319c4
|
@ -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.
|
||||
|
|
Loading…
Reference in New Issue