kube-proxy ipvs failed complete: unrecognized feature gate: SupportIPVSProxyMode

[root@hadoop03 module]# cat k8s/kubeadm-config.yaml
apiVersion: kubeadm.k8s.io/v1beta2
kind: ClusterConfiguration
kubernetesVersion: v1.22.3
apiServer:
  certSANs:    #填写所有kube-apiserver节点的hostname、IP、VIP(好像也可以不用写，只写vip就行)
  - 192.168.153.100
  - 192.168.153.103
  - 192.168.153.104
controlPlaneEndpoint: "192.168.153.100:6443" #vip
imageRepository: hadoop03:5000

networking:
  podSubnet: "10.244.0.0/16"
  serviceSubnet: 10.1.0.0/16

---
apiVersion: kubeproxy.config.k8s.io/v1alpha1
kind: KubeProxyConfiguration
featureGates:
  SupportIPVSProxyMode: true
### ipvs模式 ###
mode: ipvs


##################

[root@hadoop03 module]# kubeadm init --config kubeadm-config.yaml

[root@hadoop03 module]# kubectl  get pod -A
NAMESPACE     NAME                               READY   STATUS             RESTARTS         AGE
kube-system   coredns-7675b787fd-7qlhz           1/1     Running            0                18m
kube-system   coredns-7675b787fd-vpkzc           1/1     Running            0                18m
kube-system   etcd-hadoop03                      1/1     Running            24               18m
kube-system   etcd-hadoop04                      1/1     Running            0                7m22s
kube-system   kube-apiserver-hadoop03            1/1     Running            5                18m
kube-system   kube-apiserver-hadoop04            1/1     Running            0                7m25s
kube-system   kube-controller-manager-hadoop03   1/1     Running            6 (7m12s ago)    18m
kube-system   kube-controller-manager-hadoop04   1/1     Running            0                7m25s
kube-system   kube-proxy-fx76x                   0/1     CrashLoopBackOff   8 (2m40s ago)    18m
kube-system   kube-proxy-qq2cl                   0/1     CrashLoopBackOff   6 (87s ago)      7m27s
kube-system   kube-scheduler-hadoop03            1/1     Running            40 (7m12s ago)   18m
kube-system   kube-scheduler-hadoop04            1/1     Running            3                7m26s

[root@hadoop03 module]# kubectl get cm -n kube-system
NAME                                 DATA   AGE
coredns                              1      17m
extension-apiserver-authentication   6      17m
kube-proxy                           2      17m
kube-root-ca.crt                     1      17m
kubeadm-config                       1      17m
kubelet-config-1.22                  1      17m
[root@hadoop03 module]#
[root@hadoop03 module]# kubectl edit cm kube-proxy -n kube-system

保存退出
删除kube-proxy-xxx
待自动 pod 重启

衍生问题: coredns HTT[ probe failed with statuscode: 503

kube-proxy 以上处理了，coredns 也一道处理了

衍生问题 Failed to create SubnetManager: error retrieving pod spec for 也一并处理了…

-bash-4.2# kubectl  logs kube-flannel-ds-hv5kl -n kube-system
I0915 12:08:18.765904       1 main.go:217] CLI flags config: {etcdEndpoints:http://127.0.0.1:4001,http://127.0.0.1:2379 etcdPrefix:/coreos.com/network etcdKeyfile: etcdCertfile: etcdCAFile: etcdUsername: etcdPassword: help:false version:false autoDetectIPv4:false autoDetectIPv6:false kubeSubnetMgr:true kubeApiUrl: kubeAnnotationPrefix:flannel.alpha.coreos.com kubeConfigFile: iface:[enp0s3] ifaceRegex:[] ipMasq:true subnetFile:/run/flannel/subnet.env subnetDir: publicIP: publicIPv6: subnetLeaseRenewMargin:60 healthzIP:0.0.0.0 healthzPort:0 charonExecutablePath: charonViciUri: iptablesResyncSeconds:5 iptablesForwardRules:true netConfPath:/etc/kube-flannel/net-conf.json setNodeNetworkUnavailable:true}
W0915 12:08:18.766084       1 client_config.go:608] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
E0915 12:08:18.861561       1 main.go:234] Failed to create SubnetManager: error retrieving pod spec for 'kube-system/kube-flannel-ds-hv5kl': Get "https://10.1.0.1:443/api/v1/namespaces/kube-system/pods/kube-flannel-ds-hv5kl": dial tcp 10.1.0.1:443: connect: network is unreachable

参考：https://www.cnblogs.com/zhangsi-lzq/p/14279997.html