Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!
Starting with MOSK 25.2, the MOSK documentation set covers all product layers, including MOSK management (formerly MCC). This means everything you need is in one place. The separate MCC documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.
Addressed issues¶
The following issues have been addressed in the Mirantis Container Cloud release 2.18.0 along with the Cluster releases 11.2.0 and 7.8.0:
[24075] Fixed the issue with the Ubuntu 20.04 option not displaying in the operating systems drop-down list during machine creation for the AWS and Equinix Metal with public networking providers.
Warning
After Container Cloud is upgraded to 2.18.0, remove the values added during the workaround application from the
Cluster
object.[9339] Fixed the issue with incorrect health monitoring for Kubernetes and MKE endpoints on OpenStack-based clusters.
[21710] Fixed the issue with a too high threshold being set for the
KubeContainersCPUThrottlingHigh
StackLight alert.[22872] Removed the inefficient
ElasticNoNewDataCluster
andElasticNoNewDataNode
StackLight alerts.[23853] Fixed the issue wherein the
KaaSCephOperationRequest
resource created to remove the failed node from the Ceph cluster was stuck with theFailed
status and an error message inerrorReason
. TheFailed
status blocked the replacement of the failed master node on regional clusters of the bare metal and Equinix Metal providers.[23841] Improved error logging for load balancers deletion:
The reason for the inability to delete an LB is now displayed in the provider logs.
If the search of an FIP associated with the LB deletion returns more than one FIP, the provider returns an error instead of deleting all found FIPs.
[18331] Fixed the issue with the Keycloak admin console menu disappearing on the Add identity provider page during configuration of an identity provider SAML.