update cni version to 0.7.5 to avoid CNI-HOSTPORT-DNAT problem #499
Labels
priority/P1
Must be staffed and worked currently or soon. Is a candidate for next release
Milestone
The problem is: when using IPVS mode in kube-proxy, with a
hostPort
(assume 80) defines in a nodes, then all traffics from this node to any service:80 will be failed, actually wrongly be DNAT to thishostPort
pod.Relate discuss:
kubernetes/kubernetes#66103
containernetworking/plugins#222
kubernetes/kubernetes#62718
The reason is because the order of two chains in iptables:
CNI-HOSTPORT-DNAT
andKUBE-SERVICES
:which is, the correct order is
KUBE-SERVICES
must be ahead ofCNI-HOSTPORT-DNAT
, we can find more details in here, and if theCNI-HOSTPORT-DNAT
is at the first line, then there will be problem.The solution: in cni-plugins-portmap, they makes some changes to make the
CNI-HOSTPORT-DNAT
always in last position, and this problem will be solved, relate commit is: Portmap: appendBut, this changes only available in version 0.7.5 (and newer), so i think maybe we can update our cni version from 0.6.0 to 0.7.5.
Thanks a lot !!!
The text was updated successfully, but these errors were encountered: