backport of commit a459c198af45d33b26701666693ac203b7c1b67c (#17748)
Co-authored-by: boruszak <jeffrey.boruszak@hashicorp.com>
This commit is contained in:
parent
70d7b849bf
commit
4acf8901bc
|
@ -21,7 +21,7 @@ The following table compares these strategies in deployments with multiple datac
|
|||
| Failover Strategy | Supports WAN Federation | Supports Cluster Peering | Multi-Datacenter Failover Strength | Multi-Datacenter Usage Scenario |
|
||||
| :---------------: | :---------------------: | :----------------------: | :--------------------------------- | :------------------------------ |
|
||||
| `Failover` stanza | ✅ | ✅ | Enables more granular logic for failover targeting | Configuring failover for a single service or service subset, especially for testing or debugging purposes |
|
||||
| Prepared query | ✅ | ✅ | Central policies that can automatically target the nearest datacenter | WAN-federated deployments where a primary datacenter is configured. Prepared queries are not replicated over peer connections. |
|
||||
| Prepared query | ✅ | ❌ | Central policies that can automatically target the nearest datacenter | WAN-federated deployments where a primary datacenter is configured. Prepared queries are not replicated over peer connections. |
|
||||
| Sameness groups | ❌ | ✅ | Group size changes without edits to existing member configurations | Cluster peering deployments with consistently named services and namespaces |
|
||||
|
||||
### Failover configurations for a service mesh with a single datacenter
|
||||
|
|
Loading…
Reference in New Issue