What is K3s?
For the approach of a Demo/Development environment this becomes a great improvement on what we have talked about previously at Kubernetes: Create a minimal environment for demos , where we can see that the creation of the Kubernetes environment is complex and requires too many resources even if Ansible is the one who performs the difficult work.
We will see if what is presented to us is true and if we can include the Metallb tools that will allow us to emulate the power of the Cloud providers balancers and K8dash environments that will allow us to track the infrastructure status.
We configure the virtual machines in the same way as for Kubernetes, with the installation of dependencies:
#Debian sudo apt-get install -y ebtables ethtool socat libseccomp2 conntrack ipvsadm #Centos sudo yum install -y ebtables ethtool socat libseccomp conntrack-tools ipvsadm
We download the latest version of k3s from https://github.com/rancher/k3s/releases/latest/download/k3s and put it in
/usr/bin with execution permissions. We must do it in all the nodes.
What is K3s?
K3s includes three “extra” services that will change the initial approach we use for Kubernetes, the first is Flannel, integrated into K3s will make the entire layer of internal network management of Kubernetes, although it is not as complete in features as Weave (for example multicast support) it complies with being compatible with Metallb. A very complete comparison of Kubernetes network providers can be seen at https://rancher.com/blog/2019/2019-03-21-comparing-kubernetes-cni-providers-flannel-calico-canal-and-weave/ .
The second service is Traefik that performs input functions from outside the Kubernetes cluster, it is a powerful reverse proxy/balancer with multiple features that will perform at the Network Layer 7, running behind Metallb that will perform the functions of network layer 3 as balancer.… Read the rest “K3s: Simplify Kubernetes”