Newer documentation is now live.You are currently reading an older version.

Switch to latest✕

2.3.0

The Mirantis Container Cloud GA release 2.3.0:

• Introduces support for the Cluster release 5.10.0 that is based on Kubernetes 1.18 and the updated versions of Mirantis Kubernetes Engine 3.3.4 and Mirantis Container Runtime 19.03.13.

• Introduces support for the Cluster release 6.10.0 that is based on the Cluster release 5.10.0 and supports Mirantis OpenStack for Kubernetes (MOSK) Ussuri.

• Still supports previous Cluster releases 5.9.0 and 6.8.1 that are now deprecated and will become unsupported in one of the following Container Cloud releases.

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

• Enhancements
  • Updated versions of Mirantis Kubernetes Engine and Container Runtime
  • Additional regional cluster on VMware vSphere
  • Automated setup of a VM template for the VMware vSphere provider
  • StackLight support for VMware vSphere
  • Support of multiple host-specific L2 templates per a bare metal cluster
  • Improvements in the Container Cloud logs collection
• Known issues
  • AWS
    • [8013] Managed cluster deployment requiring PVs may fail
  • Bare metal
    • [6988] LVM fails to deploy if the volume group name already exists
    • [7655] Wrong status for an incorrectly configured L2 template
    • [8560] Manual deletion of BareMetalHost leads to its silent removal
    • [9875] Full preflight fails with a timeout waiting for BareMetalHost
  • IAM
    • [2757] IAM fails to start during management cluster deployment
  • LCM
    • [10029] Authentication fails with the 401 Unauthorized error
  • Management cluster update
    • [9899] Helm releases get stuck in PENDING_UPGRADE during cluster update
  • Storage
    • [10060] Ceph OSD node removal fails
    • [9928] Ceph rebalance during a managed cluster update
    • [7073] Cannot automatically remove a Ceph node
    • [10050] Ceph OSD pod is in the CrashLoopBackOff state after disk replacement
  • Container Cloud web UI
    • [249] A newly created project does not display in the Container Cloud web UI
• Addressed issues
• Components versions
• Artifacts

See also

• Cluster releases

• Releases summary