5 ms·
You nailed it in the first sentence. The blog post pretty much boils down to "k8s looks good but we were too lazy to learn how to use the thing, so we opted int
by avip 7y ago
You nailed it in the first sentence. The blog post pretty much boils down to "k8s looks good but we were too lazy to learn how to use the thing, so we opted into something else".
Fair enough, legit argument, but trying to make a "counter-k8s" case based on that is not very convincing.
- politelemon 7y ago> but we were too lazy This is unnecessarily dismissive and contributes to what makes HN a toxic place for discussions. They've already addressed the reasons.
- avip 7y agoPoint taken. However, the part about "why not kubernetes" reads: [...] we started adding ever-more complex layers of logic to operate our services. As an example, Kubernetes allows [...] this can get quite confusing [...]. [...] this can lead to tight, implicit coupling between your project and Kubernetes. [...] it’s tempting to go down that path and build unnecessary abstractions that can later bite you. [...] It takes a fair amount of time and energy to stay up-to-date with the best practices and latest tooling. [...] the learning curve is quite steep. So in short "it is complex so this and that may happen if you don't learn it properly". Ok, this reasoning applies a-priori to any tool.
- yjftsjthsd-h 7y agoNot every tool is equally complex or requires the same amount of learning. K8s has a reputation for being really high on the scale, so a reasonable team could consider it and then decide to use something less complex.