This message was deleted.

That being a high restarting number or not depends on many - right now - unknown data points. E.g.: • what does the k3s logs say • what does dmesg say • what does the logs of CoreDNS and the local-path provisioner itself say? If it fixed or not in a later version. Might be. Both, of CoreDNS and the local-path provisioner as well as the version of Kubernetes. There’s a high level of complexity entropy here considering the amount of components/factors at play: • os • kubernetes • coredns • local-path and thereby local node storage setup … So from the info you’ve provided it’s not possible to give an answer. What is certainly known though is that your Kubernetes cluster is on an unsupported version of Kubernetes. Upgrade.