Fail to run static pod without master running about k3s

[liyimeng]

I see we have allow this for etcdagent node, can it be extended to normal agent node?
base on resource like this I would consider this as a case that k3s break k8s conformance

[brandond]

This is a duplicate of #1686

K3s agents do not start the container runtime or kubelet until a server is reachable to provide up-to-date certificates and configuration. Because the kubelet isn't started yet, there is no issue with Kubernetes conformance - conformance places no requirements on how a distribution operates prior to startup of Kubernetes itself, or what startup dependencies a distribution enforces.

Although there have been discussions on this topic in the past, we are not planning to relax this requirement at this time.