Hacker News Reader

Comment by thiht | Hacker News Reader

Honest question: what do you need a local Kubernetes for? It’s an orchestrator, surely you don’t need that in local? Don’t you have a way to mock your services? Or simple compose files for local integration?

I have worked with Marathon and Kubernetes in the last few years and never had the need to deploy them locally, it seems strange to even need that

View on HN

> Don’t you have a way to mock your services? Or simple compose files for local integration?

now your dev env is very different from how production works. Problems that show up in production won't easily be reproducible in dev. And if you are testing in this dev env, you aren't really testing, so implicitly turn to testing in production!

Dev environment. Mocks are a bad way to test certain things such as db interactions and generally can be a pain

Our team builds a custom controller for a CRD for which it’s useful to be able to run and develop locally, rather than have each developer on the team run their own cluster in the cloud

Definitely an indicator of bad design if you need this for development, but I can imagine it's sometimes useful for ops to play with different configurations.

If you're using k8s in prod and compose locally are you really testing integration?

No, I'm testing integration in my staging environment, which is also running kubernetes. Local development is not for testing integration. The interface and surfaces should be well defined enough that you don't worry about the difference between development and integration, but when you do have issues they should fall along the lines of "Differences easily spotted on the edge between compose and k8s" and if you can handle those, you're good

Reply on news.ycombinator.com