luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Typo fix

This commit is contained in:
boruszak 2022-09-28 16:10:36 -05:00
parent 0561241104
commit e8549ee314
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/docs/connect/cluster-peering/index.mdx
View File

@ -43,7 +43,7 @@ Regardless of whether you connect your clusters through WAN federation or cluste
The cluster peering beta release includes the following features and functionality:
- **Consul v1.14 beta only**: Dyanmic traffic control with a `ServiceResolver` config entry can target failover and redirects to service instances in a peered cluster.
- **Consul v1.14 beta only**: Dynanmic traffic control with a `ServiceResolver` config entry can target failover and redirects to service instances in a peered cluster.
- Consul datacenters that are already federated stay federated. You do not need to migrate WAN federated clusters to cluster peering.
- Mesh gateways for _service to service traffic_ between clusters are available. For more information on configuring mesh gateways across peers, refer to [Service-to-service Traffic Across Peered Clusters](/docs/connect/gateways/mesh-gateway/service-to-service-traffic-peers).
- You can generate peering tokens, establish, list, read, and delete peerings, and manage intentions for peering connections with both the API and the UI.