3 ms·
This is not my experience with k8s at all. Sure, everything will work fine when it works (although I don't think it's as easy as you make it out to be), but whe
by arp242 8y ago
This is not my experience with k8s at all. Sure, everything will work fine when it works (although I don't think it's as easy as you make it out to be), but when something unexpected happens it's a massive pain to debug.
"8 hours" initial investment is already large for a small/simple scenario; and it's not the full costs either, because fixing problems will be much harder/time-consuming.
I wrote a post about this just the other day[1]:
> What does it mean for a framework, library, or tool to be “easy”? There are many possible definitions one could use, but my definition is usually that it’s easy to debug. I often see people advertise a particular program, framework, library, file format, or something else as easy because “look with how little effort I can do task X, this is so easy!” That’s great, but an incomplete picture.
[..]
> Abstractions which make something easier to write often come at the cost of make things harder to understand. Sometimes this is a good trade-off, but often it’s not. In general I will happily spend a little but more effort writing something now if that makes things easier to understand and debug later on, as it’s often a net time-saver.
[1]: https://arp242.net/weblog/easy.html https://arp242.net/weblog/easy.html
- ravedave5 8y agoWe spent weeks and weeks at work working through k8 performance issues, we got nowhere and fell back to a crappy work around.
- techntoke 8y agoSounds like it wasn't K8S performance issues then, but performance issues with your environment.
- Carpetsmoker 8y agoI don't think it matters if it was a k8s issue or not, what matters is that k8s made it much harder to get to the bottom of it. We actually had similar issues when we deployed k8s. In the end it turned out to be a misconfiguration, but took weeks to figure out, and only because our entire dev team looked at it (and not the k8s guru who implemented it all).
- ownagefool 8y agoYou need to be able to debug and separate out problems no matter your infrastructure. You'll get lots of SMEs that can use a product but can't trace or profile, and it isn't the underlying products fault beyond hype driven development. If you want to spin up ephemeral environments to test your code, kube is one of the easier ways to achieve this. Similarly, it helps you solve problems such as app health, dying nodes, etc. It's a great product, especially when you've scaled past a single app and a single team, but that's largely because it's a framework, similarly to how rails is, and if you do something serious with it, you need to know how it works. The alternative is you build your own framework, but your new hires will prefer k8s. Realistically though, use GKE and forget about it until you grow. Otherwise you're using something closed or something bespoke, the latter being fine for a 1-2 man team, but kinda pointless when you can have a managed service.
- Carpetsmoker 8y ago> The alternative is you build your own framework These are far from the only two options available.
- yebyen 8y agoI agree, but it's fun and sometimes enlightening to let the debate be framed this way Compare[1] Chapter 1: > “Nobody has ever built cloud-native apps without a platform. They either build one themselves or they use Cloud Foundry.” [1]: https://content.pivotal.io/ebooks/cloud-foundry-the-cloud-native-platform https://content.pivotal.io/ebooks/cloud-foundry-the-cloud-na...
- Carpetsmoker 8y agoYou do realize you are quoting advertising material here? "Use our product or reinvent it yourself" :-/ > it's fun and sometimes enlightening to let the debate be framed this way Not really. It's fairly close-minded.
- foobiekr 8y agoI strongly agree with "something unexpected happens it's a massive pain to debug"; though it's somewhat under-appreciated how often this applies to open source SW in general.
- sqrt17 8y agoHaving to debug closed-source software is not fun either. Plus in many cases you're left with crappy documentation and no access to the source code.