2.9.0

The Mirantis Container Cloud GA release 2.9.0:

• Introduces support for the Cluster release 5.16.0 that is based on Kubernetes 1.18, Mirantis Container Runtime 19.03.14, and Mirantis Kubernetes Engine 3.3.6.

• Introduces support for 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.15.0 and 6.14.0 that will become unsupported in one of 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.

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

• Enhancements
  • Container Cloud clusters based on Equinix Metal
  • Integration of Container Cloud to Lens
  • New bootstrap node for additional regional clusters
  • TLS certificates for management cluster applications
  • Default Keycloak authorization in Container Cloud web UI
  • SSH keys management for mcc-user
  • VMware vSphere resources controller
  • New format of L2 templates
• Addressed issues
• Known issues
  • AWS
    • [8013] Managed cluster deployment requiring PVs may fail
  • vSphere
    • [15698] VIP is assigned to each manager node instead of a single node
    • [14080] Node leaves the cluster after IP address change
    • [14458] Failure to create a container for pod: cannot allocate memory
  • OpenStack
    • [10424] Regional cluster cleanup fails by timeout
  • Equinix Metal
    • [14981] Equinix Metal machine is stuck in Deploy stage
  • Bare metal
    • [14642] Ironic logs overflow the storage volume
    • [7655] Wrong status for an incorrectly configured L2 template
  • Storage
    • [10050] Ceph OSD pod is in the CrashLoopBackOff state after disk replacement
  • IAM
    • [13385] MariaDB pods fail to start after SST sync
  • LCM
    • [13402] Cluster fails with error: no space left on device
    • [8367] Adding of a new manager node to a managed cluster hangs on Deploy stage
    • [13303] Managed cluster update fails with the Network is unreachable error
    • [13845] Cluster update fails during the LCM Agent upgrade with x509 error
    • [6066] Helm releases get stuck in FAILED or UNKNOWN state
    • [14125] Inaccurate nodes readiness status on a managed cluster
  • Upgrade
    • [15419] The iam-api pods are not ready after cluster upgrade
    • [9899] Helm releases get stuck in PENDING_UPGRADE during cluster update
    • [14152] Managed cluster upgrade fails due to DNS issues
  • Container Cloud web UI
    • [249] A newly created project does not display in the Container Cloud web UI
• Components versions
• Artifacts
• Switch L2 templates to the new format

See also

• Cluster releases (managed)

• Releases summary