Hi all,
first of all I wanted to say, that this is really an awesome project and I do enjoy every second of tinkering with it!
As I came across the new shiny Kube API proxy, I also realized that there's already GatewayAPI support 😍
Having had set up already everything for the Kube API proxy (including the NetworkRouter ) I was a little bit surprised that at the moment the GatewayAPI implementation seems to still rely on NBRoutingPeer, which would trigger a second deployment of peers, if I am not mistaken, that is fully redundant, if I already have a NetworkRouter.
This is particularly interesting, considering that I think Routes are to be replaced by Networks and the latter is automatically linked with the NetworkRouter resource.
Are there any plans to also support NetworkRouter for the GatewayAPI? Is there something one could help with? I'd be happy to contribute something if you are open for that, in whatever way it would help you (code, documentation, manual testing, ...)
Cheers
Hi all,
first of all I wanted to say, that this is really an awesome project and I do enjoy every second of tinkering with it!
As I came across the new shiny Kube API proxy, I also realized that there's already GatewayAPI support 😍
Having had set up already everything for the Kube API proxy (including the
NetworkRouter) I was a little bit surprised that at the moment the GatewayAPI implementation seems to still rely onNBRoutingPeer, which would trigger a second deployment of peers, if I am not mistaken, that is fully redundant, if I already have aNetworkRouter.This is particularly interesting, considering that I think
Routesare to be replaced byNetworksand the latter is automatically linked with theNetworkRouterresource.Are there any plans to also support
NetworkRouterfor the GatewayAPI? Is there something one could help with? I'd be happy to contribute something if you are open for that, in whatever way it would help you (code, documentation, manual testing, ...)Cheers