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

OVNK - allow specifying a different routing table for egress services (Tech Preview)

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Critical Critical
    • openshift-4.14
    • None
    • None
    • OVNK - mark the traffic that belong to a service
    • False
    • None
    • False
    • Hide
      Given an egress service with the new api with a specified routing table:
      - the return traffic coming from pods of that service are routed using the routing table
      - the egress traffic coming from endpoints of that service are routed using the routing table
      Show
      Given an egress service with the new api with a specified routing table: - the return traffic coming from pods of that service are routed using the routing table - the egress traffic coming from endpoints of that service are routed using the routing table
    • Green
    • To Do
    • TELCOSTRAT-76 - Kubernetes Service traffic steering between OVN-K and the host interfaces
    • 0% To Do, 0% In Progress, 100% Done
    • dev-ready, doc-ready, po-ready, px-ready, qe-ready
    • Hide

      2023-02-28: DEV - PR under review, OCP SDN communicated being short on reviewers & giving priority to other features. Agreement to merge in main branch once 4.13 branch cuts.

      Show
      2023-02-28: DEV - PR under review, OCP SDN communicated being short on reviewers & giving priority to other features. Agreement to merge in main branch once 4.13 branch cuts.
    • ---
    • 0
    • 0

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • Having a way to mark the return traffic coming from a service with a given mark
      • Having a way to mark the traffic originating from a pod belonging to a service with the "k8s.ovn.org/egress-service" annotation with a given mark

      Why is this important?

      Scenarios

      1. ...

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      1. Do we want to expose the mark to be applied to the service's traffic or an higher level construct?

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or 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>

            pdiak@redhat.com Patryk Diak
            fpaoline@redhat.com Federico Paolinelli
            Jean Chen Jean Chen
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: