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

The Mirantis Container Cloud GA release 2.11.0:

• Introduces support for the Cluster release 7.1.0 that is based on Mirantis Container Runtime 20.10.5 and Mirantis Kubernetes Engine 3.4.0 with Kubernetes 1.20.

• Introduces support for the Cluster release 5.18.0 that is based on Mirantis Kubernetes Engine 3.3.6 with Kubernetes 1.18 and Mirantis Container Runtime 20.10.5.

• Introduces support for the Cluster release 6.18.0 that is based on the Cluster release 5.18.0 and represents Mirantis OpenStack for Kubernetes (MOS) 21.4.

• Continues supporting the Cluster release 6.16.0 that is based on the Cluster release 5.16.0 and represents Mirantis OpenStack for Kubernetes (MOS) 21.3.

• Supports deprecated Cluster releases 5.17.0, 6.16.0, and 7.0.0 that will become unsupported in the following Container Cloud releases.

• Supports the Cluster release 5.11.0 only for attachment of existing MKE 3.3.4 clusters. For the deployment of new or attachment of existing MKE 3.3.6 clusters, the latest available Cluster release is used.

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.

Caution

Before upgrading an existing managed cluster with StackLight deployed in HA mode to the latest Cluster release, add the StackLight node label to at least 3 worker machines as described in Upgrade managed clusters with StackLight deployed in HA mode. Otherwise, the cluster upgrade will fail.

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

• Enhancements
  • Support for the Microsoft Azure cloud provider
  • RHEL 7.9 bootstrap node for the vSphere-based provider
  • Validation labels for the vSphere-based VM templates
  • Automatic migration of Docker data and LVP volumes to NVMe on AWS clusters
  • Switch of core Helm releases from v2 to v3
  • Bond interfaces for baremetal-based management clusters
  • Bare metal advanced configuration using web UI
  • Equinix Metal capacity labels for machines in web UI
  • Documentation enhancements
• Addressed issues
• Known issues
  • AWS
    • [8013] Managed cluster deployment requiring PVs may fail
  • Equinix Metal
    • [16718] Equinix Metal provider fails to create machines with SSH keys error
  • Bare metal
    • [17118] Failure to add a new machine to cluster
  • OpenStack
    • [16959] Proxy-based regional cluster creation fails
    • [10424] Regional cluster cleanup fails by timeout
  • vSphere
    • [14458] Failure to create a container for pod: cannot allocate memory
    • [14080] Node leaves the cluster after IP address change
  • LCM
    • [16146] Stuck kubelet on the Cluster release 5.x.x series
    • [8367] Adding of a new manager node to a managed cluster hangs on Deploy stage
    • [6066] Helm releases get stuck in FAILED or UNKNOWN state
  • IAM
    • [13385] MariaDB pods fail to start after SST sync
    • [18331] Keycloak admin console menu disappears on ‘Add identity provider’ page
  • StackLight
    • [16843] Inability to override default route matchers for Salesforce notifier
    • [17771] Watchdog alert missing in Salesforce route
  • Storage
    • [16300] ManageOsds works unpredictably on Rook 1.6.8 and Ceph 15.2.13
  • Bootstrap
    • [16873] Bootstrap fails with ‘failed to establish connection with tiller’ error
  • Upgrade
    • [17477] StackLight in HA mode is not deployed or cluster update is blocked
    • [17412] Cluster upgrade fails on the KaaSCephCluster CRD update
    • [17069] Cluster upgrade fails with the ‘Failed to configure Ceph cluster’ error
    • [17007] False-positive ‘release: “squid-proxy” not found’ error
    • [16964] Management cluster upgrade gets stuck
    • [16777] Cluster update fails due to Patroni being not ready
    • [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
• Upgrade managed clusters with StackLight deployed in HA mode

See also

• Cluster releases (managed)

• Releases summary