The Beginning


Every Senior Software Engineer needs hands-on infrastructure experience. That's why I built my homelab - a Kubernetes cluster running on bare metal.


Architecture Overview


My homelab runs on Kubernetes with the following components:


  • Kubernetes Cluster: 3-node cluster (1 control plane, 2 workers)
  • Storage: Local PersistentVolumes with dynamic provisioning
  • Networking: Flannel CNI with MetalLB for LoadBalancer services
  • Ingress: NGINX Ingress Controller with Cloudflare DNS
  • CI/CD: Jenkins with Kaniko for containerized builds
  • Security: Trivy for vulnerability scanning at build time
  • Monitoring: Prometheus + Grafana (coming soon)

Deployment Pipeline


Every service follows the same deployment pattern:


  1. Build: Kaniko builds container images inside Kubernetes
  2. Scan: Trivy scans for vulnerabilities
  3. Push: Images pushed to Docker Hub
  4. Deploy: Helm charts deploy to Kubernetes
  5. Expose: NGINX Ingress + Cloudflare for public access

    6. Why This Matters


    This homelab isn't just for fun - it's my learning laboratory for:


    • Kubernetes operations and troubleshooting
    • CI/CD pipeline design
    • Security best practices
    • Infrastructure as Code
    • Container orchestration at scale

    Stay tuned for more posts on my journey!