Kubernetes Failure Stories

#1

Post by hjacobs » Sun, Jan 20, 2019, 4:12 PM UTC

Re: Kubernetes Failure Stories

#2

Post by hjacobs » Sun, Jan 20, 2019, 4:28 PM UTC

Christian already followed the example and created a similar list for Serverless: https://github.com/cristim/serverless-failure-stories

Re: Kubernetes Failure Stories

#3

Post by tnolet » Sun, Jan 20, 2019, 4:51 PM UTC

I'd be interested in a related "microservices failure stories". Must be a big overlap with this.

Re: Kubernetes Failure Stories

#4

Post by SlowRobotAhead » Sun, Jan 20, 2019, 5:02 PM UTC

hjacobs wrote: post #2

Christian already followed the example and created a similar list for Serverless: https://github.com/cristim/serverless-failure-stories

The third example on that list is a nice little short story. Simple mistake, gets right to the point.

I’m setting up a lambda test right now so I find it perfectly timed!

Re: Kubernetes Failure Stories

#5

Post by coredog64 » Sun, Jan 20, 2019, 5:10 PM UTC

tnolet wrote: post #3

I'd be interested in a related "microservices failure stories". Must be a big overlap with this.

Microservices failure stories? “All of them. The End”

Re: Kubernetes Failure Stories

#6

Post by tnolet » Sun, Jan 20, 2019, 5:14 PM UTC

coredog64 wrote: post #5

tnolet wrote: post #3

I'd be interested in a related "microservices failure stories". Must be a big overlap with this.

Microservices failure stories? “All of them. The End”

I'm not convinced all microservices ventures are failures. Having worked in the space a bit as a founder/CTO of a vendor in that space I've just seen many examples of misguided attempts due to fashion / CV-driven development / hype driven development. The pattern is valid, just not for everyone at every time.

Re: Kubernetes Failure Stories

#7

Post by hjacobs » Sun, Jan 20, 2019, 5:17 PM UTC

tnolet wrote: post #6

coredog64 wrote: post #5

Earlier quoted context omitted.

Microservices failure stories? “All of them. The End”

I'm not convinced all microservices ventures are failures. Having worked in the space a bit as a founder/CTO of a vendor in that space I've just seen many examples of misguided attempts due to fashion / CV-driven development / hype driven development. The pattern is valid, just not for everyone at every time.

ThoughtWorks even has a term for it: "Microservice envy" https://www.thoughtworks.com/radar/techniques/microservice-e...

Re: Kubernetes Failure Stories

#8

Post by awinter-py » Sun, Jan 20, 2019, 5:19 PM UTC

Beyond strictly runtime failures, 2018 feels like the year that most of my friends tried kube but not everybody stayed on.

The adoption failures are mostly networking issues specific to their cloud. Performance and box limits vary widely depending on cloud vendor and I still don't quite understand the performance penalty of the different overlay networks / adapters.

Re: Kubernetes Failure Stories

#9

Post by williesleg » Sun, Jan 20, 2019, 5:31 PM UTC

Docker is pretty stable, Kubernetes is a fail pail put out by Google. So we can't catch up.

Re: Kubernetes Failure Stories

#10

Post by dehrmann » Sun, Jan 20, 2019, 5:32 PM UTC

tnolet wrote: post #3

I'd be interested in a related "microservices failure stories". Must be a big overlap with this.

I have two. One was caused by data inconsistency between services and regions. One is more hypothetical: the microservices had gotten to the point that no one knew how to start the system if all services are down, and it's possible that services have circular dependencies to the point that it would be incredibly hard to do a cold start.