2.4.0

The Mirantis Container Cloud GA release 2.4.0:

• Introduces support for the Cluster release 5.11.0 that is based on Kubernetes 1.18, Mirantis Kubernetes Engine 3.3.4, and the updated version of Mirantis Container Runtime 19.03.14.

• Supports 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.10.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 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.4.0.

• Enhancements
  • Support for the updated version of Mirantis Container Runtime
  • Dedicated network for Kubernetes pods traffic on bare metal clusters
  • Feedback form improvement in Container Cloud web UI
• Known issues
  • AWS
    • [8013] Managed cluster deployment requiring PVs may fail
  • Bare metal
    • [9875] Full preflight fails with a timeout waiting for BareMetalHost
    • [11102] Keepalived does not detect the loss of VIP deleted by netplan
    • [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
  • 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
  • LCM
    • [10029] Authentication fails with the 401 Unauthorized error
    • [6066] Helm releases get stuck in FAILED or UNKNOWN state
  • StackLight
    • [11001] Patroni pod fails to start
  • Management cluster update
    • [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
• Addressed issues
• Components versions
• Artifacts

See also

• Cluster releases (managed)

• Releases summary