-
Epic
-
Resolution: Done
-
Critical
-
None
-
None
-
Evaluate feature parity of Gateway API
-
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.
Epic Goal
This is a R&D-style Epic that is intended to support NE-993 (Dev Preview) and beyond with using feature parity with Route API as a basis. Implementation for Dev Preview should be captured in NE-993 and beyond dev-preview tasking should captured in an appropriate epic.
- Istio's implementation of Gateway API is the focus
- Determine Gateway API feature parity with OpenShift Route API
- Determine Istio Gateway API feature parity with OpenShift Route API
- Initial performance metrics for Istio Gateway
- Enumerate minimum viable features required for Dev Preview, Tech Preview, GA, etc
Why is this important?
- We need to understand features of Gateway API and Istio Gateway to help us understand what we are delivering in Dev Preview
Scenarios
- ...
Acceptance Criteria
- Istio Gateway API can run without a service mesh and in tandem with the Route API on OpenShift
- Rubric comparing valid Openshift Route API features with Gateway API and Istio Gateway
- Note: Not all features need to be compared, specifically, we can avoid haproxy-implementation specific features for after Dev Preview
- Documented and prioritized selection of OpenShift Route API features to align with
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- N/A
