The following issues have been addressed in the Mirantis Container Cloud release 2.16.0 along with the Cluster releases 11.0.0 and 7.6.0:
 Fixed the issue wherein removal of a bare metal-based management cluster failed with a timeout.
 Fixed the issue with the Container Cloud web UI reporting a successful upgrade of a baremetal-based management cluster while running the previous release.
 Fixed the issue that caused inability to deploy an OpenStack-based managed cluster if DVR was enabled.
 Fixed the CVE-2021-3520 security vulnerability in the
cinder-csi-plugin imageDocker image.
 Fixed the issue that caused deployment of an Equinix Metal based management cluster with private networking to fail with the following error message during the Ironic deployment:
0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims.
 Fixed the issue wherein the bare metal host was trying to configure an Equinix node as UEFI even for nodes with UEFI disabled.
 Fixed the issue wherein the Ironic agent could not properly determine which disk will be the first disk on the node. As a result, some Equinix servers failed to boot from the proper disk.
 Fixed the issue wherein some Equinix servers were configured in BIOS to always boot from PXE, which caused the operation system to fail to start from disk after provisioning.
 Adjusted the
kaas-exporterresource requests and limits to avoid issues with the
kaas-exportercontainer being occassionally throttled and OOMKilled, preventing the Container Cloud metrics gathering.
 Adjusted the RAM usage limit and disabled indices monitoring for
prometheus-es-exporterpod crash looping due to low memory issues.
 Fixed the following security vulnerabilities in the
 Fixed the issue wherein namespace deletion failed after removal of a managed cluster.
 Fixed the issue with inability to automatically remove a Ceph node when removing a worker node.
 Fixed the CVE-2019-20916 security vulnerability in IAM.