Uploaded image for project: 'OpenShift SDN'
  1. OpenShift SDN
  2. SDN-2333

Support Not Allocating a NodePort for LoadBalancer Service

XMLWordPrintable

    • Support Not Allocating a NodePort for LoadBalancer Service
    • BU Product Work
    • False
    • False
    • Green
    • In Progress
    • OCPSTRAT-93 - Support Not Allocating a NodePort for LoadBalancer Service
    • Impediment
    • OCPSTRAT-93Support Not Allocating a NodePort for LoadBalancer Service
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined
    • SDN Sprint 232
    • 0
    • 0

      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.

      Dependencies (internal and external):

      Prioritized epics + deliverables (in scope / not in scope):

      Not in scope:

      Merged:

      Estimate (XS, S, M, L, XL, XXL):

      Previous Work:

      Open questions:

      Acceptance criteria:

      Epic Done Checklist:

      • CI - CI Job & Automated tests: <link to CI Job & automated tests>
      • Release Enablement: <link to Feature Enablement Presentation> 
      • DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>
      • Notes for Done Checklist
        • Adding links to the above checklist with multiple teams contributing; select a meaningful reference for this Epic.
        • Checklist added to each Epic in the description, to be filled out as phases are completed - tracking progress towards “Done” for the Epic.

          There are no Sub-Tasks for this issue.

              sseethar Surya Seetharaman
              mcurry@redhat.com Marc Curry
              Surya Seetharaman
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: