3 ms·
> which is 10-15x more complicated You can learn k8s in a day. It's really simple. > various ingress controllers and weird quirks that are completely differen
by echelon 3y ago
> which is 10-15x more complicated
You can learn k8s in a day. It's really simple.
> various ingress controllers and weird quirks that are completely different on each cloud provider
Which are thoroughly documented and not that hard to implement or understand. You'd be reading about each cloud's nonstandard ingress even without k8s.
The beauty of k8s is you can run your software locally and have a much easier time lifting and shifting to another cloud.
Fitting to the shape of a cloud provider is a great way to never leave.
Another benefit of k8s is that you treat your services as cattle you can easily spawn and kill. Adoption of k8s naturally leads to anti-fragility, anti-brittle best practices.
- hosh 3y agoI think being able to abstract the cloud providers is secondary to k8s’s ability to self-heal and its modularity. But I think most developers don’t care, and instead, should interact with a platform built with Kubernetes as a foundation.
- profunctor 3y agoMaybe this is because I’m not that smart but I could not learn real kubernetes in a day. I had to build a system for loading models and returning predictions over a HTTPS api. It had to connect to storage to load the model, needed secrets etc. It took more than a day. And I think it would take most people more than a day to go from zero to able to create a useful, real world deployment in a day. I’m sure you can rush through the documentation in a day but I wouldn’t call that learning.
- bg24 3y agoHaving spent 4 years working with kubernetes (though as a PM, but pretty hands-on), getting started is easy - like in less a week. The problem happens when you run into issues. That can suck up lot of time. Also if you are new to containers, it might not be a good step to venture into k8s.