Local Kubernetes for Linux — MiniKube vs MicroK8s

In this article, we will focus on Linux. Minikube is still a contender here. Unfortunately, the Docker desktop is not available for Linux. Instead, we are going to look at MicroK8s, a Linux only solution for a lightweight local Kubernetes cluster.

We are evaluating these solutions and providing a short comparison based on ease of installation, deployment, and management.

To get in-Depth knowledge on Kubernetes you can enroll for a live demo on
Kubernetes online training

Minikube

Minikube runs a single-node Kubernetes cluster inside a VM (e.g. Virtualbox ) in your local development environment. The result is a local Kubernetes endpoint that you can use with the kubectl client. Minikube supports most typical Kubernetes features such as DNS, Dashboards, CNI, NodePorts, Config Maps, etc. It also supports multiple hypervisors, such as Virtualbox, kvm, etc.

Installation

In order to install Minikube to Linux, you can follow the steps described in the official documentation( https://github.com/kubernetes/minikube). In our evaluation, we used Ubuntu 18.04 LTS with VirtualBox support using the following commands:

Take your career to new heights of success with Kubernetes Training

After installation of Minikube, the kubectl tool needs to be installed in order to deploy and manage applications on Kubernetes. You can install kubectl by adding a new APT repository using the following command:

Finally, after a successful installation, you can start your minikube by issuing the command:

Microk8s

Microk8s is a new solution for running a lightweight Kubernetes local cluster. It was developed by the Kubernetes team at Canonical. It is designed to be a fast and lightweight upstream Kubernetes installation isolated from your local environment. This isolation is achieved by packaging all the binaries for Kubernetes, Docker.io, iptables, and CNI in a single snap package (available only in Ubuntu and compatible distributions).

By installing Microk8s using snap, you are able to create a “clean” deploy of the latest upstream Kubernetes on your local machine without any other overhead. The Snap tool is taking care of all needed operations and can upgrade all associated binaries to their latest versions. By default, Microk8s installs and runs the following services:

• Api-server
• Controller-manager
• scheduler
• kubelet
• cni

Additional services such as the Kubernetes dashboard can be easily enabled/disabled using the microk8s.enable and microk8s.disable command. The list of available services are:

1. Dns
2. Dashboard, including grafana and influxdb
3. Storage
4. Ingress, Istio
5. Registry
6. Metrics Server

Installation

Microk8s can be installed as a single snap command, directly from the Snap store.

This will install the microk8s command and an api-server, controller-manager, scheduler, etcd, kubelet, cni, Kube-proxy, and Docker. To avoid any conflicts with an existing installation of Kubernetes, Microk8s adds a microk8s.kubectl command, configured to exclusively access the new Microk8s install.

When following any generic Kubernetes instructions online, make sure to prefix kubectl with Microk8s. To verify that installation was successful, you can use the following commands to retrieve available nodes and available services respectively:

Management

As mentioned above, Microk8s installs a barebones upstream Kubernetes. This means just the api-server, controller-manager, scheduler, kubelet, cni, and kube-proxy are installed and run. Additional services such as kube-dns and the dashboard can be run using the microk8s. enable command.

You can verify that all services are up and running with the following command:

You can access any service by pointing the correct CLUSTER_IP to your browser. For example, you can access the dashboard by using the following web address, https://10.152.183.77. See image below for the dashboard:

Kubernetes dashboard

At any time, you can pause and restart all Kubernetes services and installed containers without losing any of your configurations by issuing the following command. (Note that this will also disable all commands prefixed with Microk8s.)

Removing Microk8s is very easy. You can do so by first disabling all Kubernetes services and then using the snap command to remove the complete installation and configuration files.

Deployment

Deploying an nginx service is what you would expect, with the addition of the Microk8s prefix:

You can monitor your deployed services using the command:

Now you are ready to access your deployed web service by pointing the following web URL to your preferred web browser: http://10.152.183.125

Conclusions

After looking at all solutions, here are our results…

Minikube is a mature solution available for all major operating systems. Its main advantage is that it provides a unified way of working with a local Kubernetes cluster regardless of the operating system. It is perfect for people that are using multiple OS machines and have some basic familiarity with Kubernetes and Docker.

Pros:

1. Mature solution
2. Works on Windows (any version and edition), Mac and Linux
3. Multiple drivers that can match any environment
4. Can work with or without an intermediate VM on Linux (vmdriver=none)
5. Installs several plugins (such as dashboard) by default
6. Very flexible on installation requirements and upgrades

Cons:

1. Installation and removal not as streamlined as other solutions
2. Can conflict with a local installation of other tools (such as Virtualbox)

MicroK8s is a very interesting solution as it runs directly on your machine with no other VM in between.

Pros:

1. Very easy to install, upgrade, remove
2. Completely isolated from other tools in your machine
3. Does not need a VM, all services run locally

Cons:

1. Only available for Snap supported Linux Distributions
2. Relatively new, possible unstable
3. Minikube can also run directly on Linux (vm=driver none), so MicroK8s value proposition is diminished

Top 10 Kubernetes tips and tricks

Follow us on Twitter 🐦 and Facebook 👥 and Instagram 📷 and join our Facebook and Linkedin Groups 💬.

To join our community Slack team chat 🗣️ read our weekly Faun topics 🗞️, and connect with the community 📣 click here⬇

If this post was helpful, please click the clap 👏 button below a few times to show your support for the author! ⬇