<button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">Version 1.10 (unsupported)</button>

- [Latest](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/latest/installing/hardware)
- [Version 1.16](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.16/installing/hardware)
- [Earlier versions (unsupported)](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.10/getting-support.md.txt#version-support)

<br />

Google Distributed Cloud supports a wide variety of systems running on the
hardware that the target operating system distributions support.
An Google Distributed Cloud configuration can run on minimal hardware, or on
multiple machines to provide flexibility, availability, and performance.

Regardless of your Google Distributed Cloud configuration, your nodes and clusters
must have enough CPU, RAM, and storage resources to meet the needs of clusters
and the workloads that you're running.

## Minimum and recommended CPU, RAM, and storage requirements

When you install Google Distributed Cloud, you can create different types of
clusters:

- A user cluster that runs workloads.
- An admin cluster that creates and controls user clusters to run workloads.
- A standalone cluster is a single cluster that can manage and run workloads, but a standalone cluster can't create or manage user clusters.
- A hybrid cluster can manage and run workloads, and a hybrid cluster can also create and manage additional user clusters.

In addition to cluster type, you can choose from the following installation
profiles in terms of resource requirements:

- **Default**: The default profile has standard system resource requirements,
  and you can use it for all cluster types.

- **Edge**: The edge profile has significantly reduced system resource
  requirements. Use of this profile is recommended for edge devices with limited
  resources. You can only use the edge profile for standalone clusters.

> [!WARNING]
> **Warning:** The following resource requirements don't take into account the requirements of your workloads. You must consider separately the resource requirements for your workloads to operate optimally.

### Resource requirements for all cluster types using the default profile

The following table describes the minimum and recommended hardware requirements
that Google Distributed Cloud needs to operate and manage admin, hybrid, user, and
standalone clusters using the default profile:

| Resource | Minimum | Recommended |
|---|---|---|
| **CPUs / vCPUs** | 4 core | 8 core |
| **RAM** | 16 GiB | 32 GiB |
| **Storage** | 128 GiB | 256 GiB |

### Resource requirements for standalone clusters using the edge profile

The following table describes the minimum and recommended hardware requirements
that Google Distributed Cloud needs to operate and manage standalone clusters
using the edge profile:

| Resource | Minimum | Recommended |
|---|---|---|
| **CPUs / vCPUs** | 2 core | 4 core |
| **RAM** | Ubuntu: 4 GiB CentOS/RHEL: 6 GiB | Ubuntu: 8 GiB CentOS/RHEL: 12 GiB |
| **Storage** | 128 GiB | 256 GiB |

To configure standalone clusters using the edge profile, follow these best practices:

- Run `bmctl` on a separate workstation. If you must run `bmctl` on the target
  cluster node, you need 2 GiB of memory to meet the
  minimum requirements. For example, you require 6 GiB for Ubuntu and
  8 GiB for CentOS/Redhat.

- Set `MaxPodsPerNode` to 110. The cluster runs no more than 30 user pods per
  node on average. You might need extra resources for a higher `MaxPodsPerNode`
  configuration or run more than 30 user pods per node.

- Use [`containerd` as the container runtime](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.10/installing/runtime.md.txt).
  You might need extra resources to run with the Docker container runtime.

- [Kubevirt](https://kubevirt.io) components are not
  considered in this minimum resource configuration. Kubevirt requires
  additional resources depending on the number of VMs deployed in the cluster.

## Number of machines needed

Google Distributed Cloud requires at least one machine, which serves as both
workstation and cluster node. For highly available (HA) nodes and improved
performance, we suggest a realistic minimum of five machines meeting the
recommended resource requirements.

## Additional storage requirements

Google Distributed Cloud doesn't provide any storage resources. You must provision
and configure the required storage on your system.

For detailed storage requirements, see the
[Installation prerequisites overview](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.10/installing/install-prereq.md.txt).

For more information about how to configure the storage required, see
[Configuring storage for Google Distributed Cloud](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.10/installing/storage.md.txt).

## etcd performance

The etcd documentation provides
[hardware recommendations](https://etcd.io/docs/v3.4/op-guide/hardware/)
for ensuring the best etcd performance when running your clusters in production.

To check your etcd and disk performance, use the following etcd I/O latency
metrics in the Metrics Explorer:

- `etcd_disk_backend_commit_duration_seconds`: the duration should be less than 25 milliseconds for the 99th percentile (p99).
- `etcd_disk_wal_fsync_duration_seconds`: the duration should be less than 10 milliseconds for the 99th percentile (p99).

For more information about etcd performance, see
[What does the etcd warning "apply entries took too long" mean?](https://etcd.io/docs/v3.3/faq/#what-does-the-etcd-warning-apply-entries-took-too-long-mean)
and
[What does the etcd warning "failed to send out heartbeat on time" mean?](https://etcd.io/docs/v3.3/faq/#what-does-the-etcd-warning-failed-to-send-out-heartbeat-on-time-mean).