-
Epic
-
Resolution: Done
-
Critical
-
None
-
Add Dev Preview Support for Gateway API via Istio
-
BU Product Work
-
False
-
None
-
False
-
Green
-
To Do
-
OCPSTRAT-416 - Gateway API using Istio for Cluster Ingress (Dev Preview)
-
-
0% To Do, 0% In Progress, 100% Done
-
-
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
- 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
- ...
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)
- ...
Previous Work (Optional):
Open questions::
- …
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>
- is cloned by
-
-
- Closed
-
[NE-993] Add Dev Preview Support for Gateway API via Istio
Blog post done and approved by Marc Curry.
Submitted to the correct RH blog: https://app.smartsheet.com/b/form/1915f94c8ba441b493c730c025aabc48
Alex Handy will be our contact for the blog publication.
Blog post 95% done and has been submitted to RH blog process:
https://docs.google.com/document/d/1gYndGGpdB3D-eficsiITDGgxPV3OeMpaVIKMykzyyyo/edit#
No docs are needed here, as we do not provide documentation until a feature reaches Technology Preview status. Thanks!
I think it's important to understand the features we need to achieve parity with Openshift Route API, however, these features DO NOT need to be implemented for dev preview.
Edit: this was a comment for linking NE-957 as "related to" to this epic...Jira doesn't show that it was for that operation.
Official published link:
https://cloud.redhat.com/blog/introducing-gateway-api-with-openshift-networking-developer-preview