k3d local development environment with ArgoCD sync
A local development environment that mirrors a Kubernetes production setup by running everything locally on k3d, with manifests synced via ArgoCD. It addresses the mismatch between a separate local Docker Compose setup and Kubernetes in production, making it possible to work on Kubernetes-specific concerns like ingress and network policies locally. The setup is planned to be packaged as a documented justfile.
What it addresses
Local Docker Compose setups and production Kubernetes behave differently for Kubernetes-specific work such as ingress and network policies, making local development against production-like environments difficult.
Shared over time
Each entry reflects what was shared on that date. Details may have changed since then.
k3d local development environment with ArgoCD sync
A local development environment that mirrors a Kubernetes production setup by running everything locally on k3d, with manifests synced via ArgoCD. It addresses the mismatch between a separate local Docker Compose setup and Kubernetes in production, making it possible to work on Kubernetes-specific concerns like ingress and network policies locally. The setup is planned to be packaged as a documented justfile.
Problem: Local Docker Compose setups and production Kubernetes behave differently for Kubernetes-specific work such as ingress and network policies, making local development against production-like environments difficult.
Audience: Developers who need a local environment that matches their Kubernetes production setup
Posted by @bowersbros · Original comment ↗
“I've finally taken the plunge into running it all locally on k3d, and have a pretty nice setup now with the manifests syncing with ArgoCD.”