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

Switch to latest✕

2.5.0

The Mirantis Container Cloud GA release 2.5.0:

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

• Introduces support for the Cluster release 6.12.0 that is based on the Cluster release 5.12.0 and supports Mirantis OpenStack for Kubernetes (MOS) 21.1.

• Still supports previous Cluster releases 5.11.0 and 6.10.0 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.5.0.

• Enhancements
  • Updated version of Mirantis Kubernetes Engine
  • Proxy support for OpenStack and VMware vSphere providers
  • Artifacts caching
  • NTP server configuration on regional clusters
  • Optimized ClusterRelease upgrade process
  • Dedicated network for external connection to the Kubernetes services
• Addressed issues
• Known issues
  • AWS
    • [8013] Managed cluster deployment requiring PVs may fail
  • vSphere
    • [11633] A vSphere-based project cannot be cleaned up
  • Bare metal
    • [7655] Wrong status for an incorrectly configured L2 template
    • [9875] Full preflight fails with a timeout waiting for BareMetalHost
    • [11468] Pods using LVP PV are not mounted to LVP disk
  • Storage
    • [10060] Ceph OSD node removal fails
    • [7073] Cannot automatically remove a Ceph node
    • [10050] Ceph OSD pod is in the CrashLoopBackOff state after disk replacement
  • IAM
    • [10829] Keycloak pods fail to start during a management cluster bootstrap
  • 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 and regional clusters
    • [9899] Helm releases get stuck in PENDING_UPGRADE during cluster update
    • [10424] Regional cluster cleanup fails by timeout
  • 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

• Releases summary