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

Typo fix

Browse Source
pull/14794/head
boruszak 2 years ago
parent 2589f07659
commit efcb466e38
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File

2
website/content/docs/connect/cluster-peering/create-manage-peering.mdx
Unescape View File

@ -375,7 +375,7 @@ Next to the name of the peer, click **More** (three horizontal dots) and then **
</Tab> </Tab>
</Tabs> </Tabs>
## Traffic nanagement between peers ## Traffic management between peers
As of Consul v1.14, you can use [dynamic traffic management](/consul/docs/connect/l7-traffic) to configure your service mesh so that services automatically failover and redirect between peers. The following examples updates the [ServiceResolver config entry](/docs/connect/config-entries/) in `cluster-01` so that Consul redirects traffic intended for the `frontend` service to a backup instance in peer `cluster-02` when it detects multiple connection failures. As of Consul v1.14, you can use [dynamic traffic management](/consul/docs/connect/l7-traffic) to configure your service mesh so that services automatically failover and redirect between peers. The following examples updates the [ServiceResolver config entry](/docs/connect/config-entries/) in `cluster-01` so that Consul redirects traffic intended for the `frontend` service to a backup instance in peer `cluster-02` when it detects multiple connection failures.

Write Preview
Loading…
Cancel
Save