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

Disable Client IP preservation in AWS NLB for sharded ingress service

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Network Edge
    • None
    • False
    • False
    • undefined

      1. Proposed title of this feature request

      Allow disabling client IP preservation for ingress controller LoadBalancer service

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

      As a user of an OpenShift Container Platform cluster installed in AWS, I want to be able to:

      • Annotate a LoadBalancer service that uses NLBs so that client IP preservation is disabled
      • Configure a LoadBalancer ingress controller that uses NLB so that its LoadBalancer service has client IP preservation disabled.

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

      Client IP preservation causes that, if a pod opens a connection to the load balancer service and that connection is sent to the same node where the pod resides, the connection fails. This makes mandatory dedicating nodes to ingress controllers, which is not preferred.

      4. List any affected packages or components.

      • AWS cloud provider (kube-controller-manager)
      • Ingress operator.

            mcurry@redhat.com Marc Curry
            rhn-support-jat Jobin A T (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: