kubernetes-pfsense-controller VS php-k8s

It's over-engineered, but I wanted to try running k8s in my homelab to continue learning about networking; deploying a blog seemed like a perfect test case. The cluster uses Traefik, https://github.com/travisghansen/kubernetes-pfsense-controll... to sync service definitions to HAProxy, and MetalLB. The k8s service IPs are routable from my local network, as well as the MetalLB IPs, and MetalLB handles syncing them to pfSense using BGP. pfSense sends DNS for any *.k8s.home.arpa to k8s, so I can resolve e.g. blog.default.svc.k8s.home.arpa on my local network.

One interesting hiccup: I had to introduce a NAT at pfSense because MacBooks don't listen to ICMP redirects, the packet would go laptop -> router -> k8s and then k8s -> laptop. Since the MacBook ignored the ICMP redirect, it drops the reply packet.

I have leveraged some of the best practices in renoki-co/php-k8s, taking initially Laravel Eloquent as an example to build resources that have many attributes. You might want to take examples from there as it's coherent, and you're on a good path. :D

I was inspired by Laravel Eloquent ORM model. PHP K8S is some kind of ORM, but for Kubernetes Resources. Since the Kubernetes API is consistent, the implementation was DRY af, and I could write end-to-end testing with real-world examples like running MySQL as StatefulSet. Retrieve a model or build a model, you got anything you need in one class.