Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-93

Support Not Allocating a NodePort for LoadBalancer Service

XMLWordPrintable

    • Product / Portfolio Work
    • None
    • 0% To Do, 0% In Progress, 100% Done
    • False
    • None
    • False
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • Undefined

      Goal As an OpenShift administrator, I require support for the existing capability (as of Kubernetes 1.20, OCP 4.7) to optionally not allocate a NodePort for Services of type LoadBalancer.

      Problem:
      This is useful for VIP-based implementations of Service Type=LoadBalancer where the node port is not needed, like MetalLB, otherwise unnecessarily exposed ports can fail regulatory/compliance requirements, and the number of Services of type LoadBalancer is limited by the number of available node ports.

              ddharwar@redhat.com Deepthi Dharwar (Inactive)
              mcurry@redhat.com Marc Curry
              None
              Surya Seetharaman
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: