microk8s 的节点不想启动。Kube.system pod 处于待处理状态。kubectl describe nodes
说作为警告InvalidDiskCapacity
。我的服务器有足够多的资源。
豆荚:
NAMESPACE NAME READY STATUS RESTARTS AGE
container-registry registry-7cf58dcdcc-hf8gx 0/1 Pending 0 5d
kube-system coredns-588fd544bf-4m6mj 0/1 Pending 0 5d
kube-system dashboard-metrics-scraper-db65b9c6f-gj5x4 0/1 Pending 0 5d
kube-system heapster-v1.5.2-58fdbb6f4d-q6plc 0/4 Pending 0 5d
kube-system hostpath-provisioner-75fdc8fccd-6mdvc 0/1 Pending 0 5d
kube-system kubernetes-dashboard-67765b55f5-8xsh5 0/1 Pending 0 5d
kube-system monitoring-influxdb-grafana-v4-6dc675bf8c-82fg4 0/2 Pending 0 5d
描述节点:
Normal Starting 72s kubelet, h2860142.stratoserver.net Starting kubelet.
Warning InvalidDiskCapacity 71s kubelet, h2860142.stratoserver.net invalid capacity 0 on image filesystem
Normal NodeHasSufficientPID 70s kubelet, h2860142.stratoserver.net Node h2860142.stratoserver.net status is now: NodeHasSufficientPID
Normal NodeHasNoDiskPressure 70s kubelet, h2860142.stratoserver.net Node h2860142.stratoserver.net status is now: NodeHasNoDiskPressure
Normal NodeHasSufficientMemory 70s kubelet, h2860142.stratoserver.net Node h2860142.stratoserver.net status is now: NodeHasSufficientMemory
Warning InvalidDiskCapacity 54s kubelet, h2860142.stratoserver.net invalid capacity 0 on image filesystem
Normal NodeHasSufficientMemory 54s kubelet, h2860142.stratoserver.net Node h2860142.stratoserver.net status is now: NodeHasSufficientMemory
Normal NodeHasNoDiskPressure 54s kubelet, h2860142.stratoserver.net Node h2860142.stratoserver.net status is now: NodeHasNoDiskPressure
Normal NodeHasSufficientPID 54s kubelet, h2860142.stratoserver.net Node h2860142.stratoserver.net status is now: NodeHasSufficientPID
如何解决这个问题?
谢谢:)
我可以找到该问题的解决方案。好吧,这不是一个真正的解决方案,但答案是...我在STRATO上托管一个VPS服务器作为托管提供商。因此,在这种情况下,虚拟化是不可能的。如果我不升级到专用服务器,我将永远无法运行 Kubernetes 或 Microk8s。
问题是snap.microk8s.daemon-kubelet
的服务。 只有您应该重新启动服务
sudo systemctl restart snap.microk8s.daemon-kubelet
sudo systemctl status snap.microk8s.daemon-kubelet
从这里的文档中使用 ZFS 文件系统的步骤
停止微克8s
microk8s stop
删除容器的旧状态:
sudo rm -rf /var/snap/microk8s/common/var/lib/containerd
将容器配置为使用 ZFS:
编辑文件/var/snap/microk8s/current/args/containerd-template.toml
将snapshotter = "overlayfs"
替换为snapshotter = "zfs"
创建新的 zfs 数据集供容器使用:
zfs create -o mountpoint=/var/snap/microk8s/common/var/lib/containerd/io.containerd.snapshotter.v1.zfs $POOL/containerd
重新启动 microk8s:
microk8s start
当服务器的主机名有大写字母时,我就发生这种情况。 我们创建了一个具有小写名称的新 VM,但没有看到问题。
据我所知,这与证书访问和计算机名称不匹配有关。