摘要：
1.系统镜像列表k8s.gcr.io/kube-apiserver:v1.19.1k8s.gcr.io/kube-scheduler:v1.19.1k8s.gcr.io/kube-controller-manager:v1.19.1k8s.gcr.io/kube-proxy:v1.19.1k8s.gcr.io/pause:3.2k8s.gcr.io/coredns:1.7.02.将原始景象打标签，
1.系统镜像列表
k8s.gcr.io/kube-apiserver:v1.19.1 k8s.gcr.io/kube-scheduler:v1.19.1 k8s.gcr.io/kube-controller-manager:v1.19.1 k8s.gcr.io/kube-proxy:v1.19.1 k8s.gcr.io/pause:3.2 k8s.gcr.io/coredns:1.7.0
2.将原始景象打标签，推送至某**公有**镜像库，不需要密码认证那种（没解决私有库问题，会报错pod类型不兼容imagePullSecrets）
3.分别修改master节点的image
/etc/kubernetes/manifests/kube-apiserver.yaml /etc/kubernetes/manifests/kube-controller-manager.yaml /etc/kubernetes/manifests/kube-scheduler.yaml
4.修改coredns(能有其他不动yaml的修改方法请教教小弟)
kubectl -n kube-system get deploy/coredns -o yaml kubectl -n kube-system edit deploy/coredns
5.修改proxy(同上)
kubectl -n kube-system get ds/kube-proxy -o yaml kubectl -n kube-system edit ds/kube-proxy
6.未完，最后一个镜像pause还没找到应用的路径，留待补充(未验证)
vi /usr/lib/systemd/system/kubelet.service.d/10-kubeadm.conf
Environment="KUBELET_POD_INFRA_CONTAINER=–pod-infra-container-image={k8s.gcr.io}/pause:3.2"
systemctl daemon-reload
systemctl restart kubelet