Diagnostic step 1
On the affected Debian nodes, check kernel modules: lsmod | egrep 'ip_vs|nf_conntrack' and load if missing (modprobe ip_vs; modprobe ip_vs_rr; modprobe nf_conntrack_netlink).
Generated Oct 12, 2026, 10:57:58 PM
On the affected Debian nodes, check kernel modules: lsmod | egrep 'ip_vs|nf_conntrack' and load if missing (modprobe ip_vs; modprobe ip_vs_rr; modprobe nf_conntrack_netlink).
Verify kernel supports IPVS: review dmesg for ipvs errors and check uname -a; if custom kernel lacking IPVS, plan a kernel upgrade or fallback.
Ensure sysctls are set: sysctl net.bridge.bridge-nf-call-iptables=1 and net.ipv4.ip_forward=1. Apply temporarily and test.
If quick remediation is needed, roll kube-proxy back to iptables mode by editing the kube-proxy ConfigMap (mode: "iptables") and redeploying the daemonset. Test DNS resolution after the change; this is reversible.
If node kernels cannot be changed, consider re-scheduling critical services away from affected nodes until either kernel support is added or kube-proxy mode is changed; escalate to platform/kernel team for permanent kernel/module fix.