kubelet：
Orphaned pod "4db449f0-4eaf-11e8-94ab-90b8d042b91a" found, but volume paths are still present on disk : There were a total of 3 errors similar to this. Turn up verbosity to see them.
rm -rf /var/lib/kubelet/pods/4db449f0-4eaf-11e8-94ab-90b8d042b91a/volumes/rook.io~rook/pvc-4d3b9c2c-4eaf-11e8-b497-90b8d0abcd2b/
从etcd中删除pod
export ETCDCTL_API=3
alias etcdctl="etcdctl --endpoints=https://109.105.30.155:2379 --cacert=/etc/etcd/ssl/etcd-ca.pem --cert=/etc/etcd/ssl/etcd.pem --key=/etc/etcd/ssl/etcd-key.pem"
etcdctl del /registry/pods/default/wordpress-consul-5b88f4868-4ss8x
5月 10 08:28:17 k8s-n2 kubelet[3015]: I0510 08:28:17.624322 3015 kubelet.go:1794] skipping pod synchronization - [PLEG is not healthy: pleg was last seen active 3m3.938096515s ago; threshold is 3m0s]
5月 10 08:28:19 k8s-n2 kubelet[3015]: W0510 08:28:19.229291 3015 prober.go:103] No ref for container "docker://df22c6530224fdadeb959a0c0871c3e84010ad3eab76195522e414183fc48767" (jenkins-d4c9dd86f-6pp7m_default(4971d8fc-5426-11e8-9d8d-90b8d0abcd2b):jenkins)
5月 10 08:28:19 k8s-n2 kubelet[3015]: W0510 08:28:19.477882 3015 prober.go:103] No ref for container "docker://133698a55ef791596552b41c29b99cc51d6937272ee6ae1e2bb6f56c96932e02" (spinnaker-jenkins-8bf88cfdf-ldr44_spinnaker(5513b474-5426-11e8-9d8d-90b8d0abcd2b):spinnaker-jenkins)
5月 10 08:28:20 k8s-n2 kubelet[3015]: I0510 08:28:20.736842 3015 kubelet_node_status.go:811] Node became not ready: {Type:Ready Status:False LastHeartbeatTime:2018-05-10 08:28:20.736749717 +0000 UTC m=+181566.248206558 LastTransitionTime:2018-05-10 08:28:20.736749717 +0000 UTC m=+181566.248206558 Reason:KubeletNotReady Message:PLEG is not healthy: pleg was last seen active 3m7.050606596s ago; threshold is 3m0s}
容器太多 docker inspect 没有响应