loft-sh
Support Gateway API spec
Is your feature request related to a problem?
The Gateway API is in v1 and is supposed to be able to completely replace the usage of Ingress and give more possibilities, power, expressiveness and security to users.
Ingress is frozen. New features are being added to the Gateway API. - source
Gateway API is the successor to the Ingress API. However, it does not include the Ingress kind. As a result, a one-time conversion from your existing Ingress resources to Gateway API resources is necessary. Refer to the ingress migration guide for details on migrating Ingress resources to Gateway API resources. - source
-
HTTP flow
-
Users (Personas)
Which solution do you suggest?
Have for vcluster...
- full compliance with https://gateway-api.sigs.k8s.io/reference/spec/
- docs for how to manage and use shared (host x vcluster) Gateway API resources
- tested GatewayClass (like in e2e_generic/clusterscope/ingressclasses.go) and related
- listed caveats when using Gateway API
Which alternative solutions exist?
NA
Additional context
- Many projects have already reported conformance https://gateway-api.sigs.k8s.io/implementations/v1.1/
- https://github.com/kubernetes/ingress-nginx is going to implement it too https://youtube.com/clip/UgkxgCwz2N3y19vEyQh-vBYHR78ekQJnDtfA?si=8dSf3JK4pU6xTz8Z
GA was in 2023 and 1.2 is out now. Users are deploying it. There hasn't been any activity or response for some time.
What is the plan for native integration/sync with vCluster? What are folks doing currently?
