Setup On-premise Kubernetes with Kubeadm, MetalLB, Traefik and Vagrant

Google published Kubernetes as open-source in 2014, except a milk cow: the external connectivity (load balancer, ingress, DNS, etc). Other K8s cloud providers follow this strategy, too. They use own solution because it’s a rational cost model for them and fits to their infrastructure. If a company would like to setup on-premise solution, it has to be solved with open-source solutions and/or with non-free, for example: Red Hat OpenShift.

Free link to this article: https://pgillich.medium.com/setup-on-premise-kubernetes-with-kubeadm-metallb-traefik-and-vagrant-8a9d8d28951a?source=friends_link&sk=a91bd4da64b020a0430b5f124b4c59f4

Components

Depending on the expectations and requirements, below components may be used:

• External Load Balancer for K8s Services (type: LoadBalancer), for example: MetalLB, Porter
• Ingress Controller (reverse proxy, HTTP router), for example: Nginx, Contour, HAProxy, Traefik
• Cert Manager, for example: Let’s Encrypt, BuyPass
• External DNS, for example: ExternalDNS
• Persistent Volume, for example: NFS, GlusterFS

Setup a cluster which uses above components is a long journey, see an article series…