Andrew Sy Kim

Agreed, we should have a separate issue for e2e

> So... (spitballing...) what if we added service.Spec.TopologyLabels which is an array of labels, and if set, then kube-proxy will prefer that clients get routed to an endpoint on a...

The "prefer node local" case was one of the primary drivers of this since you can do something like: ``` topologyKeys: - "kubernetes.io/hostname" - "*" ``` But we figured the...

> So I feel like we don't have enough consensus here to move forward in 1.26? (We don't even have consensus on if it should be topology or traffic policy...)...

> I don't think we need to try to force this into 1.26, as long as we keep talking about it, rather than forgetting about it again until the week...

> so it doesn't seem like something we can add to the iTP KEP as it's going to GA. I think we should reconsider GA-ing ITP in v1.26 if we...

@mihivagyok are you able to share steps you used to reproduce the memory leak and test your fix? I'd like to test/validate your patch against one of my development clusters

@mihivagyok I think I was able to reproduce this issue, will try to test your patch to see if it resolves the issue

> note: this change does not solve the issue which make the tunnel hanging Are you able to check the `konnectivity_network_proxy_server_grpc_connections` metric on the proxy server with this patch?

@mihivagyok I think I'm able to reproduce this issue now, and it was possible while just using the default proxy strategy. From the goroutine stacktrace, this was the semaphore lock...