部署K8s
node 節點not ready
root@n226-060-152:/opt/cni/bin# kubectl get node
NAME STATUS ROLES AGE VERSION
n224-214-218 NotReady <none> 119s v1.18.4
n226-060-152 Ready master 21h v1.18.4
n226-070-127 NotReady <none> 76m v1.18.4
n226-075-141 NotReady <none> 82m v1.18.4
node 節點檢視日志
sudo journalctl -u kubelet -n 100 --no-pager
Jul 22 15:10:30 n224-214-218 kubelet[2353397]: I0722 15:10:30.621814 2353397 docker_service.go:353] docker cri received runtime config &RuntimeConfig{NetworkConfig:&NetworkConfig{PodCidr:10.244.3.0/24,},}
Jul 22 15:10:30 n224-214-218 kubelet[2353397]: I0722 15:10:30.622415 2353397 kubelet_network.go:77] Setting Pod CIDR: -> 10.244.3.0/24
Jul 22 15:10:30 n224-214-218 kubelet[2353397]: I0722 15:10:30.667034 2353397 status_manager.go:158] Starting to sync pod status with apiserver
Jul 22 15:10:30 n224-214-218 kubelet[2353397]: I0722 15:10:30.667082 2353397 kubelet.go:1821] Starting kubelet main sync loop.
Jul 22 15:10:30 n224-214-218 kubelet[2353397]: E0722 15:10:30.667123 2353397 kubelet.go:1845] skipping pod synchronization - [container runtime status check may not have completed yet, PLEG is not healthy: pleg has yet to be successful]
Jul 22 15:10:30 n224-214-218 kubelet[2353397]: E0722 15:10:30.768762 2353397 kubelet.go:1845] skipping pod synchronization - container runtime status check may not have completed yet
Jul 22 15:10:30 n224-214-218 kubelet[2353397]: E0722 15:10:30.969358 2353397 kubelet.go:1845] skipping pod synchronization - container runtime status check may not have completed yet
Jul 22 15:10:31 n224-214-218 kubelet[2353397]: I0722 15:10:31.051390 2353397 cpu_manager.go:184] [cpumanager] starting with none policy
Jul 22 15:10:31 n224-214-218 kubelet[2353397]: I0722 15:10:31.051406 2353397 cpu_manager.go:185] [cpumanager] reconciling every 10s
Jul 22 15:10:31 n224-214-218 kubelet[2353397]: I0722 15:10:31.051429 2353397 state_mem.go:36] [cpumanager] initializing new in-memory state store
Jul 22 15:10:31 n224-214-218 kubelet[2353397]: I0722 15:10:31.058700 2353397 policy_none.go:43] [cpumanager] none policy: Start
Jul 22 15:10:31 n224-214-218 kubelet[2353397]: W0722 15:10:31.090594 2353397 manager.go:597] Failed to retrieve checkpoint for "kubelet_internal_checkpoint": checkpoint is not found
Jul 22 15:10:31 n224-214-218 kubelet[2353397]: I0722 15:10:31.091915 2353397 plugin_manager.go:114] Starting Kubelet Plugin Manager
Jul 22 15:10:31 n224-214-218 kubelet[2353397]: E0722 15:10:31.105446 2353397 kubelet.go:2187] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
Jul 22 15:10:31 n224-214-218 kubelet[2353397]: I0722 15:10:31.373531 2353397 topology_manager.go:233] [topologymanager] Topology Admit Handler
Jul 22 15:10:31 n224-214-218 kubelet[2353397]: I0722 15:10:31.381300 2353397 topology_manager.go:233] [topologymanager] Topology Admit Handler
Jul 22 15:10:31 n224-214-218 kubelet[2353397]: I0722 15:10:31.447630 2353397 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "kube-proxy" (UniqueName: "kubernetes.io/configmap/7dc21d2f-16c0-49da-b61f-8b7d3e9e385a-kube-proxy") pod "kube-proxy-dfcxb" (UID:"7dc21d2f-16c0-49da-b61f-8b7d3e9e385a")
Jul 22 15:10:31 n224-214-218 kubelet[2353397]: I0722 15:10:31.447677 2353397 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "xtables-lock" (UniqueName: "kubernetes.io/host-path/7dc21d2f-16c0-49da-b61f-8b7d3e9e385a-xtables-lock") pod "kube-proxy-dfcxb" (UID: "7dc21d2f-16c0-49da-b61f-8b7d3e9e385a")
Jul 22 15:10:31 n224-214-218 kubelet[2353397]: I0722 15:10:31.447726 2353397 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "lib-modules" (UniqueName: "kubernetes.io/host-path/7dc21d2f-16c0-49da-b61f-8b7d3e9e385a-lib-modules") pod "kube-proxy-dfcxb" (UID: "7dc21d2f-16c0-49da-b61f-8b7d3e9e385a")
似乎是鏡像拉取失敗
主節點
kubectl get pods -n kube-system
root@n226-060-152:/opt/cni/bin# kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-66bff467f8-nczr6 0/1 ImagePullBackOff 0 21h
coredns-66bff467f8-vr296 0/1 ImagePullBackOff 0 21h
etcd-n226-060-152 1/1 Running 0 21h
kube-apiserver-n226-060-152 1/1 Running 0 21h
kube-controller-manager-n226-060-152 1/1 Running 0 21h
kube-flannel-ds-2vlf9 1/1 Running 0 21h
kube-flannel-ds-5blq4 1/1 Running 0 6m53s
kube-flannel-ds-mqczm 0/1 Init:0/1 0 81m
kube-flannel-ds-mzkw4 0/1 Init:0/1 0 87m
kube-proxy-c94sn 0/1 ContainerCreating 0 81m
kube-proxy-dfcxb 1/1 Running 0 6m53s
kube-proxy-gzk8b 0/1 ContainerCreating 0 87m
kube-proxy-vz54p 1/1 Running 0 21h
kube-scheduler-n226-060-152 1/1 Running 0 21h
确認拉取鏡像失敗
檢視pod詳情
kubectl describe pod coredns-66bff467f8-nczr6 --namespace=kube-system
docker pull registry.aliyuncs.com/google_containers/coredns:1.6.7
docker tag registry.aliyuncs.com/google_containers/coredns:1.6.7 k8s.gcr.io/coredns:1.6.7
docker rmi registry.aliyuncs.com/google_containers/coredns:v1.6.7