This section outlines new features and enhancements introduced in the Cluster release 6.18.0.
Graceful MCR upgrade¶
Implemented a graceful Mirantis Container Runtime (MCR) upgrade from 19.03.14 to 20.10.5 on existing Container Cloud clusters.
MKE logs gathering enhancements¶
Improved the MKE logs gathering by replacing the default
DEBUG logs level
INFO. This change reduces the unnecessary load on the MKE cluster
caused by an excessive amount of logs generated with the
Log verbosity for StackLight components¶
Implemented the capability to configure the verbosity level of logs produced by all StackLight components or by each component separately.
StackLight log level severity setting in web UI¶
Implemented the capability to set the default log level severity for all StackLight components as well as set a custom log level severity for specific StackLight components in the Container Cloud web UI. You can update this setting either during a managed cluster creation or during a post-deployment configuration.
Improvements to StackLight alerting¶
Implemented the following improvements to StackLight alerting:
Added the following alerts:
PrometheusMsTeamsDownthat raises if
ServiceNowWebhookReceiverDownthat raises if
SfNotifierDownthat raises if the
MKEAPICertExpirationWarningthat inform on SSL certificates expiration.
KubeContainersCPUThrottlingHighthat raises in case of containers CPU throttling.
KubeletDownthat raises if kubelet is down.
Removed the following inefficient alerts:
Reworked a number of alerts to improve alerting efficiency and reduce alert flooding.
Reworked the alert inhibition rules to match the receivers.
Updated Alertmanager to v0.22.2.
Changed the default behavior of the Salesforce alerts integration. Now, by default, only
Criticalalerts will be sent to the Salesforce.
StackLight node labeling improvements¶
Implemented the following improvements for the StackLight node labeling during a cluster creation or post-deployment configuration:
Added a verification that a cluster contains minimum 3 worker nodes with the StackLight label for clusters with StackLight deployed in HA mode. This verification applies to cluster deployment and update processes. For details on how to add the StackLight label before upgrade to the latest Cluster releases of Container Cloud 2.11.0, refer to Upgrade managed clusters with StackLight deployed in HA mode.
Added a notification about the minimum number of worker nodes with the StackLight label for HA StackLight deployments to the cluster live status description in the Container Cloud web UI.
Removal of the StackLight label from worker nodes along with removal of worker nodes with StackLight label can cause the StackLight components to become inaccessible. It is important to keep the worker nodes where the StackLight local volumes were provisioned.
Salesforce feed update¶
Implemented the capability to enable feed update in Salesforce using
feed_enabled parameter. By default, this parameter is set to
to save API calls.
Proxy configuration on existing clusters¶
Implemented the capability to add or configure proxy on existing Container Cloud managed clusters using the Container Cloud web UI.
Upgraded Ceph from 14.2.19 (Nautilus) to 15.2.13 (Octopus) and Rook from 1.5.9 to 1.6.8.
On top of continuous improvements delivered to the existing Container Cloud guides, added the following procedures:
Hyperconverged Ceph improvement¶
Implemented the capability to define Ceph tolerations and resources management
KaaSCephCluster spec using the native Rook way for setting
resource requirements for Ceph daemons.
Ceph cluster status¶
MiraCephLog custom resource by adding more information about
all Ceph cluster entities and their statuses. The
MiraCephLog values are now integrated to
KaaSCephCluster.status and can be viewed using the
Ceph Manager modules¶
Implemented the capability to define a list of Ceph Manager modules to enable
on the Ceph cluster using the
mgr.modules parameter in