Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-8652

Pre-flight Latency Validator HCP installer dry run

XMLWordPrintable

    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1.Proposed title of this feature request:

      Network latency check for mixed infrastructure, like a  latency validator  in the HCP installer dry run between the nodes before installation.
      2. What is the nature and description of the request?

      Documentation mandates <200ms latency. We should be able to validate it from the installer, like an "hcp create cluster --dry-run --validate-latency" flag.

      Verifying the mandated maximum latency of 200 ms between the management cluster and the nodes is critical because asynchronous components in the control plane (hosted on the management cluster) must maintain timely communication with the data plane  to avoid etcd timeouts and node instability. Could be a transient pod on the management cluster to execute an ICMP test or TCP handshake (port 6443 or 22) against the provided target CIDR or specific gateway IP of the compute node network checking RTT.

      3. Why does the customer need this? (List the business requirements here)

      Prevents failed deployments where the management cluster.
      4. List any affected packages or components.

      HCP CLI.

              racedoro@redhat.com Ramon Acedo
              rhn-support-dahernan David Hernandez Fernandez
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                None
                None