microshift VS microk8s

Another good option is Microshift: https://github.com/openshift/microshift

RPM RHEL derivatives I recommend: https://microshift.io

If you are moving to edge you can try microshift (https://microshift.io/). There is also option to run a single node ocp (https://docs.openshift.com/container-platform/4.9/installing/installing_sno/install-sno-installing-sno.html).

There is also microshift. https://microshift.io/

I use one snap, but not on Fedora, instead with RHEL. It is the only way to use Microk8s, which is a quite full-featured distribution of Kubernetes that has a small footprint. Red Hat recently came out with an early offering called MicroShift, but it's not really ready yet. When it can satisfy my needs, you'll bet I'm switching.

This is an open source project from the start (as most things red hat creates), you can find the coffee here: https://github.com/redhat-et/microshift

GitHub - redhat-et/microshift: A small form factor OpenShift/Kubernetes optimized for edge computing

If you want hands-on practice you should have a running Kubernetes cluster (I used MicroK8s for this tutorial) and Helm (see how to install on Installing Helm tutorial). It is important that you understand the basics of these tools to fully understand.

And install microk8s:

MicroK8s is a lightweight, batteries included Kubernetes distribution by Canonical designed for running edge workloads which also happens to be developer-friendly and a great choice for building your own homelab. The following lab covers how to install and run MicroK8s on your own edge node running Ubuntu 22.04 LTS, deploy the NGINX web service and exposing your NGINX website to the Internet with SSL/TLS enabled using AWS resources included within the Free Tier.

One quick and easy win I can recommend, is microk8s.

I had the same problem (and there's a github issue about this: https://github.com/canonical/microk8s/issues/2186). I swapped to k3s and the usage was half of what microk8s used.

microk8s currently has a showstopping issue that makes it guaranteed to have an irrecoverable failure in HA mode. see https://github.com/canonical/microk8s/issues/3227

k0s is better but also has a lot of bugs. it's the closest to vanilla kubernetes among all the distributions.

> like the simplest GPU support

linux users should be ready to install the nvidia device plugin. if they can't do that, they're never going to succeed in running a gpu accelerated application on their cluster anyway.

> like bootstrapping

in my experience, writing all the bootstrap scripts is painful. but now that there's chatgpt, so much of the drudgery as gone away.

MicroK8S to spin up a Kubernetes cluster

They now power my microk8s/x86 cluster (in addition to my 8-node Raspberry Pi4 ARM64 microk8s cluster), microceph cluster and my LXD cluster, and all are configured with WOL, so I can bring up the cluster from any machine in the homelab, on demand.