5 ms·

Literally, design by resume. I see it at my current workplace. Top talent guys are fucking around wit K8s even though we really have no use for it and could hos

Literally, design by resume. I see it at my current workplace. Top talent guys are fucking around wit K8s even though we really have no use for it and could host the whole shebang on a single EC2 instance and be no worse off for it. But that "won't scale" I'm told. Never mind our startup has a TAM that involves no more than 1,000 customers with maybe a dozen accounts each.

jskrablin 4y ago
It's not always about traffic scale. Sometimes it's about having a common deployment platform at different locations, on premise. Where relatively simple and small setups still bring a lot of value via pure convenience - suddenly everything is packed into Helm charts, running off basically identical CICD pipelines. But I guess that's not what "top talent guys" are interested in doing?
- dvtrn 4y ago
  Sometimes it's about having a common deployment platform at different locations, on premise. That’s fair, that’s valid, that doesn’t however strike me as a compelling case to go off and hoist all of your stuff into k8s if there’s other equally performant and fault tolerant methods of running your application that require less operational complexity and cognitive load to triage and resolve failures. It seems to me the problem you bring up would serve an engineering team well to solve and solidify even if the application isn’t running on k8s