This section outlines new features and enhancements introduced in the Cluster release 6.14.0.
StackLight logging levels¶
Significantly enhanced the StackLight log collection mechanism to avoid
collecting and keeping an excessive amount of log messages when it is not
essential. Now, during or after deployment of StackLight, you can select one of
the 9 available logging levels depending on the required severity. The default
logging level is
Remote logging to syslog¶
Implemented the capability to configure StackLight to forward all logs to an external syslog server. In this case, StackLight will send logs both to the syslog server and to Elasticsearch, which is the default target.
Log collection optimization¶
Improved the log collection mechanism by optimizing the existing and adding new log parsers for multiple Container Cloud components.
Implemented the capability to configure Ceph Controller to start pods on the taint nodes and manage the resources of Ceph nodes. Now, when bootstrapping a new management or managed cluster, you can specify requests, limits, or tolerations for Ceph resources. You can also configure resource management for an existing Ceph cluster. However, such approach may cause downtime.
Ceph objectStorage section in KaasCephCluster¶
Improved user experience by moving the
rgw section of the
KaasCephCluster CR to a common
objectStorage section that now includes
all RADOS Gateway configurations of a Ceph cluster. The
spec.rgw section is
deprecated. However, if you continue using
spec.rgw, it will be
automatically translated into the new
objectStorage.rgw section during the
Container Cloud update to 2.6.0.
Ceph maintenance orchestration¶
Implemented the capability to enable Ceph maintenance mode using the
maintenance flag not only during a managed cluster update but also when
required. However, Mirantis does not recommend enabling
production deployments other than during update.
Dedicated network for the Ceph distributed storage traffic¶
Added the possibility to configure dedicated networks for the Ceph cluster access and replication traffic using dedicated subnets. Container Cloud automatically configures Ceph to use the addresses from the dedicated subnets after you assign the corresponding addresses to the storage nodes.
Ceph Multisite configuration¶
Implemented the capability to enable the Ceph Multisite configuration that allows object storage to replicate its data over multiple Ceph clusters. Using Multisite, such object storage is independent and isolated from another object storage in the cluster.
Ceph troubleshooting documentation¶
On top of continuous improvements delivered to the existing Container Cloud guides, added the Troubleshoot Ceph section to the Operations Guide. This section now contains a detailed procedure on a failed or accidentally removed Ceph cluster recovery.