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

HAProxy Dynamic Configuration Manager for OpenShift 4

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • openshift-4.12
    • None
    • Network Edge
    • None
    • False
    • False
    • Undefined

      1. Proposed title of this feature request
      HAProxy Dynamic Configuration Manager for OpenShift 4

      2. What is the nature and description of the request?
      In OpenShift 3.11 the dynamic configuration manager for HAProxy was available as a feature, configurable easily setting the following env variable:

      oc set env dc/<router_name> ROUTER_HAPROXY_CONFIG_MANAGER='true'

      More info about this feature:
      https://docs.openshift.com/container-platform/3.11/install_config/router/default_haproxy_router.html#using-the-dynamic-configuration-manager

      3. Why does the customer need this? (List the business requirements here)
      While seamless HAProxy reloads were included in OpenShift 3.9, one of our customers could have been detected SYN connections not being ACK'ed during the TCP handshake. This customer would like to avoid unnecessary HAProxy reloads.
      This feature was available in OpenShift 3 but not in OpenShift 4.

      4. List any affected packages or components.
      HAProxy

              mcurry@redhat.com Marc Curry
              rh-ee-vhernand Victor Hernando
              Votes:
              1 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: