XML

Word

Printable

Epic Name:
OVNK - mark the traffic that belong to a service
Blocked:
False
Blocked Reason:
None
Ready:
False
Acceptance Criteria:

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
Color Status:
Green
Epic Status:
To Do
Feature Link:
TELCOSTRAT-76 - Kubernetes Service traffic steering between OVN-K and the host interfaces
Hierarchy Progress Bar:

0% To Do, 0% In Progress, 100% Done
Ready-Ready:

dev-ready, doc-ready, po-ready, px-ready, qe-ready
Status Summary:

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.
[QE] How to address?:
---
Target Version:

openshift-4.14

<--- 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?

This is another piece of the feature described in https://issues.redhat.com/browse/HATSTRAT-58

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

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

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>

links to