One Public IPv4, Many Kubernetes Apps

I have an on-premise Kubernetes cluster with persistent storage. Now it’s time to find a way to expose my applications to the internet.

I only have a single public IPv4 address and a /24 private subnet behind NAT, managed by OPNsense. This means I’ll need a few creative (and slightly dirty) hacks to make everything work.

I’m starting to realize how much the cloud has spoiled me. Without unlimited load balancers and public IP addresses, things quickly become a bit more complex.

For this setup, my main tools will be MetalLB and NGINX Ingress. NGINX Ingress will be retired soon, and I plan to replace it in the near future. However, for a home lab environment it will work just fine for now.

This setup is far from perfect, so don’t try this in real production.

Continue reading “One Public IPv4, Many Kubernetes Apps” →

Persistent volume for on premise kubernetes cluster with NFS

Data will be stored on Debian VM with NFS. Provisioning persistent volumes will be automated like in the cloud. Every PVC will have his own sub directory on NFS. I will use Kubernetes NFS Subdir External Provisioner and Helm. Helm is installed on jumpbox with access to the existing cluster. Setup is for home lab, special security for NFS server will not be implemented.

Continue reading “Persistent volume for on premise kubernetes cluster with NFS” →

Start Kubernetes cluster on Debian 13 with kubeadm v1.35 on proxmox VM in 2026

Kubernetes cluster for a small lab installed on Debian virtual machines. Set-up just one instance first, clone it later. One control plane, two worker nodes. Official Documentation

Requirements:

  • Debian 13 trixie
  • Network connectivity between the VMs. Every VM has unique MAC address, IP address, hostname
  • 2 GB or more of RAM per machine (any less will leave little room for your apps).
  • 2 CPUs or more for control plane machines.
Continue reading “Start Kubernetes cluster on Debian 13 with kubeadm v1.35 on proxmox VM in 2026” →