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

Allow Ingress to Modify the HAProxy Log Length when using a Sidecar


    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • openshift-4.10.z, openshift-4.11.z, openshift-4.12.z
    • Network Edge
    • False
    • None
    • False
    • Not Selected
    • x86_64

      1. Proposed title of this feature request

      Allow Ingress to be modified the log length when using a sidecar

      2. What is the nature and description of the request?

      In the past we had the RFE-1794 where an option was created to specify the length of the HAProxy log, however this option was only available for when redirecting the log for an external syslog. We need this option to be available for when using a sidecar to collect the logs.


      apiVersion: operator.openshift.io/v1
      kind: IngressController
        name: default
        namespace: openshift-ingress-operator
        replicas: 2
              type: Container
              container: {}

      Differently from the Syslog type, the Container type does not have any sub-parameter, which makes possible to configurate the log length.

      As we can see in the RFE-1794, the option to change the log length already exists in the haproxy configuration, but when using the sidecar, only the default value(1024) is used.

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

      The default log length of HAProxy is 1024. When the clients communicate to the application with the long uri arguments, it cannot catch the full access log and the parameter info. It is required a option to setup 8192 or higher.

      4. List any affected packages or components.

      • haproxy
      • ingress
      • ingress-operator

            ddharwar@redhat.com Deepthi Dharwar
            rhn-support-dsilvaju David Silva (Inactive)
            10 Vote for this issue
            6 Start watching this issue