1.16.11 hyperkube assumes nf_tables for kube-proxy

[jackfrancis]

Our current 1.16.11 implementation uses the hyperkube image for kube-proxy. The 1.16.11 hyperkube image is based on Debian buster, and assumes nf_tables instead of legacy iptables. Because our Ubuntu images assume legacy iptables, kube-proxy breaks.

The 1.16.11 kube-proxy image (not hyperkube) includes "which iptables should I use?" wrapping, which supports either nf_tables or legacy iptables depending on which one is present on the underlying OS that it's scheduled onto. If we can convert our 1.16.11 kube-proxy implementation to use that image we should be able to deliver a working 1.16.11.

[aramase]

The change that caused the issue - kubernetes/kubernetes#91388. In this PR the hyperkube debian base was bumped up to v1.0.0 from 0.12.1.

The base image for kube-proxy component was also bumped - kubernetes/kubernetes#82966 but with an iptables-wrapper that determines which one to use nft or legacy.

[jadarsie]

oh, great, I was pulling my hair.