2.10.0

The Mirantis Container Cloud GA release 2.10.0:

• Introduces support for the Cluster release 7.0.0 that is based on the updated versions of Mirantis Container Runtime 20.10.5, and Mirantis Kubernetes Engine 3.4.0 with Kubernetes 1.20.

• Introduces support for the Cluster release 5.17.0 that is based on Mirantis Kubernetes Engine 3.3.6 with Kubernetes 1.18 and the updated version of Mirantis Container Runtime 20.10.5.

• Continues supporting 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.16.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.10.0.

• Enhancements
  • 7.x Cluster release series with updated versions of MCR, MKE, and Kubernetes
  • Support of MKE 3.3.x series and 3.4.0 for cluster attachment
  • Initial CentOS support for the VMware vSphere provider
  • RHEL 7.9 support for the VMware vSphere provider
  • Guided tour in the Container Cloud web UI
  • Removal of IAM and Keycloak IPs configuration for the vSphere provider
  • Command for creation of Keycloak users
  • Documentation enhancements for IAM
• Addressed issues
• Known issues
  • AWS
    • [8013] Managed cluster deployment requiring PVs may fail
  • Equinix Metal
    • [16718] Equinix Metal provider fails to create machines with SSH keys error
  • Bare metal
    • [17118] Failure to add a new machine to cluster
    • [7655] Wrong status for an incorrectly configured L2 template
  • OpenStack
    • [10424] Regional cluster cleanup fails by timeout
  • vSphere
    • [15698] VIP is assigned to each manager node instead of a single node
    • [14458] Failure to create a container for pod: cannot allocate memory
    • [14080] Node leaves the cluster after IP address change
  • LCM
    • [16146] Stuck kubelet on the Cluster release 5.x.x series
    • [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
  • IAM
    • [13385] MariaDB pods fail to start after SST sync
  • StackLight
    • [16843] Inability to override default route matchers for Salesforce notifier
    • [17771] Watchdog alert missing in Salesforce route
  • Storage
    • [10050] Ceph OSD pod is in the CrashLoopBackOff state after disk replacement
  • Bootstrap
    • [16873] Bootstrap fails with ‘failed to establish connection with tiller’ error
  • Upgrade
    • [16233] Bare metal pods fail during upgrade due to Ceph not unmounting RBD
    • [16379,23865] Cluster update fails with the FailedMount warning
    • [9899] Helm releases get stuck in PENDING_UPGRADE during cluster update
    • [15766] Cluster upgrade failure
    • [16141] Alertmanager pod gets stuck in CrashLoopBackOff during upgrade
  • 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