Requirements for a baremetal-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 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")

  • Salesforce

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

Caution

Regional clusters are unsupported since Container Cloud 2.25.0. Mirantis does not perform functional integration testing of the feature and intends to remove the related code in Container Cloud 2.26.0. If you still require this feature, contact Mirantis support for further information.

• Reference hardware configuration
• System requirements for the seed node
• Network fabric
• DHCP range requirements for PXE
• Management cluster storage