Sebastian Florek

Gateway API is not the same as API Gateway. We need API Gateway to stitch together our services and expose them as a single API.

> > Gateway API is not the same as API Gateway. We need API Gateway to stitch together our services and expose them as a single API. > > And...

On our side, it's quite simple. API exposes the WebSocket endpoint and frontend connects to it. In case you are using some kind of additional proxies you need to make...

That's expected. If the connection will be dropped at any point by i.e. your proxy then it will always reconnect to the same pod that keeps the connection open internally...

You shouldn't really have to touch kong configuration if you want to enable ingress. This looks like a configuration issue.

I'd have to recheck but IIRC this was intentional. I think there was an issue accessing metrics scraper service in code when it was using a named port. https://github.com/kubernetes/dashboard/blob/9a476333d4f392a5b85d80a51c8149b4c2ec011d/modules/api/pkg/integration/metric/sidecar/restclient.go#L48-L55

Yep, we can't change that as connecting to the service via API service proxy does not work with named ports. /close

It would have to be a generic solution and the main issue is that we do not have a good way to store user configuration since Dashboard is stateless and...

Our API uses very little resources when idle. Since this is mostly a proxy to Kubernetes API server it's good to balance the load through more pods. It can also...

> resources do not "idle" per-se. they are actually committed/dedicated as defined in their resource limits settings. Of course. That's why most kubernetes clusters are heavily overprovisioned and actual resource...