Version 1.16. This version is no longer supported. For information about how to upgrade to version 1.28, see Upgrade clusters in the latest documentation. For more information about supported and unsupported versions, see the Versioning page in the latest documentation.
This page provides basic scaling information for VMs running on
Google Distributed Cloud. The information provided doesn't indicate hard limits
or guaranteed thresholds for the product or your installation. The information
is intended to help you determine whether VM Runtime on GDC can meet
your computing requirements.
For information about quotas, limits, and scaling for Google Distributed Cloud,
see Quotas and limits.
Maximum VM scaling
We have determined through extensive testing that you can run reliably as many
as 500 VMs concurrently on a Google Distributed Cloud cluster with 50 nodes.
Resource usage
To scale up VM deployments, make sure there are enough CPU, memory, and storage
resources in the cluster for both VMs and the control plane components. For
standard resource requirements for cluster node machines, see
Cluster node machine prerequisites.
Note the following VM Runtime on GDC resource usage for our maximum VM
scaling configuration:
Total CPU share used by all the components in the vm-system namespace is
approximately 1.3 at the peak usage.
Total memory consumed by all the components in the vm-system namespace is
approximately 10 GiB.
Known resource issue
Currently, when the guest agent is enabled,
each VM registers a separate watcher to the API server. Therefore, the number of registered watchers in kube-apiserver increases linearly with the number of the VMs. Depending on the workloads you run, you may
encounter issues related to kube-apiserver as the number of VMs increases. If
you're affected by this issue, you can configure the kube-apiserver or
disable the guest agent if
you aren't using it.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-05 UTC."],[[["This document provides guidance on VM scaling for Google Distributed Cloud, but does not represent hard limits or guarantees."],["Testing has shown that a Google Distributed Cloud cluster with 50 nodes can reliably run up to 500 VMs concurrently."],["Scaling VM deployments requires ensuring sufficient CPU, memory, and storage resources within the cluster for both VMs and control plane components."],["The `vm-system` namespace components consume approximately 1.3 CPU share and 10 GiB of memory at peak usage in the maximum VM scaling configuration."],["Enabling the guest agent can increase the number of watchers registered to `kube-apiserver`, which may lead to issues as the number of VMs increases, with options to adjust `kube-apiserver` or disable the agent."]]],[]]
