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.

Directory and URL structure

The URL structure in the air gap implementation contains three types of file CDN resources and one image CDN resource. The private file CDN resources emulate the following public resources:

The private image CDN resource emulates the mirantis.azurecr.io Docker registry.

Each of these private file CDN resources contains a limited copy of files that is necessary to deploy a specific ClusterRelease version. Any file on any private CDN resource exists on the same path as on the corresponding public CDN resource. For example, the LCM Agent binary 1.42.6 on the public CDN is located on the https://binary.mirantis.com/core/bin/lcm-agent-1.42.6 binary resource. When copied to the private CDN, its new URL becomes <Private Binary Files CDN>/core/bin/lcm-agent-1.42.6.

The same principle applies to images: only images required for a specific ClusterRelease are copied from the CDN with public images. On the private CDN, images are available under the same <image name>:<tag>. The only thing that differs is the registry base URL. For example, image mirantis.azurecr.io/general/external/pause:3.1 becomes <Private Images CDN>/general/external/pause:3.1.