3 ms·
Each vm belongs to a single cluster. The best way to maximimize resource utilization is to size the vms according to the tenant load, generally you want to
by zaat 7y ago
Each vm belongs to a single cluster.
The best way to maximimize resource utilization is to size the vms according to the tenant load, generally you want to minimize the number of vms, as each of them add some overhead, but you don't want to waste unnecessary resources. You must have a minimum set of vms in each cluster to ensure high availability.
Automating the provisioning of an entire new cluster is very easy, at least for some people with the required resources. But even for a small shop it is possible to automate it using stuff like Jenkins and Ansible. It is still relatively sophisticated stuff. It is not rocket science but not an elementary school project level either.
- polskibus 7y agoThanks, that was informative. Do you have a reference that you'd recommend about the details of how the big names that you've mentioned are doing multitenant Kubernetes? I'd love to read more about it.
- zaat 7y agoOh, sorry, that was tongue in the cheek. They are cloud providers, and as such they provide costumers with separate cluster. The aks-engine repo let you peep to what goes behind the scenes, but this is not the kind of beast you will grow at home - it is a public cloud provider with global scale, with the expected level of complexity and engineering. It is available on: https://github.com/Azure/aks-engine https://github.com/Azure/aks-engine
- merb 7y agobtw. in hard multitenant k8s you can even go as wide as using a "master" cluster that contains the control plane of another cluster. actually you need the right network cni for that.