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

• Add Gateway API via Istio Gateway implementation as Dev Preview in 4.12 

Problem: ** As an administrator, I would like to securely expose cluster resources to remote clients and services while providing a self-service experience to application developers. Currently, this goal is achieved through the Route and IngressController custom resources. Although this approach overcame the limitations of the Kubernetes-native Ingress resource, it requires additional burden on Red Hat to maintain.

Dev Preview: An optional product capability that is not officially supported by Red Hat, but is intended to provide a mechanism to explore early phase technology. Developer preview functionality is opt-in, and subject to removal at any time. Production use is not permitted.  Installation and use is not eligible for Red Hat production support.  Enabling a developer preview feature may render a cluster unsupportable dependent upon the scope of the feature. See documentation specific to that feature for specific guidance. 

Why is this important?

• Reduces the burden on Red Hat developers to maintain IngressController and Route custom resources.
• Provides advanced routing capabilities for cluster ingress traffic.
• Demonstrates Red Hat’s leadership in the Kubernetes community.

Scenarios

1. ...

Acceptance Criteria

• Standalone installation documentation in Dev Preview
• Gateway API and Istio Gateway are in an acceptable standing for Dev Preview
• Continued team operational familiarity with Istio Gateway and Envoy 

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. https://issues.redhat.com/browse/NE-435

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>