4 ms·
"we didn’t find enough reason to figure out if kubernetes was a better option." Then proceeds to name every problem kubernetes fixes
by vuyani 10y ago
"we didn’t find enough reason to figure out if kubernetes was a better option."
Then proceeds to name every problem kubernetes fixes
- eggie5 10y agohaha, that's exactly what I said in my comment.
- swap32 10y agoYes. My bad! We really should have invested some time evaluating Kubernetes.
- gtaylor 10y agoIf you don't want to stand up your own cluster for eval, fire up Google Container Engine for a few days. It's cheap and very well done.
- x0x0 10y agoI think the problem started far earlier. The author couldn't name a single clear rationale for using docker at all. One client asked them to, but why continue? They were using virtualenv and it mostly worked fine. So why docker period? Complexity for the sake of complexity? The rest of the article then basically says complex things are complex.
- swap32 10y agoWell, I didn't name the reasons of why we continued using Docker because I thought they were obvious to any serious docker user. The reasons are all the promises that docker makes to you without actually telling you the complexities involved. Namely - the promise of better portability, better dev-prod environment replication (You can even run vagrant for dev portability but you wouldn't use it for prod, but with docker, its just docker everywhere), better scalability with managing clusters and deployments, and so on... without actually running heavy virtual machines. And no, as per the docker promise, it wasn't supposed to be complex.