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

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

Kubernetes underlay

The Kubernetes lifecycle management (LCM) engine in MOSK consists of the following components:

LCM Controller

Responsible for all LCM operations. Consumes the LCMCluster object and orchestrates actions through LCM Agent.

LCM Agent

Runs on the target host. Executes Ansible playbooks in headless mode.

Helm Controller

Responsible for the Helm charts life cycle, is installed by the provider as a Helm v3 chart.

The Kubernetes LCM components handle the following custom resources:

• LCMCluster

• LCMMachine

• HelmBundle

The following diagram illustrates handling of the LCM custom resources by the Kubernetes LCM components. On a MOSK cluster, apiserver handles multiple Kubernetes objects, for example, deployments, nodes, RBAC, and so on.

The following sections outline key components of the Kubernetes LCM engine in MOSK.

• LCM custom resources
• LCM Controller
• LCM Agent
• Helm Controller
• MKE API limitations
• MKE configuration management
  • MKE configuration managed by MOSK
    • [audit_log_configuration]
    • [auth]
    • [auth.external_identity_provider]
    • [hardening_configuration]
    • [scheduling_configuration]
    • [tracking_configuration]
    • [cluster_config]
  • MKE configuration managed directly by the MKE API