@MirantisIT

kubectl get nodes NAME STATUS ROLES AGE VERSION 2.novalocal Ready <none> 7m38s v1.19.3

~170mb Binary k0s is a successor to pharos project by Kortena (https://github.com/kontena/pharos-cluster)

k0s was previously called MKE(Mirantis kubernetes/Container Engine I suppose) its control plane is meant to be isolated (there is no way to schedule workloads on controller nodes ). No container engine running on the control plane multiple db support based on @Rancher_Labs Kine

Konnectivity for Node-control plane communication is similar to tunnel proxy of k3s

I like the - isolated control plane - custom worker profiles - Future native cluster backup/restore and other features Overall a good project to keep an eye on but a lot of effort is the same as of k3s

What are your thoughts/opinions?