You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gateway-API is someday going to replace ingress.
Currently we dont support it and we, quite simply, should.
Describe the solution you'd like
We should implement all gateway API objects and ensure feature parity with ingress
Describe alternatives you've considered
.
Additional context
The nice thing about it, is that its cut into multiple objects.
GatewayClass (cluster-wide gateway settings)
Gateway (the entrypoint definition)
Routes (comparable with ingress, linking entry points to svcs with domain names)
There are also some consequences of this, the most important one is that we need to "abstract" away things like hostname-fetching first.
As we cannot rely on going over all ingresses anymore to fetch hostnames, as those could also be defined on httpRoutes en tcpRoutes
Is your feature request related to a problem?
Gateway-API is someday going to replace ingress.
Currently we dont support it and we, quite simply, should.
Describe the solution you'd like
We should implement all gateway API objects and ensure feature parity with ingress
Describe alternatives you've considered
.
Additional context
The nice thing about it, is that its cut into multiple objects.
There are also some consequences of this, the most important one is that we need to "abstract" away things like hostname-fetching first.
As we cannot rely on going over all ingresses anymore to fetch hostnames, as those could also be defined on httpRoutes en tcpRoutes
Somewhat depends on: #31880
https://gateway-api.sigs.k8s.io/concepts/api-overview/
https://gateway-api.sigs.k8s.io/guides/migrating-from-ingress/
https://docs.nginx.com/nginx-gateway-fabric/overview/gateway-architecture/
I've read and agree with the following
The text was updated successfully, but these errors were encountered: