4 ms·
I disagree with that. Many fortune 500s are running k8s to power critical infra. GMF processes all OnStar data in realtime on k8s, GitHub runs entirely on k8s,
by grepfru_it 4y ago
I disagree with that. Many fortune 500s are running k8s to power critical infra. GMF processes all OnStar data in realtime on k8s, GitHub runs entirely on k8s, etc etc. You need the personal and the tools to manage it, but at a certain point k8s makes sense. There are still use cases were k8s is not a solution.
EDIT: part of actions, codespaces and packages are not run on k8s, but 80% of github services are
- goodpoint 4y ago> GitHub runs entirely on k8s That's really not the endorsement you think it is.
- grepfru_it 4y agoYour comment doesn't really help understand why.
- remram 4y agoGitHub experiences outages pretty regularly, for example on 12 separate days last month: https://www.githubstatus.com/history https://www.githubstatus.com/history
- joshribakoff 4y agoSo what? Nothing here is sufficient to conclude it has anything to do with k8 whatsoever. For example “users cannot resume code spaces created before the incident” sounds a lot more like an application level problem.
- remram 4y agoThe point above was that it wasn't a good endorsement. Correlation is not causation but the opposite is also true.