[Rantenki]

We 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]

> 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]

Spoiler 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]

Erlang 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.