3 ms·

I half agree with you here. It is actually quite simple, but everything in Kubernetes is very explicit, which is good, but also intimidating. If you've never wo

• arinlen 4y ago
  > If you've never worked with Kubernetes before then it's a lot of added complexity without clear benefits. Unless you're someone who only had to work on a monolith deployed to a single box somewhere, Kubernetes adds zero complexity to the problem you're already dealing with. In fact, Kubernetes simplifies the whole problem of running stuff on a cluster. Network, security, deployment, observanility... That's all provided out of the box. And you can rollback whole deployments with a single command. Heck, even ssh-ing into a container, regardless of where it's running, became trivial. How is that harder than deploying stuff to boxes somewhere?
  • treis 4y ago
    >Unless you're someone who only had to work on a monolith deployed to a single box somewhere, I think the point is that 90%+ of websites are fine with a few monoliths behind a load balancer. That set up can handle low thousands of requests per second in Rails/Django/etc. Maybe low 10 thousands with a more performant language. And it's not just k8s. It's the whole microservice/SOA that comes with it. It ramps up the complexity of everything and is a constant time sink in my experience.