hostport方式部署的ingress controller无法更新本地iptables规则 about hybridnet HOT 2 CLOSED

It must be clear that hostPort is not handled by kube-proxy but the portmap cni. So maybe all you want is to enable portmap cni in hybridnet.

To do this, first you need to check whether there is a portmap binary in your /opt/cni/bin/ path on every node. If not, you can use the --set daemon.neededCommunityCNIPlugins="loopback,bandwidth,portmap" to install it from the inside of hybridnet-daemon.

Then you should add the portmap cni configuration in hybridnet-cni-conf ConfigMap just like a cni conf file in /etc/cni/net.d/ and restart all the hybridnet-daemon pods.

from hybridnet.

It must be clear that hostPort is not handled by kube-proxy but the portmap cni. So maybe all you want is to enable portmap cni in hybridnet.
To do this, first you need to check whether there is a portmap binary in your /opt/cni/bin/ path on every node. If not, you can use the --set daemon.neededCommunityCNIPlugins="loopback,bandwidth,portmap" to install it from the inside of hybridnet-daemon.
Then you should add the portmap cni configuration in hybridnet-cni-conf ConfigMap just like a cni conf file in /etc/cni/net.d/ and restart all the hybridnet-daemon pods.

thx very much for ur help , i dont understand ur say about "you can use the --set daemon.neededCommunityCNIPlugins="loopback,bandwidth,portmap" to install it from the inside of hybridnet-daemon"

shoud i just reinstall hybridnet like "helm install hybridnet hybridnet/hybridnet -n kube-system --set daemon.neededCommunityCNIPlugins="loopback,bandwidth,portmap" ?

You are welcome :)

Maybe using the helm upgrade command is enough. With the neededCommunityCNIPlugins setting, hybridnet-daemon will copy some cni binaries to host path from the inside of container.

from hybridnet.