Please select the area the issue is related to
Area/Gateway (Routing, API deployment in gateway etc.)
Please select the aspect the issue is related to
Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)
Suggested Feature
The gateway-operator need to reconcile standard Kubernetes Gateway API resources (gateway.networking.k8s.io Gateway and HTTPRoute) alongside the existing APIGateway and RestApi CRDs.
Gateway: Same infrastructure role as APIGateway — deploy the platform gateway via Helm, discover the gateway-controller Service, register it in the in-memory GatewayRegistry (no dependency on an APIGateway CR for this path).
HTTPRoute: Same API role as RestApi — build an api.yaml-compatible payload (APIConfigData) and call gateway-controller REST (POST/PUT /rest-apis, DELETE /rest-apis/{handle}).
Service: Not reconciled as its own API object; HTTPRoute resolution and a watch on Service enqueue routes when backends change.
Related Issues
#1665
Please select the area the issue is related to
Area/Gateway (Routing, API deployment in gateway etc.)
Please select the aspect the issue is related to
Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)
Suggested Feature
The gateway-operator need to reconcile standard Kubernetes Gateway API resources (gateway.networking.k8s.io Gateway and HTTPRoute) alongside the existing APIGateway and RestApi CRDs.
Gateway: Same infrastructure role as APIGateway — deploy the platform gateway via Helm, discover the gateway-controller Service, register it in the in-memory GatewayRegistry (no dependency on an APIGateway CR for this path).
HTTPRoute: Same API role as RestApi — build an api.yaml-compatible payload (APIConfigData) and call gateway-controller REST (POST/PUT /rest-apis, DELETE /rest-apis/{handle}).
Service: Not reconciled as its own API object; HTTPRoute resolution and a watch on Service enqueue routes when backends change.
Related Issues
#1665