mprweb VS microk8s

Debian has the MPR https://mpr.makedeb.org/

https://mpr.makedeb.org/ this is the link.

I know the MPR is a thing, but I've always found it unwieldy to use.

So the main difference from something like MPR is that it does that same thing, but for more packages, not only .deb files?

Regarding system repositores, it's generally best to avoid tampering with system repositories like this because it'll cause problems with release upgrades down the line. But if you really want to, look into https://mpr.makedeb.org/ with the expectation that a release upgrade with these packages installed will most likely fail.

makedeb - Like makepkg, but produces installable *.deb files. There are already lots of packages in the MPR

Actually exists! https://mpr.makedeb.org/

Mist is powered by the MPR, an AUR-like repository that's also for Debian and Ubuntu based systems (of which I'm also the project lead for, as well as the makedeb project listed below). In short, it uses pretty much the same PKGBUILD format that you'd see on Arch Linux, but uses them to build .deb packages instead of Arch Linux packages.

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.