k3s VS minikube

In this demo, we will be using k3d a lightweight wrapper to run k3s (Rancher Lab’s minimal Kubernetes distribution) in docker, to create 4 separate clusters named control-plane, cluster-1, cluster-2, and cluster-3 respectively.

To run the demo locally, we recommend k3d a lightweight wrapper to run k3s (Rancher Lab’s minimal Kubernetes distribution) in docker.

I've been messing around with k8s (k3s) lately, and got to the "issue" of downtime/inconsistencies caused by one of multiple workers being down, who had pods running on them. I found a couple useful parameters here that helped me reduce the time needed to redeploy the old pods on other nodes, as well as stop sending requests to the NotReady node. But that got me thinking, how long should k8s wait before doing these things? Or is there perhaps a better option for increasing avaliability?

Local Kubernetes clusters are clusters that are running on the individual computer of the developer. There are many tools that provide such an environment, such as Minikube, microk8s, k3s, or kind. While they are not all the same, their use as a development environment is quite comparable.

Since the developer is the only one who has to access this cluster for development, local clusters can be a feasible solution for this purpose. Over time, several solutions have emerged that are particularly made for running Kubernetes in local environments. The most important ones are Kubernetes in Docker (kind), MicroK8s, minikube and k3s. For a comparison of these local Kubernetes options, you can look at this post.

With local Kubernetes environments such as minikube or k3s, developers can create their own Kubernetes clusters on their local computers. This often leads to developers struggling with the management and setup of these pared-down Kubernetes technologies that are also not completely realistic compared to “real-world”, cloud-based environments. The upside of this approach is that the developers have full control over their environment and can independently create it whenever they need it.

K3d - a lightweight wrapper to run k3s in docker.

With the containerized Node.js/Express API, I could run multiple containers, scaling to handle more traffic. Using a tool called minikube, we can easily spin up a local Kubernetes cluster to horizontally scale Docker containers. It was possible to keep one shared instance of the database, and many APIs were routed with an internal Kubernetes load balancer.

Install Minicube - a tool that allows us to spin up a Kubernetes cluster in a local machine Run minikube start to start your Kubernetes cluster Run minikube dashboard to spin up a web-based user interface that allows you to manage your Kubernetes cluster

If you're just messing around, just use kind (https://kind.sigs.k8s.io) or minikube if you want VMs (https://minikube.sigs.k8s.io). Both work on ARM-based platforms.

You can also use k3s; it's hella easy to get started with and it works great.

$ minikube addons enable dashboard 💡 dashboard is an addon maintained by Kubernetes. For any concerns contact minikube on GitHub. You can view the list of minikube maintainers at: https://github.com/kubernetes/minikube/blob/master/OWNERS ▪ Using image docker.io/kubernetesui/dashboard:v2.7.0 ▪ Using image docker.io/kubernetesui/metrics-scraper:v1.0.8 🌟 The 'dashboard' addon is enabled $ minikube addons enable metrics-server 💡 metrics-server is an addon maintained by Kubernetes. For any concerns contact minikube on GitHub. You can view the list of minikube maintainers at: https://github.com/kubernetes/minikube/blob/master/OWNERS ▪ Using image registry.k8s.io/metrics-server/metrics-server:v0.6.4 🌟 The 'metrics-server' addon is enabled $ minikube addons enable ingress 💡 ingress is an addon maintained by Kubernetes. For any concerns contact minikube on GitHub. You can view the list of minikube maintainers at: https://github.com/kubernetes/minikube/blob/master/OWNERS 💡 After the addon is enabled, please run "minikube tunnel" and your ingress resources would be available at "127.0.0.1" ▪ Using image registry.k8s.io/ingress-nginx/kube-webhook-certgen:v20230407 ▪ Using image registry.k8s.io/ingress-nginx/controller:v1.8.1 ▪ Using image registry.k8s.io/ingress-nginx/kube-webhook-certgen:v20230407 🔎 Verifying ingress addon... 🌟 The 'ingress' addon is enabled

A Kubernetes distribution: You need to install a Kubernetes distribution to create the Kubernetes cluster and other necessary resources, such as deployments and services. This tutorial uses kind (v0.18.0), but you can use any other Kubernetes distribution, including minikube or K3s.

3.Minikube ( https://minikube.sigs.k8s.io ):

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES7523fd2c20c7 gcr.io/google\_containers/k8s-dns-sidecar-amd64 "/sidecar --v=2 --..." 18 hours ago Up 18 hours k8s\_sidecar\_kube-dns-86f6f55dd5-qwc6z\_kube-system\_c1333ffc-e4d6-11e7-bccf-0021ccbf0996\_09bd438011406 gcr.io/google\_containers/k8s-dns-dnsmasq-nanny-amd64 "/dnsmasq-nanny -v..." 18 hours ago Up 18 hours k8s\_dnsmasq\_kube-dns-86f6f55dd5-qwc6z\_kube-system\_c1333ffc-e4d6-11e7-bccf-0021ccbf0996\_05c35e00a5a27 gcr.io/google\_containers/k8s-dns-kube-dns-amd64 "/kube-dns --domai..." 18 hours ago Up 18 hours k8s\_kubedns\_kube-dns-86f6f55dd5-qwc6z\_kube-system\_c1333ffc-e4d6-11e7-bccf-0021ccbf0996\_077ef463642b7 gcr.io/google\_containers/pause-amd64:3.0 "/pause" 18 hours ago Up 18 hours k8s\_POD\_kube-dns-86f6f55dd5-qwc6z\_kube-system\_c1333ffc-e4d6-11e7-bccf-0021ccbf0996\_039f618666205 gcr.io/google\_containers/kubernetes-dashboard-amd64 "/dashboard --inse..." 18 hours ago Up 18 hours k8s\_kubernetes-dashboard\_kubernetes-dashboard-vgpjl\_kube-system\_c1176a44-e4d6-11e7-bccf-0021ccbf0996\_0023b7b554a8c gcr.io/google\_containers/pause-amd64:3.0 "/pause" 18 hours ago Up 18 hours k8s\_POD\_kubernetes-dashboard-vgpjl\_kube-system\_c1176a44-e4d6-11e7-bccf-0021ccbf0996\_01c3bdb7bdeb1 gcr.io/google-containers/kube-addon-manager "/opt/kube-addons.sh" 18 hours ago Up 18 hours k8s\_kube-addon-manager\_kube-addon-manager-tpad\_kube-system\_7b19c3ba446df5355649563d32723e4f\_08a00feefa754 gcr.io/google\_containers/pause-amd64:3.0 "/pause" 18 hours ago Up 18 hours k8s\_POD\_kube-addon-manager-tpad\_kube-system\_7b19c3ba446df5355649563d32723e4f\_0b657eab5f6f5 gcr.io/k8s-minikube/storage-provisioner "/storage-provisioner" 18 hours ago Up 18 hours k8s\_storage-provisioner\_storage-provisioner\_kube-system\_c0a8b187-e4d6-11e7-bccf-0021ccbf0996\_067be5cc1dd0d gcr.io/google\_containers/pause-amd64:3.0 "/pause" 18 hours ago Up 18 hours k8s\_POD\_storage-provisioner\_kube-system\_c0a8b187-e4d6-11e7-bccf-0021ccbf0996\_0 I just did the Kubernetes minikube tutorial at https://github.com/kubernetes/minikube, and I cannot stop or remove these containers, they always get recreated.

https://github.com/kubernetes/minikube for local learning that's lightweight.

Haven’t dabbled with minikube yet, but there’s a whole thread about this error here: https://github.com/kubernetes/minikube/issues/9798