Requirements for an AWS-based cluster¶
While planning the deployment of an AWS-based Mirantis Container Cloud cluster with Mirantis Kubernetes Engine, consider the requirements described below.
For system requirements for a bootstrap node, see Requirements for a bootstrap node.
Warning
Some of the AWS features required for Container Cloud may not be included into your AWS account quota. Therefore, carefully consider the AWS fees applied to your account that may increase for the Container Cloud infrastructure.
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 required for the Container Cloud content delivery network and alerting:
IP ranges:
Microsoft Azure (only IPs for
MicrosoftContainerRegistry
)Amazon AWS (only IPs for
"service": "CLOUDFRONT"
)
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 and login.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.
Note
If you want to deploy a managed cluster that is based on Equinix Metal on top of an AWS-based management cluster, see Requirements for an Equinix Metal based cluster.
Note
The requirements in this section apply to the latest supported Container Cloud release.
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 |
|
Storage in GB per node |
120 |
120 |
|
Operating system |
Ubuntu 20.04 |
Ubuntu 20.04 |
For a management and managed cluster, a base Ubuntu 20.04 image is required. |
MCR |
20.10.13 |
20.10.13 |
Mirantis Container Runtime (MCR) is deployed by Container Cloud as a Container Runtime Interface (CRI) instead of Docker Engine. |
Instance type |
|
|
To prevent issues with low RAM, Mirantis recommends the following types of instances for a managed cluster with 50-200 nodes:
The Warning Do not stop the AWS instances dedicated to the Container Cloud clusters to prevent data failure and cluster disaster. |
Bastion host instance type |
|
|
The Bastion instance is created with a public Elastic IP address to allow SSH access to instances. |
# of volumes |
7 (total 110 GB) |
5 (total 60 GB) |
|
# of Elastic load balancers to be used |
10 |
6 |
|
# of Elastic IP addresses to be used |
1 |
1 |