Service Mesh

Traefik is a simple and eficient load balancer that can be used at any environment, but if is used with docker or kubernetes can use the service discovery funcionality to allow you the deploy your services and it automaticaly discover all of your replicas and where are running

Used with kubernetes, acts as a ingress controller ( version 1.7 ), so you can use the standard ingress manifest to deploy your services

• Service discovery
• Path routing
• Letsencrypt integration

At the last post k3s introduction I told that I was not going to install traefik because is more dificult to make changes on it, so now we are going to learn how to install and use it.

At this point I indicate that to facilitate the dns resolution of the differents deployments we are going to use the nip.io domain, to allow us to call every deployment with dns its name and for that the ingress manifest must have a domain name.

First we are going to install traefik 1.7 at our kubernetes cluster. We can do that with 2 approaches

• As a Deployment so you can choose how many replicas are running at the cluster.
• As a DaemonSet so one replica of traefik is running at every node of your cluster.

k3s.io is a full operating kubernets environment that can help you to run your deployments for example at your laptop. It is more lightweight than microk8s or minikube.

K3s get its lightweight goal by removing features out of the Kubernetes binaries (legacy, alpha, and cloud-provider-specific features), also use containerd instead of docker, use sqlite3 as database instead of etcd.

FEATURES:

• k3s binary: 52Mb
• containerd instead of docker
• Helm Chart support
• sqlite3 database ( support for other databases )
• local storage class provisioner