kubernetes-failure-stories

This was posted elsewhere in this thread: https://github.com/hjacobs/kubernetes-failure-stories To me the biggest problem is the hype and massive salesmanship used to sells extreme complexity to gullible companies / individuals. K8s really is the J2EE application server of last century on steriods.

This is probably a good place to start: https://github.com/hjacobs/kubernetes-failure-stories (Not a balanced evaluation, just cherry-picking failures. But I suppose we're at the point in the hype cycle where it's easier to find success stories being talked about.)

An outage that is caused by k8s. You can pick a random from this list. https://github.com/hjacobs/kubernetes-failure-stories >>This is like saying you wouldn't take driving advice from me until I total a few cars No, I am saying you do not have enough experience with k8s. That is all. Totaling a car implying you are driving, using k8s implying that whoever wrote that particular part of k8s is driving. You have some control but ultimately you need to understand what is going on. As that list shows many companies who put k8s into production learned it in a hard way.

Yeah, so just posting here for anyone else that comes along. I managed to find someone on linkedin who cataloging this exact thing! https://github.com/hjacobs/kubernetes-failure-stories

Thanks for mentioning my collection of Kubernetes Failure Stories! I'll use this opportunity to encourage everyone to submit their own postmortems :-) --> https://github.com/hjacobs/kubernetes-failure-stories

Here's a whole collection of Kubernetes bloopers: https://github.com/hjacobs/kubernetes-failure-stories. I for one am glad people are sharing!

Kubernetes Failure Stories https://github.com/hjacobs/kubernetes-failure-stories

Yeah it is absolutely amazing for exactly that and yes it has a good approach to the distributed cluster problem. Once you put it in production there a very different picture. https://github.com/hjacobs/kubernetes-failure-stories I haven't had a single Kubernetes user who had it in production and did not have stability or performance issues with it. This is why I mentioned that I am not ready to trade my Hadoop outages and performance issues for Kubernetes ones.

Location: Greater Seattle, WA area Remote: Yes/only Willing to relocate: No Technologies: Kubernetes/k8s, Devops, Infrastructure, SRE, automation Email: jahodges419 - at - gmail.com Do you find yourself frustrated with a lack of visibility and increase in latency with your K8 clusters? How about Outages? Downtime? 5XXs thrown out of the blue? Wouldn't it be great to get back to a time when your infrastructure was just simple, functional, and 'boring'? If you've taken a look at some of the Real-World Kubernetes Failure Stories[1], you know that with great power comes great responsibility (and great opportunity for spectacular failure). Your engineers can tell you about that responsibility. They'll tell you that the savings you expected from Kubernetes has been overwhelmed by sunk engineering time troubleshooting, fixing, and maintaining yo

SEEKING WORK - Greater Seattle, WA area - 100% Remote Do you find yourself frustrated with a lack of visibility and increase in latency with your K8 clusters? How about Outages? Downtime? 5XXs thrown out of the blue? Wouldn't it be great to get back to a time when your infrastructure was just simple, functional, and 'boring'? If you've taken a look at some of the Real-World Kubernetes Failure Stories[1], you know that with great power comes great responsibility (and great opportunity for spectacular failure). Your engineers can tell you about that responsibility. They'll tell you that the savings you expected from Kubernetes has been overwhelmed by sunk engineering time troubleshooting, fixing, and maintaining your k8s cluster. If you're looking for a solution that takes you back to simple, functional infrastructure, we're experts in suc