The problem to me is that someone needs to maintain it. Setting it up is simple (k3s makes it very simple), but since you depend on it, if it breaks, you are in trouble as debugging is not exactly simple, so better use a supportable ready-out-of-the-box solutions like Rancher, Charmed Kubernetes or kublr incl. Support contract. They make it easier and support contracts are probably cheaper than the ingress costs... Source: over 3 years ago

Kubernetes on the backend used to utilize docker for much of its container runtime solutions. One of the modular features of Kubernetes is the ability to utilize a Container Runtime Interface or CRI. The problem was that Docker didn't really meet the spec properly and they had to maintain a shim to translate properly. Instead users could utilize the popular containerd or cri-o runtimes. These follow the Open... - Source: dev.to / 4 months ago

Multiple container runtimes are supported, like conatinerd, cri-o, or other CRI compliant runtimes. - Source: dev.to / 6 months ago

Install container runtime on all nodes. We will use cri-o. - Source: dev.to / 6 months ago

Container Runtime Interface (CRI) is one of the important parts of the Kubernetes cluster. It is a plugin interface allowing kubelet to use different container runtimes. And recently CRI-O container runtime has been announced as a CNCF Graduated project. I thought of writing a blog on CRI-O and how to set up a single-node Kubernetes cluster with Kubeadm and CRI-O. - Source: dev.to / 11 months ago

CRI-O: This is an open-source container runtime designed for use with Kubernetes. It is a lightweight and stable environment for containers. It also complies with the Kubernetes Container Runtime Interface (CRI), making it easy to integrate with Kubernetes. - Source: dev.to / about 1 year ago