4 ms·
> That's not how LTS is supposed to work. You should be able to uograde effortlessly with minimum risk. How do you do that on something as complex and with as
by sofixa 3y ago
> That's not how LTS is supposed to work. You should be able to uograde effortlessly with minimum risk.
How do you do that on something as complex and with as many moving parts as Kubernetes? And how do you as an operator update that many things without checking there's no breaking changes in the patch?
- x86x87 3y agobingo! how do you do it? and do you want that kind of complexity to begin with?
- sofixa 3y agoDon't ask me, I'm firmly in the HashiCorp Nomad camp: https://atodorov.me/2021/02/27/why-you-should-take-a-look-at-nomad-before-jumping-on-kubernetes/ https://atodorov.me/2021/02/27/why-you-should-take-a-look-at... (Note: quite old, some things are no longer true most notably around Nomad downsides)
- rigrassm 3y agoI'm with you, Nomad is highly underrated!
- Rantenki 3y agoWe upgrade our distros pretty much fearlessly, all the time. While I have had breakage from Kernel upgrades, they've been very rare (and generally related to third party closed drivers). Kubernetes is _not_ more complicated than the Linux kernel, but it is much more dangerous to upgrade in place.
- eddythompson80 3y ago> Kubernetes is _not_ more complicated than the Linux kernel, but it is much more dangerous to upgrade in place. eh, the kernel is an incredibly mature project with 1 machine scope. The kernel also has decades of operating systems research and literature to build on. Kubernetes in comparison is new, distributed and exploring uncharted territory in terms of feature set and implementation. Sometimes bad decisions are made, and it's fair to not want to live with them forever. The kernel project looks very different today than it did in 1999. There is a happy medium though, especially that Kubernetes is kinda far from it.
- x86x87 3y agoSpoiler alert: k8s is not in uncharted territory. Erlang and its runtime discovered and solved most of the problems in the 80s. We are slowly rediscovering this the same way react discovered the event loop that Windows had discovered in the 90s.
- eddythompson80 3y agoErlang solved the problem by making a custom VM that abstracts the network away for the most part and is pretty opinionated about how you do that. Kubernetes is not that. I don't see how Erlang is relevant here. You can run Erlang applications on kuberntes, not the other way around.
- jen20 3y agoMy answer is simple: don't. Use something far simpler and with fewer moving parts than Kubernetes, and something where crucial parts of the ecosystem required to make things even basically work are not outsourced to third party projects. Nomad is a good solution.