torstai 21. heinäkuuta 2016 9.55.12 UTC+3 Amit Gupta kirjoitti: > > Just curious, why do you want at least 1000 virtual machines? I can > understand wanting to run a lot of containers, and perhaps having enough > virtual machines to guarantee anti-affinity of pods in the same replication > controller, and/or being able to have several isolation pools to keep > groups of workloads separate, e.g. for some form of multi-tenancy, or to > separate dev from prod for instance. But why the focus on high VMs? >
We're currently peaking at around 800 virtual machines in our production environment. We use already Docker, so the total Docker container count is somewhere around 3000-4000 containers (not sure, haven't counted). I emphasised the VM count because some Kubernetes compatible networking layers imposes limits (for example the Weave aws-vpc-mode depends on the RouteTable limit of max entries). I'm assuming that each additional VM causes some performance impact to either the control plane, or in a worst case to the data plane, so I want to be sure that whatever I pick will not cause a bottleneck somewhere deep in the system. -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
