3 ms·
Kubernetes is not supposed to be run on a single node, but on dozens or hundreds of machines. Scheduling, networking, and authorizing heterogeneous highly avail
by nielsole 9y ago
Kubernetes is not supposed to be run on a single node, but on dozens or hundreds of machines. Scheduling, networking, and authorizing heterogeneous highly available workloads by possibly different teams + managing ingress + managing networked storage is what Kubernetes is built for.
I wouldn't know how to do this with LXC
- colek42 9y agoThe API for k8s is great. We mostly run large (50 core 500GB memory) machines co-located at client sites. We have hundreds of these to manage, but they are separated geographically. K8's API/Infrastructure would be great to manage/monitor them.
- nielsole 9y agoSounds like an interesting problem. What is your use-case? Caching servers in ISPs? Kubernetes kind of assumes that any node can fail any time and reschedules workloads. This assumption might not be in line with your requirements.