You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a workaround because CRIO's CNI driver has different
hostport behavior than Kubernetes' CNI driver. Kube leaves all
hostport handling to the CNI plugin itself, while CRIO does
hostport handling internally, leading to duplicate work if the
plugin also handles hostports.
For now, detect the runtime based on socket path and disable
openshift-sdn hostport handling if the runtime is CRIO.
The real fix for this is to add hostport handling to Kube's CNI
driver, but in the "split" mode discussed upstream where kube's
CNI driver handles the port reservations on the host, while the
plugin handles the actual iptables rules. CRIO should be converted
to this scheme as well, and plugins will indicate with capabilities
in the CNI JSON whether they support this scheme or not. At
that point we can remove this hack and just have openshift-sdn
advertise portmapping support via the CNI JSON.
0 commit comments