Addressed issues¶
The following issues have been addressed in the Mirantis Container Cloud release 2.7.0 along with the Cluster releases 5.14.0 and 6.14.0:
[13176] [vSphere] Fixed the issue with the cluster network settings related to IPAM disappearing from the cluster provider spec and leading to invalid metadata provided to virtual machines.
[12683] [vSphere] Fixed the issue with the
kaas-ipam
pods being installed and continuously restarted even if IPAM was disabled on the vSphere-based regional cluster deployed on top of an AWS-based management cluster.
[12305] [Ceph] Fixed the issue with inability to define the CRUSH map rules through the
KaaSCephCluster
custom resource. For details, see Operations Guide: Ceph advanced configuration.[10060] [Ceph] Fixed the issue with a Ceph OSD node removal not being triggered properly and failing after updating the
KaasCephCluster
custom resource (CR).
[13078] [StackLight] Fixed the issue with Elasticsearch not receiving data from Fluentd due to the limit of open index shards per node.