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 Container Cloud). This means everything you need is in one place. Some legacy names may remain in the code and documentation and will be updated in future releases. The separate Container Cloud documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.

2.22.0

The Mirantis Container Cloud GA release 2.22.0:

• Introduces support for the Cluster release 11.6.0 that is based on Mirantis Container Runtime 20.10.13 and Mirantis Kubernetes Engine 3.5.5 with Kubernetes 1.21.

• Supports the Cluster release 12.5.0 that is based on the Cluster release 11.5.0 and represents Mirantis OpenStack for Kubernetes (MOSK) 22.5.

• Does not support greenfield deployments on deprecated Cluster releases 11.5.0 and 8.10.0. Use the latest available Cluster releases of the series instead.

  Caution

  Make sure to update the Cluster release version of your MOSK cluster before the current Cluster release becomes unsupported by a new MOSK management release. Otherwise, MOSK management stops auto-upgrade and eventually MOSK itself becomes unsupported.

This section outlines release notes for the Container Cloud release 2.22.0.

• Enhancements
  • The ‘rebootRequired’ notification in the baremetal-based machine status
  • Custom network configuration for managed clusters based on Equinix Metal with private networking
  • Custom TLS certificates for the StackLight ‘iam-proxy’ endpoints
  • Cluster deployment and update history objects
  • Extended logging format for essential management cluster components
• Addressed issues
• Known issues
  • Bare metal
    • [24005] Deletion of a node with ironic Pod is stuck in the Terminating state
    • [20736] Region deletion failure after regional deployment failure
  • Equinix Metal with private networking
    • [29296] Deployment of a managed cluster fails during provisioning
  • vSphere
    • [29647] The ‘Network prepared’ stage of cluster deployment never succeeds
  • LCM
    • [5782] Manager machine fails to be deployed during node replacement
    • [5568] The calico-kube-controllers Pod fails to clean up resources
    • [27797] A cluster ‘kubeconfig’ stops working during MKE minor version update
  • TLS configuration
    • [29604] The ‘failed to get kubeconfig’ error during TLS configuration
  • StackLight
    • [30040] OpenSearch is not in the ‘deployed’ status during cluster update
    • [29329] Recreation of the Patroni container replica is stuck
    • [28822] Reference Application triggers alerts during its upgrade
    • [28479] Increase of the ‘metric-collector’ Pod restarts due to OOM
    • [28373] Alerta can get stuck after a failed initialization
    • [20876] StackLight pods get stuck with the ‘NodeAffinity failed’ error
  • Ceph
    • [26441] Cluster update fails with the MountDevice failed for volume warning
• Components versions
• Artifacts
• Security notes

See also

• Cluster releases

• Releases summary

• Deprecation Notes