On my little kubernetes cluster with microK8s
i got this problem:
kubectl get nodes
NAME STATUS ROLES AGE VERSION
zigbee NotReady <none> 59d v1.19.5-34+b1af8fc278d3ef
ubuntu Ready <none> 59d v1.19.6-34+e6d0076d2a0033
The solution was:
kubectl describe node zigbee
and in the output i found:
Hmmm - so running additional databases, processes outside of kubernetes is not such a good idea.Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Starting 18m kube-proxy Starting kube-proxy.
Normal Starting 14m kubelet Starting kubelet.
Warning SystemOOM 14m kubelet System OOM encountered, victim process: influx, pid: 3256628
Warning InvalidDiskCapacity 14m kubelet invalid capacity 0 on image filesystem
Normal NodeHasNoDiskPressure 14m (x2 over 14m) kubelet Node zigbee status is now: NodeHasNoDiskPressure
Normal NodeHasSufficientPID 14m (x2 over 14m) kubelet Node zigbee status is now: NodeHasSufficientPID
Normal NodeHasSufficientMemory 14m (x2 over 14m) kubelet Node zigbee status is now: NodeHasSufficientMemory
But as a fast solution: I ejected the SD card and did a resize + add swap on my laptop and put the SD card back to the raspberry pi...
No comments:
Post a Comment