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.29.0

The Mirantis Container Cloud major release 2.29.0:

• Introduces support for the Cluster release 17.4.0 that is based on the Cluster release 16.4.0 and represents MOSK 25.1.

• Introduces support for the Cluster release 16.4.0 that is based on Mirantis Container Runtime (MCR) 25.0.8 and Mirantis Kubernetes Engine (MKE) 3.7.19 with Kubernetes 1.27.

• Does not support greenfield deployments on deprecated Cluster releases of the 17.3.x and 16.3.x series. 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.29.0.

• Enhancements
  • BareMetalHostInventory instead of BareMetalHost
  • Validation of the Subnet object changes against allocated IP addresses
  • Improvements in calculation of update estimates using ClusterUpdatePlan
  • Switch of the default container runtime from Docker to containerd
• Addressed issues
• Known issues
  • Bare metal
    • [50287] BareMetalHost with a Redfish BMC address is stuck on registering phase
    • [42386] A load balancer service does not obtain the external IP address
    • [24005] Deletion of a node with ironic Pod is stuck in the Terminating state
  • Ceph
    • [50637] Ceph creates second miracephnodedisable object during node disabling
    • [50566] Ceph upgrade is very slow during patch or major cluster update
    • [26441] Cluster update fails with the MountDevice failed for volume warning
  • LCM
    • [50561] The local-volume-provisioner pod switches to CrashLoopBackOff
    • [50768] Failure to update the MCCUpgrade object
    • [31186,34132] Pods get stuck during MariaDB operations
  • StackLight
    • [51145] PrometheusTargetScrapesDuplicate firing on a management cluster
    • [43474] Custom Grafana dashboards are corrupted
  • Container Cloud web UI
    • [50181] Failure to deploy a compact cluster
    • [50168] Inability to use a new project right after creation
    • [50140] The Ceph Clusters tab does not display Ceph cluster details
• Components versions
• Artifacts
  • Bare metal artifacts
  • Core artifacts
  • IAM artifacts
• Security notes
• Update notes
  • Pre-update actions
    • Update managed clusters to Ubuntu 22.04
    • Back up custom Grafana dashboards on managed clusters
    • Ensure that local-volume-provisioner is healthy
  • Post-update actions
    • Start using BareMetalHostInventory instead of BareMetalHost
    • Update passwords for custom Linux accounts
    • Migrate container runtime from Docker to containerd

See also

• Cluster releases

• Releases summary

• Deprecation Notes

• Patch releases