3 ms·
I’ve only ever seen a single dev team managing their own K8s cluster. If by deploy you mean “they merge a branch which triggers a lot of automation that causes
by sgarland 2y ago
I’ve only ever seen a single dev team managing their own K8s cluster. If by deploy you mean “they merge a branch which triggers a lot of automation that causes their code to deploy,” you don’t need K8s for that.
Don’t get me wrong, I like K8s and run it at home, and I’d take it any day over ECS or the like at work, but it’s not like you can’t achieve a very similar outcome without it.
- k8sToGo 2y agoOf course. And I can achieve a Webserver in C. Doesn’t mean it’s the best way given the circumstances. There are many ways in tech to achieve the same result. I don’t understand why people constantly need to point that out. I also don’t understand why k8s ruffles so many feathers. Reminds me a bit of Linux vs windows vs Mac debates.
- sgarland 2y agoK8s ruffles my feathers because it’s entirely too easy to build on it (without proper IaC, natch) without having any clue how it works, let alone the underlying OS that’s mostly abstracted away. /r/kubernetes is more or less “how do I do <basic thing I could have read docs for>.” I’m a fan of graduated difficulty. Having complex, powerful systems should require that you understand them, else when they break – and they will, because they’re computers – you’ll be utterly lost.