Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!

Starting with MOSK 25.2, the MOSK documentation set covers all product layers, including MOSK management (formerly MCC). This means everything you need is in one place. The separate MCC documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.

Air-gapped clusters

Available since MCC 2.30.0 (21.0.0 and 20.0.0) 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:

../../_images/air-gap.png

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