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.

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

Docs/ce 470 locality aware #19071

Merged
merged 20 commits into from
Oct 6, 2023
Merged
Changes from 1 commit
Commits
Show all changes
20 commits
Select commit Hold shift + click to select a range
79f2105
updated nav; renamed L7 traffic folder
trujillo-adam Oct 5, 2023
e209e82
Added locality-aware routing to traffic mgmt overview
trujillo-adam Oct 5, 2023
e860219
Added route to local upstreams topic
trujillo-adam Oct 5, 2023
8ad81f9
Updated agent configuration reference
trujillo-adam Oct 5, 2023
6a98edc
Added locality param to services conf ref
trujillo-adam Oct 5, 2023
13e12ce
Added locality param to conf entries
trujillo-adam Oct 5, 2023
56f60ae
mentioned traffic management in proxies overview
trujillo-adam Oct 5, 2023
db46295
added locality-aware to failover overview
trujillo-adam Oct 5, 2023
58c8cc3
Merge branch 'main' into docs/CE-470-locality-aware
trujillo-adam Oct 5, 2023
60c99f3
Merge branch 'main' into docs/CE-470-locality-aware
trujillo-adam Oct 5, 2023
c2aedfa
added docs for service rate limiting
trujillo-adam Oct 5, 2023
295da17
Merge branch 'docs/CE-470-locality-aware' of github.com:hashicorp/con…
trujillo-adam Oct 5, 2023
b2b858a
updated service defaults conf entry
trujillo-adam Oct 5, 2023
3fac825
Merge branch 'main' into docs/CE-470-locality-aware
trujillo-adam Oct 5, 2023
da2e373
Apply suggestions from code review
trujillo-adam Oct 6, 2023
bb10b19
Merge branch 'main' into docs/CE-470-locality-aware
trujillo-adam Oct 6, 2023
db89103
Merge branch 'main' into docs/CE-470-locality-aware
trujillo-adam Oct 6, 2023
3db1687
Apply suggestions from code review
trujillo-adam Oct 6, 2023
3ce76eb
updated links and added redirects
trujillo-adam Oct 6, 2023
97c1619
Merge branch 'main' into docs/CE-470-locality-aware
trujillo-adam Oct 6, 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
Prev Previous commit
Next Next commit
Updated agent configuration reference
  • Loading branch information
trujillo-adam committed Oct 5, 2023
commit 8ad81f9940605a0a0f6f961c2e7ab6a4a937ddd2
4 changes: 4 additions & 0 deletions website/content/docs/agent/config/config-files.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -1280,6 +1280,10 @@ subsystem that provides Consul's service mesh capabilities.
corresponding to the NIST P-\* curves of the same name.
- `private_key_type = rsa`: `2048, 4096`

- `locality` <EnterpriseAlert inline/>: Specifies a map of configurations that set the region and zone of the Consul agent. When specified on server agents, `locality` applies to all partitions on the server. When specified on clients, `locality` applies to all services registered to the client. Configure this field to enable Consul to route traffic to the nearest physical service instance. Refer to [Route traffic to local upstreams](/consul/docs/connect/manage-traffic/route-to-local-upstreams) for additional information.
- `region`: String value that specifies the region where the Consul agent is running. Consul matches this value to regions defined for services in the network. When service agent regions match, Consul is able to prioritize routes between the agent and the service in the same region over healthy service instances in other regions. When multiple healthy service instances are available in the local region, Consul prioritizes services that match the agent's `zone`. You must specify values that are consistent with how regions are defined in your network, for example `us-west-1` for networks in AWS.
- `zone`: String value that specifies the zone where the Consul agent is running. Consul matches this value to zones defined for services in the region. When service agent zones match, Consul is able to prioritize routes between the agent and the service in the same zone over healthy service instances in other zones. When multiple healthy service instances are available in the local zone, Consul distributes traffic equally the services. You must specify values that are consistent with how zones are defined in your network, for example `us-west-1a` for networks in AWS.
trujillo-adam marked this conversation as resolved.
Show resolved Hide resolved

## DNS and Domain Parameters

- `dns_config` This object allows a number of sub-keys
Expand Down