cuber-gem VS microk8s

Here's the link: https://github.com/cuber-cloud/cuber-gem

I know this is a very dicey question - helm is also arguably a deployment standard. But then, the value of a ton of different projects (like https://github.com/cuber-cloud/cuber-gem Acorn.io ) is an opinionated/declarative application model. Even Docker Compose standard is one.

It looks like a fairly thin wrapper around Docker, Heroku buildpacks, and this template file: https://github.com/cuber-cloud/cuber-gem/blob/master/lib/cub...

You can also consider Cuber (https://github.com/cuber-cloud/cuber-gem) to deploy multiple apps on the same cluster (I am the developer). Each app is in its own namespace so you can definitely do that.

This is what we built/use: https://github.com/cuber-cloud/cuber-gem

Cuber has a good starting template that works for most applications (Heroku-like but using a K8s template): https://github.com/cuber-cloud/cuber-gem

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.