环境:
$k得到所有
NAME READY STATUS
RESTARTS AGE
pod/mysql-0 1/1 Running 0 72s
pod/nginx-ingress-microk8s-controller-c2pgz 0/1 CrashLoopBackOff 129 22h
pod/web-0 1/1 Running 0 78s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.152.183.1 <none> 443/TCP 70m
service/mysql-service ClusterIP None <none> 3306/TCP 72s
service/nginx-service ClusterIP None <none> 80/TCP 78s
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/nginx-ingress-microk8s-controller 1 1 0 1 0 <none> 2d22h
NAME DESIRED CURRENT AGE
statefulset.apps/mysql 1 1 72s
statefulset.apps/web 1 1 78s/var/log/syslog:
failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory
Error syncing pod f0ab0f74-e6f2-11e8-8410-482ae31e6a94 ("nginx-ingress-microk8s-controller-c2pgz_default(f0ab0f74-e6f2-11e8-8410-482ae31e6a94)"), skipping: failed to "StartContainer" for "nginx-ingress-microk8s" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=nginx-ingress-microk8s pod=nginx-ingress-microk8s-controller-c2pgz_default(f0ab0f74-e6f2-11e8-8410-482ae31e6a94)"什么是nginx入口-microk8s控制器-c2pgz?是谁挑起的?
发布于 2020-10-29 19:40:36
您在注释中提到,原因与kubeadm init失败有关。
只在以下位置填充/var/lib/kubelet/config.yaml配置文件:
kubeadmin init)。kubeadm join)之后。因此,如果kubeadm init出了问题,您应该检查命令的输出(如果您可以将它粘贴在问题中也很好)。
确保您的不使用--ignore-preflight-errors=all标志在中运行kubeadm。
我不太熟悉您的具体错误,但是为了让答案更有帮助,我将尝试给出一些可能的解决方案:
发布于 2022-02-22 13:43:13
根据RtmY,它只起作用于kubectl初始化,在执行以下操作后才正确工作
kubeadm init --pod-network-cidr=192.168.0.0/16成功地发挥了作用。
发布于 2019-08-13 10:48:27
由于我更新了kubelet,所以找不到/var/lib/kubelet/config.yaml
对于"systemctl status kubelet连载日志-xe“
未能加载Kubelet配置文件/var/lib/kubelet/config.yaml
按照下面的链接,我从其他工作的工作节点复制了config.yaml及其工作!!
https://github.com/kubernetes/kubernetes/issues/65863#issuecomment-403003592
https://stackoverflow.com/questions/53276901
复制相似问题