I checked out #microk8s today after feeling pressure from seeing it discussed so many places about. Canonical's all in one #k8s/#kunernetes.

I am pretty amazed how much is on tap here with #microk8s.

I feel like I must switch. Sure, it brings me so many great capabilities that I'd have to recreate on #k3s (my current micro #k8s), but while this offering is amazingly compelling & diverse- #LetsEncrypt, #Prometheus, many more- mostly I find it overpoweringly compelling because if I want a good #devops base to hone my craft on, it needs to be a shareable base. One others can put into practice readily too.

I have questions about it's tech stratum. Alas #k3s & #microk8s are less forthcoming about what layers of container tech they perch upon than would be ideal.

We can look at questions like cgroups v2 support, & #outrider techs such as crun have the leg up here. The stratum are as important as the package. But these distros, targeting further ended users, rarely chase the leading edge, & alas do not do a ton of work to make clear what tech they do ride atop.
https://github.com/rancher/k3s/issues/900

Fedora 31 Support - cgroups v2 · Issue #900 · rancher/k3s

k3s-agent is failing to run on Fedora 31. I suspect this is due to cgroups v2 being the default on Fedora 31, but can't quite figure out how to see which version of runc is shipping with k3s (r...