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

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

EDIT: This EPIC is only tracking the pre-work, FUP https://issues.redhat.com/browse/CORENET-6248 for GA promotion

Epic Goal

Promote Egress-service to General Availability from Tech Preview only on local gateway mode - leadership decided its OK to have a feature GA-ed only on LGW and not on SGW (surya feels otherwise but that is not valid here)

Egress Service enhancement and TechPreview was done 2 years ago: https://github.com/openshift/enhancements/blob/master/enhancements/network/service-egress-traffic-steering.md#network in OCP Release 4.14. On OCP Side we don't have that many customers asking for this feature so we never prioritized getting it to GA. Recently however Telco has reached out saying they have "two support exceptions for this feature" and "other customers waiting for this feature" -> not sure how many. So they would like to have us GA Egress Service in OCP for Local Gateway mode.

Compared to when the feature was added, things have changed in OCP with regards to "feature gates promotion" which I will outline here as a task and also will outline other API related and feature related discussions that we would like to have cleared before we can GA this feature. - Whether all of these must be followed or not is upto the sub group implementing the feature.

Most important thing to be outlined as part of this EPIC is thorough API design review and potential spike work for this feature to work alongside other features that are GA

Why is this important?

• SUPPORTEX-21918

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):

1. SDN-2682 
2. https://github.com/openshift/enhancements/blob/master/enhancements/network/service-egress-traffic-steering.md 

Open questions::

1. ...

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>