Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think you're mistaken ( or i'm not understanding you correctly).

In a default setup vanilla Kubernetes, you have master nodes which host the master services ( etcd, kube-apiserver, etc. etc.), and worker nodes on the side.

With managed k8s, in most cases, the "control plane" ( what normally runs on the master nodes) is run by the cloud host, usually on shared instances ( Scaleway did a talk and it runs on dedicated Kubernetes clusters, in a namespace per client).

Indeed, then you're subject to limitations ( e.g. the kube-apiserver for you is limited to 1000 MB of RAM and if you need more because you do X, you're screwed), but that's always the case - if you run your own master nodes, they have limitations as well ( based on instance/server size), just usually higher. There's the added risk that another customer might sature an unlimited resources and impact your control plane.

In any case, I haven't hit any limitations with Scaleway's Kubernetes so far and haven't seen anyone talking about having hit one, while this isn't the first time i've heard about Digital Ocean. I don't know if it's due to size or because Scaleway have higher limits.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: