The following issues have been addressed in the Mirantis Container Cloud release 2.6.0 and the Cluster release 5.13.0:
 [LCM] Fixed the issue with inability to delete a Container Cloud project with attached MKE clusters that failed to be cleaned up properly.
 [LCM] Added
vrrp_script chk_myscriptto the Keepalived configuration to prevent issues with VIP (Virtual IP) pointing to a node with broken Kubernetes API.
 [LCM] Fixed the issue with
kubeletbeing randomly stuck, for example, after a management cluster upgrade. The fix enables automatic restart of
kubeletin case of failures.
 [bootstrap] Renamed the SSH key used during bootstrap for every cloud provider from
openstack_tmpto an accurate and clear
 [StackLight] Fixed the issue with StackLight failing to integrate with an external proxy with authentication handled by a proxy server and ignoring the HTTP
Authorizationheader for basic authentication passed by Prometheus Alertmanager.
 [StackLight] Fixed the issue with Patroni pod failing to start and remaining in the
CrashLoopBackOffstatus after the management cluster update.
 [IAM] Fixed the issue with the Keycloak pods failing to start during a management cluster bootstrap with the Failed to update database exception in logs.
 [BM] Fixed the issue with the persistent volumes (PVs) that are created using local volume provisioner (LVP) not being mounted on the dedicated disk labeled as
local-volumeand using the root volume instead.
 [BM] Fixed the issue with the bootstrap.sh preflight script failing with a timeout waiting for
 [vSphere] Fixed the issue with the vSphere-based managed cluster projects failing to be cleaned up because of stale secret(s) related to the RHEL license object(s).