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

Feature to specify DNS name for HAProxy syslog

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%

    Description

      As per the documentation, we can specify only the IPv4 address for the syslog server to collect the HAProxy access logs currently.

      --> https://docs.openshift.com/container-platform/4.10/networking/ingress-operator.html#nw-configure-ingress-access-logging_configuring-ingress

       

       

      apiVersion: operator.openshift.io/v1
      kind: IngressController
      metadata:
        name: default
        namespace: openshift-ingress-operator
      spec:
        replicas: 2
        logging:
          access:
            destination:
              type: Syslog
              syslog:
                address: 1.2.3.4  <------
                port: 10514
      

      However, it's not feasible for customers to specify the IP address all the time. I am sharing the points raised by the customer for the same below.

       

      This then requires a change to the HA Proxy configuration with the new IP Address and as such a restart of the service potentially disrupting traffic.
      
      It would be more beneficial to configure a DNS Name such as the name of the Service rather than the IP Address.  
      
      Define the value or impact to you or the business
      We could lose the ability to forward logs to an external log store if the internal service IP Address changes and the HA Proxy is not re-configured wit the new IP Address.
      
       ingresscontrollers.operator.openshift.io "default" was not valid:
      # * <nil>: Invalid value: "": "spec.logging.access.destination.syslog" must validate one and only one schema (oneOf). Found none valid
      # * spec.logging.access.destination.syslog.address: Invalid value: "syslog-ng.test.svc.cluster.local": spec.logging.access.destination.syslog.address in body must be of type ipv4: "syslog-ng.test.svc.cluster.local"
      
        logging:
          access:
            destination:
              syslog:
                address: syslog-ng.test.svc.cluster.local
                maxLength: 1024
                port: 6514
              type: Syslog
            logEmptyRequests: Log
      
      Changing the address to be an IP works

      If we specify the hostname in address field then it gives the above error.

      Attachments

        Activity

          People

            mcurry@redhat.com Marc Curry
            rhn-support-aygarg Ayush Garg
            Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: