1. 想不起来是什么时候的了

orphaned pod "82646587-78c6-47e4-9509-7d4ff8debbc0" found, but volume 
subpaths are still present on disk : There were a total of 2 errors 
similar to this. Turn up verbosity to see them.



https://www.ziji.work/kubernetes/kubelet-orphaned-pod-found-but-volume-paths-are-still-present-on-disk-problem.html

2. kubelet证书异常

unable to read client-cert /etc/kubernetes/ssl/client.crt for admin due to open /etc/kubernetes/ssl/client.crt: no such file or directory,
unable to read client-key /etc/kubernetes/ssl/client.key for admin due to open/etc/kubernetes/ssl/client.key for admin due to open /etc/kubernetes/ssl/client.key: no such file or directory
 
#缺少证书文件

3. kubelet异常

运行中节点突然notready

日志
Dependency failed for Kubernetes Kubelet Server
k8s kubelet依赖性失败


发现docker重启

手动start kubelet即可

4.证书未授权

Unable to authenticate the request due to an error: [invalid bearer token, square/go-jose: error in cryptographic primitive

以及生成的证书中的用户在集群中没有权限，需要根据自己的用户进行授权

5 查看node已经一直notready和ready反复切换

节点一直notreade和readey切换

日志报这个
PLEG is not healthy: pleg was last seen active 3m0.969422755s ago; threshold

#我这边是有个容器会一直处于Created状态，rm 后看起来正常了，原因未知
#这个解决方法并不稳妥，下面找到个相似的哥们发的，下次碰到做参考



https://blog.csdn.net/huiqiwei321/article/details/107692601