Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-23427

UPI LoadBalancer HAProxy config example is not correct

XMLWordPrintable

    • No
    • 3
    • OSDOCS Sprint 248
    • 1
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required

      Description of problem:

      UPI install doc: Sample API and application Ingress load balancer configuration
      Does not have health checks and should be explicit for loadbalance rules (round-robin/source)  in installation-load-balancing-user-infra.adoc

      Version-Release number of selected component (if applicable):

       

      How reproducible:

       

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

      No readyz checks, and contradicts the recommentations on the same docs page.

      Expected results:

      Has Readyz check, and round-robin, Also meets the requirments of the LB as per the Docs. in particular:
      
      > from the docs.
      The load balancer must be configured to take a maximum of 30 seconds from the
      time the API server turns off the /readyz endpoint to the removal of the API
      server instance from the pool. Within the time frame after /readyz returns an
      error or becomes healthy, the endpoint must have been removed or added. Probing
      every 5 or 10 seconds, with two successful requests to become healthy and three
      to become unhealthy, are well-tested values.
      

      Additional info:

      An example of a correctly configured loadbalancer (from IPI installer) https://github.com/openshift/installer/blob/master/upi/vsphere/lb/haproxy.tmpl
      
      Example of how it should look
      https://github.com/openshift/openshift-docs/compare/main...Timdawson264:openshift-docs:patch-1
      
      
      

            dfitzmau@redhat.com Darragh Fitzmaurice
            rhn-support-tidawson Timothy Dawson
            Gaoyun Pei Gaoyun Pei
            Pedro Jose Amoedo Martinez
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: