Requirements for an Azure-based cluster

While planning the deployment of an Azure-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 Azure features required for Container Cloud may not be included into your Azure account quota. Therefore, carefully consider the Azure 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:

  • 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 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

The requirements in this section apply to the latest supported Container Cloud release.

Requirements for an Azure-based Container Cloud cluster

Resource

Management or regional cluster

Managed cluster

Comment

# of nodes

3 (HA)

5 (6 with StackLight HA)

  • A management cluster requires 3 nodes for the manager nodes HA. Adding more than 3 nodes to a management or regional cluster is not supported.

  • A managed cluster requires 3 manager nodes for HA and 2 worker nodes for the Container Cloud workloads. If the multiserver mode is enabled for StackLight, 3 worker nodes are required for workloads.

# of vCPUs per node

8

8

RAM in GB per node

24

16

Storage in GB per node

128

128

Operating system

Ubuntu 20.04

Ubuntu 20.04

For a management, regional 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.

Virtual Machine size

Standard_F16s_v2

Standard_F8s_v2

To prevent issues with low RAM, Mirantis recommends selecting Azure virtual machine sizes that meet the following minimum requirements for managed clusters:

  • 16 GB RAM (24 GB RAM for a cluster with 50-200 nodes)

  • 8 CPUs

  • Ephemeral OS drive supported

  • OS drive size is more than 128 GB

# of Azure resource groups

1

1

# of Azure networks

1

1

# of Azure subnets

1

1

# of Azure security groups

1

1

# of Azure network interfaces

3

One network interface per each machine

# of Azure route tables

1

1

# of Azure load balancers to be used

2

2

1 load balancer for an API server and 1 for Kubernetes services

# of public IP addresses to be used

12/9

8

  • Management cluster: 10 public IPs for Kubernetes services and 2 public IPs as front-end IPs for load balancers

  • Regional cluster: 7 public IPs for Kubernetes services and 2 public IPs as front-end IPs for load balancers

  • Managed cluster: 6 public IPs for Kubernetes services and 2 public IPs as front-end IPs for load balancers

# of OS disks

3

1 OS disk per each machine

# of data disks

0

5 (total 60 GB)

A managed cluster requires 5 volumes for StackLight