News for hackers. Stuff that matters.

A comment on Will Kubernetes Collapse Under the Weight of Its Complexity?.

Re:Will Kubernetes Collapse Under the Weight of Its Complexity? by mwcampbell on Monday May 28, 2018 @09:28PM (#17175786)
> available 99.5% of the time with decent alerting for operators to kick it

An operator should never have to "kick" a service. It should repair itself, except for the occasional hardware replacement if one is working with bare metal. And for anything that's being sold as a product, as opposed to an internal tool, I think 99.9% availability should be the minimum.

But I don't know enough about Kubernetes to say whether it's overkill at the scale of just a few servers.

[ Parent | on HN ]
Re:Will Kubernetes Collapse Under the Weight of Its Complexity? by smudgymcscmudge on Monday May 28, 2018 @10:39PM (#17176075)
> An operator should never have to "kick" a service.

Have you ever been a sysadmin? There are very few services that don’t need a kick every now and then.

[ Parent | on HN ]
Re:Will Kubernetes Collapse Under the Weight of Its Complexity? by mwcampbell on Monday May 28, 2018 @10:43PM (#17176092)
Yes I have. And if a service ever needs a manual kick, I consider that a bug. At least when running in a public cloud.
[ Parent | on HN ]
Re:Will Kubernetes Collapse Under the Weight of Its Complexity? by randallsquared on Monday May 28, 2018 @10:48PM (#17176115)
Sure, sure, but... everything is buggy, by that metric. I think that's what the parent comment was getting at.
[ Parent | on HN ]
Re:Will Kubernetes Collapse Under the Weight of Its Complexity? by 49bc on Monday May 28, 2018 @10:12PM (#17175965)
How many “kicks” does it take to build a reasonably resilient distributed service? A lot!
[ Parent | on HN ]
Re:Will Kubernetes Collapse Under the Weight of Its Complexity? by wang_li on Monday May 28, 2018 @11:47PM (#17176320)
CAP theorem says it's impossible.
[ Parent | on HN ]
Re:Will Kubernetes Collapse Under the Weight of Its Complexity? by Xorlev on Tuesday May 29, 2018 @12:00AM (#17176384)
That isn't what the CAP theorem says at all. It says you need to pick your guarantees.

Additionally, resilience is in the eye of the beholder: might mean AP for a service that needs to be up at the cost of consistency or CP for a service that detects when it can't achieve quorum and fail gratefully.

[ Parent | on HN ]