Details
-
Epic
-
Resolution: Unresolved
-
Blocker
-
None
-
None
-
None
-
Provide a solution for Gateway management by an operator
-
False
-
None
-
False
-
-
Green
-
To Do
-
OCPSTRAT-416 - Gateway API using Istio for Cluster Ingress (Dev Preview)
-
87
-
87%
-
8
-
0
-
0.0
Description
User Story: As a cluster admin, I want to create a gatewayclass and a gateway, and OpenShift should configure Istio/Envoy with an LB and DNS, so that traffic can reach httproutes attached to the gateway.
The operator will be one of these (or some combination):
- cluster-ingress-operator
- OSSM operator
- a new operator
Functionality includes DNS (NE-1107), LoadBalancer (NE-1108), , and other operations formerly performed by the cluster-ingress-operator for routers.
- configures GWAPI subcomponents
- Installs GWAPI Gateway CRD
- installs Istio (if needed) when Gateway and GatewayClasses are created
Requires design document or enhancement proposal, breakdown into more specific stories.
(probably needs to be an Epic, will move things around later to accomodate that).
Out of scope for enhanced dev preview:
- Unified Control Plane operations (NE-1095)
- Installs RBAC that restricts who can configure Gateway and GatewayClasses
Attachments
Issue Links
- is related to
-
NE-1160 Add Tech Preview Support for Gateway API via Istio
-
- Planning
-
-
OCPBUGS-8526 Enhanced Dev Preview GWAPI doesn't create DNS records for Gateways that are manually linked
-
- New
-
- relates to
-
NE-1036 Add Enhanced Dev Preview Support for Gateway API via Istio
-
- In Progress
-
-
NE-1095 Provide a solution for a Unified Control Plane
-
- To Do
-
-
NE-1107 Provide a solution for DNS Management
-
- Closed
-
-
NE-1108 Provide a solution for Load Balancer Management
-
- Closed
-
-
NE-999 Understand Istio operator interactions with Istio Gateway
-
- To Do
-
- links to