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

We are bringing MCC documentation into the MOSK documentation set so you can find everything in one place. The current MCC documentation portal will be retired soon, so we encourage you to update your bookmarks and workflows for continued easy access to the latest content.

2.12.0

The Mirantis Container Cloud GA release 2.12.0:

• Introduces support for the Cluster release 7.2.0 that is based on Mirantis Container Runtime 20.10.6 and Mirantis Kubernetes Engine 3.4.5 with Kubernetes 1.20.

• Introduces support for the Cluster release 5.19.0 that is based on Mirantis Kubernetes Engine 3.3.12 with Kubernetes 1.18 and Mirantis Container Runtime 20.10.6.

• Introduces support for the Cluster release 6.19.0 that is based on the Cluster release 5.19.0 and represents Mirantis OpenStack for Kubernetes (MOS) 21.5.

• Supports deprecated Cluster releases 5.18.0, 6.18.0, and 7.1.0 that will become unsupported in the following Container Cloud releases.

  Caution

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

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

• Enhancements
  • General availability of the Microsoft Azure cloud provider
  • Container Cloud deployment on top of MOS Victoria
  • LVM or mdadm RAID support for bare metal provisioning
  • Preparing state of a bare metal host
  • TLS for all Container Cloud endpoints
  • Migration of iam-proxy from Louketo Proxy to OAuth2 Proxy
  • Backup configuration for a MariaDB database on a management cluster
  • Renaming of the Container Cloud binary
  • Documentation enhancements
• Addressed issues
• Known issues
  • AWS
    • [8013] Managed cluster deployment requiring PVs may fail
  • Azure
    • [17705] Failure to deploy more than 62 Azure worker nodes
  • Bare metal
    • [18752] Bare metal hosts in ‘provisioned registration error’ state after update
    • [17981] Failure to redeploy a bare metal node with RAID 1
    • [17960] Overflow of the Ironic storage volume
    • [17792] Full preflight fails with a timeout waiting for BareMetalHost
  • OpenStack
    • [10424] Regional cluster cleanup fails by timeout
  • vSphere
    • [14080] Node leaves the cluster after IP address change
  • LCM
    • [16146] Stuck kubelet on the Cluster release 5.x.x series
    • [6066] Helm releases get stuck in FAILED or UNKNOWN state
  • IAM
    • [18331] Keycloak admin console menu disappears on ‘Add identity provider’ page
  • StackLight
    • [17771] Watchdog alert missing in Salesforce route
    • [19682] URLs in Salesforce alerts use HTTP for IAM with enabled TLS
  • Storage
    • [20312] Creation of ceph-based PVs gets stuck in Pending state
    • [18879] The RGW pod overrides the global CA bundle with an incorrect mount
    • [16300] ManageOsds works unpredictably on Rook 1.6.8 and Ceph 15.2.13
  • Regional cluster
    • [17359] Deletion of AWS-based regional cluster credential fails
  • Upgrade
    • [18193] Management cluster upgrade fails with Ceph cluster being not ready
    • [4288] Equinix and MOS managed clusters update failure
    • [16379,23865] Cluster update fails with the FailedMount warning
    • [9899] Helm releases get stuck in PENDING_UPGRADE during cluster update
    • [18076] StackLight update failure
  • Container Cloud web UI
    • [249] A newly created project does not display in the Container Cloud web UI
• Components versions
• Artifacts

See also

• Cluster releases (managed)

• Releases summary

• Deprecation notes