Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of docs: admin partition and DNS clarification into release/1.15.x #18632

Merged
merged 2 commits into from
Aug 31, 2023
Merged

Backport of docs: admin partition and DNS clarification into release/1.15.x #18632

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7638316
backport of commit bd136d12dc5746b876b0177f336feec8b0b9c4c5
jkirschner-hashicorp Aug 29, 2023
778584c
backport of commit cb770fa67d6d0dd38641674c108d99f5914f08b4
jkirschner-hashicorp Aug 31, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion website/content/docs/enterprise/admin-partitions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,12 @@ Only resources in the `default` admin partition will be replicated to secondary

### DNS Queries

Client agents will be configured to operate within a specific admin partition. The DNS interface will only return results for the admin partition within the scope of the client.
When queried, the DNS interface returns results for a single admin partition.
The query may explicitly specify the admin partition to use in the lookup.
If you do not specify an admin partition in the query,
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.

### Service Mesh Configurations

Expand Down