| 2020-10-19 12:42:24 |
liujinxin |
description |
The kuryr-controller does not completely take over kube-proxy's functions, meaning that kuryr-controller and kube-proxy coexist, but kube-proxy does not discriminate for ovs' pods, 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 |
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. |
|
| 2020-10-20 01:38:05 |
liujinxin |
description |
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. |
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. |
|
