Member-only story
Production like Kubernetes on Raspberry Pi: Ingress
In this series i want to create a production grade kubernetes cluster which can be very useful at least in a home environment but maybe also for some small bussiness environments.
The Plan
- Part 1: Setup a 3 node k3s cluster with 2 Master and 1 worker nodes (more worker nodes can be added later on)
- Part 2: Deploy metallb (load-balancer) to get traffic routed to the cluster.
- Part 3: Deploy traefik as a ingress controller to reach services by dns name
- Part 4: Deploy cert-manager for automatic creation of let’s encrypt certificates
- Part 5: Deploy longhorn for persistent-storage. (An alternative is using an NFS-Server as described here)
- Part 6: Cluster backup with velero.
- Part 7: Metrics with promethues and logging with loki
- Part 8: Use flux-cd for storing cluster description in git for rebuilding the cluster
The problem
In the last part we added a load-balancer which enabled having one ip to access the whole cluster. But how can i reach a specific service in the cluster?
Ingress-controller is the keyword.
Solution: Ingress-controller
To access service A we type in our browser “service-a.local” the request goes through our router to the load-balancer which can reach the cluster. When we reach the cluster the request goes to the ingress-controller which is listening on port 80 and port 443.
The ingress-controller is requested with the dns-name “service-a.local” and route the request to the specific service A on the matching node.
The implementation
We use traefik as our ingress-controller. The easiest way to install traefik is with the helm package manager. Follow…
