5 ms·
The original k8s paper mentioned that the only use case was a low latency and a high latency workflow combination and the resource allocation is based on that.
by datadeft 2y ago
The original k8s paper mentioned that the only use case was a low latency and a high latency workflow combination and the resource allocation is based on that. The generic idea is that you can easily move low latency work between nodes and there are no serios repercussions when a high latency job fails.
Based on this information, it is hard to justify to even consider k8s for the problem that gitpod has.
- junkaccount 2y agoThanks for reading the paper!
- datadeft 2y agoFor those who are interested: https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/43438.pdf https://static.googleusercontent.com/media/research.google.c... I am not sure what differences k8s has compare to Borg. At the concept level these are pretty comparable.