See also #11977 (comment) . Basically if we'd enable kube-proxy-replacement as strict, then upgrade test from 1.7.4 to master breaks on 1.7.4 image. There is v4+v6+debug+strict enabled. Needs fixing on 1.7 side or further investigation whether disabling debugging in BPF datapath gets it back to working state.
See also #11977 (comment) . Basically if we'd enable kube-proxy-replacement as strict, then upgrade test from 1.7.4 to master breaks on 1.7.4 image. There is v4+v6+debug+strict enabled. Needs fixing on 1.7 side or further investigation whether disabling debugging in BPF datapath gets it back to working state.