2.18.0 (current)

The Mirantis Container Cloud GA release 2.18.0:

• Introduces support for the Cluster release 11.2.0 that is based on Mirantis Container Runtime 20.10.8 and Mirantis Kubernetes Engine 3.5.1 with Kubernetes 1.21.

• Introduces support for the Cluster release 7.8.0 that is based on Mirantis Container Runtime 20.10.8 and Mirantis Kubernetes Engine 3.4.7 with Kubernetes 1.20.

• Supports the Cluster release 8.6.0 that is based on the Cluster release 7.6.0 and represents Mirantis OpenStack for Kubernetes (MOSK) 22.2.

• Supports deprecated Cluster releases 11.1.0 and 7.7.0 that will become unsupported for new deployments in the Container Cloud 2.18.1.

• Does not support the Cluster release 8.5.0 for greenfield deployments. Use the latest Cluster release 8.6.0 instead.

  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.

Caution

Due to the known issue 24802 affecting clusters with enabled proxy, the Container Cloud release upgrade from 2.17.0 to 2.18.0 can trigger automatic update of managed clusters to the latest available Cluster releases in their respective series. For details, see the known issue 24802.

This section outlines release notes for the Container Cloud release 2.18.0.

• Enhancements
  • Ubuntu kernel update for bare metal clusters
  • Support for Ubuntu 20.04 on greenfield vSphere deployments
  • Booting a machine from a block storage volume for OpenStack provider
  • IPSec encryption for Kubernetes networking
  • Support for MITM proxy
  • Support for custom Docker registries
  • Upgrade sequence for machines
  • Enablement of Salesforce propagation to all clusters using web UI
  • Documentation enhancements
• Addressed issues
• Known issues
  • MKE
    • [20651] A cluster deployment or update fails with not ready compose deployments
  • Bare metal
    • [24806] The dnsmasq parameters are not applied on multi-rack clusters
    • [24005] Deletion of a node with ironic Pod is stuck in the Terminating state
    • [20736] Region deletion failure after regional deployment failure
  • Equinix Metal
    • [16379,23865] Cluster update fails with the FailedMount warning
  • Upgrade
    • [24802] Container Cloud upgrade to 2.18.0 can trigger managed clusters update
    • [21810] Upgrade to Cluster releases 5.22.0 and 7.5.0 may get stuck
  • Container Cloud web UI
    • [23002] Inability to set a custom value for a predefined node label
    • [249] A newly created project does not display in the Container Cloud web UI
• Components versions
• Artifacts

See also

• Cluster releases (managed)

• Releases summary

• Deprecation notes