Requirements for an Equinix Metal based cluster¶
While planning the deployment of a Mirantis Container Cloud cluster with MKE that is based on the Equinix Metal cloud provider, consider the requirements described below.
Mirantis supports deploying of clusters on Equinix Metal in two modes: with public or private networks. The deployment mode for management and managed clusters must be the same. For details on the private networks mode, see Equinix Metal with private networking.
For system requirements for a bootstrap node, see Requirements for a bootstrap node.
Note
For the Equinix Metal cloud provider with private networks, a bootstrap node must be attached to the VLAN that will be used to deploy a management cluster.
If you want to deploy an Equinix Metal based managed cluster with public networks on top of an AWS management cluster, also refer to requirements for an Requirements for an AWS-based cluster.
If you use a firewall or proxy, make sure that the bootstrap, management, and regional clusters have access to the following IP ranges and domain names:
IP ranges:
Domain names:
mirror.mirantis.com and repos.mirantis.com for packages
binary.mirantis.com for binaries and Helm charts
mirantis.azurecr.io and *.blob.core.windows.net for Docker images
mcc-metrics-prod-ns.servicebus.windows.net:9093 for Telemetry (port 443 if proxy is enabled)
mirantis.my.salesforce.com for Salesforce alerts
Note
Access to Salesforce is required from any Container Cloud cluster type.
If any additional Alertmanager notification receiver is enabled, for example, Slack, its endpoint must also be accessible from the cluster.
Resource |
Management or regional cluster |
Managed cluster |
Comment |
||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
# of nodes |
3 (HA) |
5 (6 with StackLight HA) |
|
||||||||
# of vCPUs per node |
8 |
8 |
|||||||||
RAM in GB per node |
24 |
16 |
|||||||||
Operating system |
Ubuntu 20.04 |
Ubuntu 20.04 |
|||||||||
MCR |
20.10.8 |
20.10.8 |
Mirantis Container Runtime (MCR) is deployed by Container Cloud as a Container Runtime Interface (CRI) instead of Docker Engine. |
||||||||
Server type |
c3.small.x86 |
c3.small.x86 |
Most available Equinix Metal servers are configured with minimal requirements to deploy Container Cloud clusters. However, ensure that the selected Equinix Metal server type meets the following minimal requirements for a managed cluster:
Warning If the Equinix Metal data center has not enough capacity, the server provisioning request will fail. Servers of particular types can be unavailable at a given time. Therefore, before you deploy a cluster, verify that the selected server type is available as described in Verify the capacity of the Equinix Metal facility. For more details about the Equinix Metal capacity, see official Equinix Metal Documentation. |
||||||||
# of Elastic IP addresses to be used |
12 |
6 |
|
||||||||
# of IP addresses for a cluster with private networks |
12 |
5 |
|
||||||||
# VLANs for a cluster with private networks |
1 |
1 |
Each cluster deployed on Equinix Metal with private networks requires 1 separate VLAN. |
||||||||
Ceph nodes |
- |
See comments |
Recommended minimal number of Ceph node roles:
If you select Manual Ceph Configuration during the cluster creation, you can manually configure Ceph roles for each machine in the cluster following the recommended minimal number of Ceph node roles. Otherwise, Equinix Metal cloud provider will automatically configure Ceph roles: all control plane machines will be configured with Storage and Manager and Monitor roles. All worker machines will be configured with Storage role. |