mfa2fa.com started as a security consultancy site — MFA/2FA integration, SIEM deployment, network security, and cloud infrastructure services. It ran on a standard LAMP stack: Apache, WordPress, MySQL on a single VPS. Functional, but fragile.
After 5+ years of commercial Linux and infrastructure work spanning Kubernetes, Ansible, CI/CD pipelines, and multi-cloud platforms (AWS, OCI, Azure), the decision was made to migrate the site to a fully self-hosted Kubernetes platform — not just as a practical improvement, but as a living portfolio piece.
The domain now serves three distinct sections from a single nginx reverse proxy on an OVH VPS:
wordpress6 namespace as a Kubernetes Deployment. Accessible at /wp/ as the migration baseline.Everything runs on a 3-node homelab cluster, proxied via an OVH VPS over WireGuard:
Running Kubernetes in a homelab is one thing. Documenting it properly — with architecture decisions, gotchas, and runbooks — is what separates a learning exercise from professional infrastructure work.
These docs are written the way a senior engineer would write them: assuming the reader knows Linux and containers, skipping the basics, focusing on decisions and lessons learned. The kind of documentation you'd want to find if you were inheriting this infrastructure.
Every command in these docs was run against real infrastructure. Every gotcha documented was a real problem. Nothing is theoretical.