2.7.0

The Mirantis Container Cloud GA release 2.7.0:

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

• Supports the Cluster release 6.14.0 that is based on the Cluster release 5.14.0 and represents Mirantis OpenStack for Kubernetes (MOS) 21.2.

• Supports deprecated Cluster releases 5.13.0 and 6.12.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.7.0.

• Enhancements
  • Full support for the VMware vSphere provider
  • Universal SSH user
  • Configuration of SSH keys on existing clusters using web UI
  • Cluster and machines live statuses in web UI
  • Enabling of proxy access using web UI for vSphere, AWS, and bare metal
  • QuickStart guides
• Addressed issues
• Known issues
  • AWS
    • [8013] Managed cluster deployment requiring PVs may fail
  • vSphere
    • [14458] Failure to create a container for pod: cannot allocate memory
  • OpenStack
    • [10424] Regional cluster cleanup fails by timeout
  • Bare metal
    • [7655] Wrong status for an incorrectly configured L2 template
  • Storage
    • [7073] Cannot automatically remove a Ceph node
    • [10050] Ceph OSD pod is in the CrashLoopBackOff state after disk replacement
    • [12723] ceph_role_* labels remain after deleting a node from KaaSCephCluster
  • IAM
    • [13385] MariaDB pods fail to start after SST sync
  • LCM
    • [13845] Cluster update fails during the LCM Agent upgrade with x509 error
    • [13381] Management and regional clusters with enabled proxy are unreachable
    • [13402] Cluster fails with error: no space left on device
    • [8112] Nodes occasionally become Not Ready on long-running clusters
    • [10029] Authentication fails with the 401 Unauthorized error
    • [6066] Helm releases get stuck in FAILED or UNKNOWN state
  • Upgrade
    • [13292] Local volume provisioner pod stuck in Terminating status after upgrade
    • [9899] Helm releases get stuck in PENDING_UPGRADE during cluster update
  • 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