The biggest question to ask about running Kubernetes at the edge is whether your IT organization’s edge resources are comparable to its cloud resources. If they are, a standard Kubernetes deployment — with set node affinities and related pod-assignment parameters to steer edge pods to edge nodes — is the more effective setup. If the edge and cloud environments are symbiotic, rather than unified, consider KubeEdge. Most edge users should consider this to be the default option.

The more dissimilar the edge and cloud environments or requirements are, the more logical it is to keep the two separated — particularly if edge resources are too limited to run standard Kubernetes. If you want common orchestration of both edge and cloud workloads so the cloud can back up the edge, for example, use MicroK8s or a similar distribution. If latency or resource specialization at the edge eliminates the need for that cohesion, K3s is a strong choice.

https://searchitoperations.techtarget.com/tip/Run-Kubernetes-at-the-edge-with-these-K8s-distributions