Comment

Comment by bowersbros

I've ran into so many problems trying to get a nice setup for my local development that matches similar to our production setup. I usually have completely separate docker compose setup locally, and a kubernetes setup of some kind in production.

These behave fairly similar, until I need to work on the ingress, or network policies, or anything else that is kubernetes specific.

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.

I'm thinking of packaging it up into a justfile and documenting it, but wondered how other people work on these sort of things. Do you just accept the shortcomings and test in staging envs for kubernetes specific changes?

parent bowersbros 1 month ago

No comments yet

Be the first to share your thoughts.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton