For endpoints that are services of ovs' pods, kube-proxy sends down redundant table entries on the node

[liujinxin]

The kuryr-controller does not completely take over kube-proxy's functions, meaning that kuryr-controller and kube-proxy coexist, but kube-proxy Can't distinguish if the endpoints is an ovs pod or not, and still configures them on the host (whether in iptables or ipvs mode).

so obviously, these rules issued by kube-proxy about endpoints being ovs' pods on the host are redundant

For example, if the endpoints of a svc are all ovs pods, the kube-proxy does not need to configure the svc configuration on the host (e.g., issue iptables rules for the svc), because these rules are not used.

[Michal Dulko (michal-dulko-f)]

Can you elaborate? Which functions of kube-proxy are not taken over by kuryr-controller? Why would you want to run kube-proxy alongside Kuryr? That's not really a supported scenario. We've tried doing that in order to drop dependency on Octavia, but had troubles to join kube-proxy networking with OpenStack's pod networking.

[liujinxin (scilla)]

Hi，Michal：
Why would you want to run kube-proxy alongside Kuryr?
If kube-proxy is not deployed on the kuryr node, does that mean that the endpoints of svc cannot be used on the kuryr node that are hostnetwork pods?

[Maysa de Macedo Souza (maysa)]

A load balancing solution would be needed in order to backup the Endpoints for a Service, regardless if the Pods of the Endpoints are running on hostNetwork. Right now, Kuryr only supports using Octavia.
As Michal mentioned we attempted running with kube-proxy on Nested environments and had problems with it. Are you still attempting to run Kuryr with Kube-proxy?

[liujinxin (scilla)]

Are you still attempting to run Kuryr with Kube-proxy?
--
Yes, on the kuryr node I deployed kube-proxy

[Maysa de Macedo Souza (maysa)]

All right, and are you still hitting the issue mentioned here?