status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

[Docs] Update admin-partitions.mdx (#18430) 

* [Docs] Update admin-partitions.mdx

Adding a note on DNS queries requiring the presence of a Consul Client in the Admin partition

The consul-dns endpoints are the consul clients and servers as seen In the Helm chart consul/templates/dns-service.yaml
  selector:
    app: {{ template "consul.name" . }}
    release: "{{ .Release.Name }}"
    hasDNS: "true"

all components have the first two labels for app and release but only consul clients and servers have the last one hasDNS so it will only match clients AND servers
grep hasDNS ./* 2> /dev/null
./client-daemonset.yaml:      hasDNS: "true"
./dns-service.yaml:    hasDNS: "true"
./server-statefulset.yaml:        hasDNS: "true"

* Update website/content/docs/enterprise/admin-partitions.mdx

Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>

---------

Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
This commit is contained in:
am-ak 2023-11-14 18:11:11 +01:00 committed by GitHub
parent 2ff6ab19ce
commit c835c90c0b
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. Server agents always exist within the `default` admin partition.
Client agents are configured to operate within a specific 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 ### 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. 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.