Deployed cluster via cluster-bot using openshift/sdn/pull/338, the issue is fixed. sh-4.4# iptables -t raw -S -P PREROUTING ACCEPT -P OUTPUT ACCEPT -N OPENSHIFT-NOTRACK -A PREROUTING -m comment --comment "disable conntrack for vxlan" -j OPENSHIFT-NOTRACK -A OUTPUT -m comment --comment "disable conntrack for vxlan" -j OPENSHIFT-NOTRACK -A OPENSHIFT-NOTRACK -p udp -m udp --dport 4789 -j NOTRACK sh-4.4# exit % oc version Client Version: 4.9.0-0.nightly-2021-08-18-144658 Server Version: 4.7.0-0.ci.test-2021-08-31-091530-ci-ln-s3w5yrb-latest Kubernetes Version: v1.20.0-1095+9689d22dc3121e-dirty Thanks, Ying
Checked on version 4.7.0-0.nightly-2021-09-06-042858, issue is fixed. sh-4.4# iptables -t raw -S -P PREROUTING ACCEPT -P OUTPUT ACCEPT -N OPENSHIFT-NOTRACK -A PREROUTING -m comment --comment "disable conntrack for vxlan" -j OPENSHIFT-NOTRACK -A OUTPUT -m comment --comment "disable conntrack for vxlan" -j OPENSHIFT-NOTRACK -A OPENSHIFT-NOTRACK -p udp -m udp --dport 4789 -j NOTRACK % oc version Client Version: 4.9.0-0.nightly-2021-08-18-144658 Server Version: 4.7.0-0.nightly-2021-09-06-042858 Kubernetes Version: v1.20.0+9689d22 Thanks, Ying
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.7.30 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:3422
The information you share is very good and interesting I know more useful things. Keep posting interesting things and I will keep an eye on your posts. https://gettingoverit.co
OpenShift SDN does not add a NOTRACK rule to the raw iptables table to prevent vxlan from reaching conntrack. This is considered a pretty good solution, very effective and meets the desired user criteria https://deathrun3d.io