HA guide erroneously refers to AWS Global Accelerator. Fixes #28174
Signed-off-by: Ryan Emerson <remerson@redhat.com>
This commit is contained in:
parent
30cd40e097
commit
9bf131b5fb
1 changed files with 1 additions and 1 deletions
|
@ -20,7 +20,7 @@ If the primary site fails, the DNS changes will need to propagate to the clients
|
||||||
Depending on the client's settings, the propagation may take some minutes based on the client's configuration.
|
Depending on the client's settings, the propagation may take some minutes based on the client's configuration.
|
||||||
When using mobile connections, some internet providers might not respect the TTL of the DNS entries, which can lead to an extended time before the clients can connect to the new site.
|
When using mobile connections, some internet providers might not respect the TTL of the DNS entries, which can lead to an extended time before the clients can connect to the new site.
|
||||||
|
|
||||||
.AWS Global Accelerator Failover
|
.AWS Route53 Failover
|
||||||
image::high-availability/route53-multi-az-failover.svg[]
|
image::high-availability/route53-multi-az-failover.svg[]
|
||||||
|
|
||||||
Two Openshift Routes are exposed on both the Primary and Backup ROSA cluster.
|
Two Openshift Routes are exposed on both the Primary and Backup ROSA cluster.
|
||||||
|
|
Loading…
Reference in a new issue