mirror of https://github.com/status-im/consul.git
Typo fix
This commit is contained in:
parent
055bb88ee5
commit
dfd5903c8e
|
@ -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**: Dynanmic traffic control with a `ServiceResolver` config entry can target failover and redirects to service instances in a peered cluster.
|
||||
- **Consul v1.14 beta only**: Dynamic 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.
|
||||
|
|
Loading…
Reference in New Issue