Does OpenShift 4.x have the same stretch cluster latency requirement as OpenShift 3.11?

Solution Verified - Updated -

Issue

  • For OCP 3.11 there is a requirement that the arbiter site should within a 2ms latency window for communication between the primary and secondary sites.
  • Does the mandatory 2ms latency still apply for OCP 4.6 Stretch clusters?
  • The arbiter site will be relocated and there is a possibility that communication with primary and secondary sites may increase.

Environment

  • Red Hat OpenShift Container Platform 4.x
  • Red Hat OpenShift Container Platform 3.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content