Air-gapped clusters

TechPreview

Aside from proxy, Mirantis supports deployment of air-gapped clusters that are useful in financial and other security-concerned areas. Such clusters exist in isolated environments that have no Internet connection, neither direct nor proxied. Such an isolated environment provides all required network services, such as NTP, DNS, file resources, image registries, and so on.

MOSK air-gapping solution allows you to create an offline copy of files and images required to deploy and upgrade a cluster. You can use this offline copy to create a private content delivery network (CDN) similar to the Mirantis public CDN. If required, you can also migrate an existing non-airgapped cluster to an air-gapped one.

The following diagram illustrates air gap implementation in MOSK:

The following sections contain deployment and update details for air-gapped clusters.

• Directory and URL structure
• Limitations on Logging, Monitoring, and Alerting
• Requirements for air-gapped clusters
  • Public area
  • Private area
  • Demo CDN storage size
• Configure and deploy an air-gapped cluster
  • Prepare an offline copy for an air-gapped cluster
    • Set up airgapped-tools
    • Estimate storage size
    • Fetch the release_files tarball and sync data
  • Create a local mirror
    • Prepare a demo CDN
    • Transfer artifacts from the demo CDN to private CDN
  • Deploy an air-gapped management cluster
  • Monitor the airgapped tool status in JSON format
• Update a cluster in an air-gapped environment
  • Update an air-gapped cluster
  • Update a non-airgapped cluster in an air-gapped environment