[pacala]

I wonder how much of that attitude was caused by an overstretched team with no effective scaling mechanism in place. No, "open source" does not automatically mean "scalable team". Part of Kubernetes success is its ability to scale up the community, empowering multiple entities to meaningfully contribute.

[faitswulff]

Scaling is an issue with any company, but judging by a friend's description of working there, there's almost certainly a large company culture / attitude factor as well.

[alias_neo]

I don't have an answer to the why, but I can say that in the 5+ years I've been using it daily, the issues I've faced have been reciprocated by others others, and GitHub reflects this.

Some of the issues are solved by the likes of K8s, but many of us don't want or need K8s for our use cases. Other issues are resolved by other told, and yet still others are only resolved with effort (you still can't expose/bind a port range, e.g. 10000 UDP ports in Docker without killing your server).

[0xDEFC0DE]

At the same time, I gather it's really, really hard to write software that satisfies a lot of use cases across a lot of businesses without having to be somewhat opinionated.

[pacala]

True! Another part of Kubernetes success is the fact that it's core architecture is sound, scalable for both workloads and features.