Run cluster self-diagnostics¶

Available since MOSK 24.3 TechPreview

MOSK provides cloud operators with a unified tool to perform automatic self-diagnostic checks on both management and managed clusters. This capability allows for easier troubleshooting and preventing potential issues. For instance, self-diagnostic checks can notify you of deprecated features that, if left unresolved, may block upgrades to subsequent versions.

Examples of self-diagnostic checks include:

An SSL/TLS certificate is not set explicitly as plain text
Deprecated OpenStackDeploymentSecret does not exist

Running self-diagnostics is essential to ensure the overall health and optimal performance of your cluster. Mirantis recommends running self-diagnostics before cluster update, node replacement, or any other significant changes in the cluster to optimize maintenance window.

The Diagnostic Controller is a tool with a set of diagnostic checks to automatically perform self-diagnostics of any cluster and help the operator to easily understand, troubleshoot, and resolve potential issues against the following major subsystems: core, bare metal, Ceph, StackLight, Tungsten Fabric, and OpenStack. For illustration of diagnostic checks, refer to the subsection describing the bare metal provider checks.

The Diagnostic Controller analyzes the configuration of the cluster subsystems and reports results of checks that contain useful information about cluster health. These reports may include references to documentation on known issues related to results of checks, along with ticket numbers for tracking the resolution progress of related issues.

The Diagnostic Controller watches for the Diagnostic objects and runs a set of diagnostic checks depending on the cluster version and type, which are identified by the cluster name defined in the spec.cluster section of the Diagnostic object.