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

[L3] [Services] Add support for Pod->Services traffic in user-defined primary networks

XMLWordPrintable

    • Strategic Portfolio Work
    • 8
    • False
    • None
    • False
    • OCPSTRAT-1248 - Native Network Isolation for Namespaces
    • ---
    • SDN Sprint 255, SDN Sprint 256, SDN Sprint 257, SDN Sprint 258, SDN Sprint 259
    • 0
    • 0.000

      This builds on top of https://issues.redhat.com/browse/SDN-4937

      Goal of this card is to implement the services workflow for user-defined networks - in-cluster traffic flows only (external->svc is tracked in another card)

      • Check Services aspect in the KEP
      • add logic to ensure services are accessible on the user-defined network
      • How will the endpointslices for user-defined networks be designed as? Will it be a new representation? new eps controller extended from core kube that will create eps-es on ovnk's behalf and do the healthchecks? runtime lookup of VIP->user-defined-network-podIP?
      • accordingly for services create LBs on switches and routers for the secondary network topology
      • extend current services controller to be multiple networks aware
      • add tests for all combos here
      • pod->services code is same for both gateway modes, so ensure it works on both

      End goal here is: Only add support for east-west pod->services logic on user-defined network for the pods. Other things will have other cards. Please work with other assignee as a "services-design-sub-group" so that you also have your potential reviewer in your group.

      TL;DR: traffic flows that should be supported here:

      1. pod->clusterip (w & w/ITP=local)
      2. pod->loadbalancerVIP (w & w/ ETP=local)
      3. pod->externalIP
      4. pod->nodePort -> sameNode/otherNode

              rravaiol@redhat.com Riccardo Ravaioli
              sseethar Surya Seetharaman
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: