The following issues have been addressed in the Mirantis Container Cloud release 2.19.0 along with the Cluster releases 11.3.0 and 7.9.0:
[16379, 23865] Fixed the issue that caused an Equinix-based management or managed cluster update to fail with the FailedAttachVolume and FailedMount warnings.
 Fixed the issue wherein creation of a new Equinix-based managed cluster failed due to failure to release a new vRouter ID.
 Fixed the issue that caused Ceph clusters to be broken on Equinix-based managed clusters deployed on a Container Cloud instance with a non-default (different from
region-one) region configured.
 Fixed the issue wherein the
dhcp-option=tagparameters were not applied to
dnsmasq.confduring the bootstrap of a bare metal management cluster with a multi-rack topology.
 Fixed the issue wherein the Container Cloud web UI displayed the new release version while update for some nodes was still in progress.
 Fixed the issue wherein the deployment of an Equinix-based management cluster failed with the following error message:
Failed waiting for OIDC configuration readiness: timed out waiting for the condition
 For security reasons, disabled the deprecated TLS v1.0 and v1.1 for the
kaas-uiContainer Cloud services.
 Optimized the number of simultaneous connections to etcd to be open during configuration of Calico policies.
 Fixed the issue wherein Helm Controller was getting stuck during readiness checks due to the timeout for
helmclientbeing not set.
 Fixed a number of security vulnerabilities in the Container Cloud Docker images:
Updated the following Docker images to fix CVE-2022-24407 and CVE-2022-0778:
aws-ebs-csi-driverto fix the following Amazon Linux Security Advisories:
keycloakto fix the following security vulnerabilities:
nginxto fix CVE-2022-28391
frontendto fix CVE-2022-27404
kube-proxyto fix CVE-2022-1292