3 ms·
And, as mentioned in a sibling comment, as complex as the K8s project is now, upgrades break things. They regularly break APIs, CLI arguments, tooling, document
by falcolas 8y ago
And, as mentioned in a sibling comment, as complex as the K8s project is now, upgrades break things. They regularly break APIs, CLI arguments, tooling, documentation, integrations, and just about everything else.
Having your entire k8s infrastructure go down due to a "oopsie" in an upgrade is a risk. And mitigating these risks takes time and effort.
- toomuchtodo 8y agoAs an ex-devops/infra guy, every day I'm ecstatic I don't have to wrangle k8s. These are not attributes of production infrastructure tooling. My hat is off to all of you in the trenches.
- falcolas 8y agoI still struggle with the idea that an infrastructure software version can go out of support within 6 months. I still recall the days where we would wait 6 months on a new version of software, just to let it settle and get its initial patches out of the way. I hearken back to a snippet from a recent article: > 2014: We must adopt microservices to solve all the problems with monoliths > 2016: We must adopt Docker to solve all the problems with Microservices > 2018: We must adopt Kubernetes to solve all the problems with Docker What's next? "We must adopt Rancher to solve all the problems with K8s"?
- deleted 8y ago[deleted]