Hacker News Reader

Comment by n_ary | Hacker News Reader

Honestly, getting started with k8s is easy. Get started with minikube on local desktop. Once you get the feel for it, try configuring a multi-node cluster using k3s on DigitalOcean or Hetzner and eventually using managed AKS/EKS/GKE if you feel the need.

View on HN

I was surprised when I setup k3d the first time, I had a multi-node cluster on my (4 year old) desktop and was able to deploy a multi-node service I wanted to test out without any problems. I would highly recommend k3d if you don't want to pay for cloud servers and don't actually need either high-availability or the CPU power of 3 servers. Also, your desktop is probably more powerful than any base-tier server.

What do you use for load balancing and ingress? Do you rely on service discovery in this setup? I always get stuck figuring out how to get traffic into the cluster properly while allowing for graceful fault tolerance.

I’ve had success with MetalLB to dynamically announce a single IP for the ingress controller but that feels a bit overkill for a simple lab setup.

Are you asking about my "clusters" or k3d?

For my clusters, they're all single-node and therefore not fault-tolerant clusters, so I don't worry about graceful fault tolerance. I just use nginx-ingress which opens a port on the node (via iptables, so don't expect `lsof` to help!). Then my router port-forwards so my home IP:80 eventually hits my NUC

Reply on news.ycombinator.com