Searching for results...

No results

Your search did not match anything from Mirantis documentation.
Check your spelling or try different keywords.

An error occurred

An error occurred while using the search.
Try your search again or contact us to let us know about it.

Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!

Now, the MOSK documentation set covers all product layers, including MOSK management (formerly Container Cloud). This means everything you need is in one place. Some legacy names may remain in the code and documentation and will be updated in future releases. The separate Container Cloud documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.

Troubleshoot Mirantis Kubernetes Engine alerts

This section describes the investigation and troubleshooting steps for the Mirantis Kubernetes Engine (MKE) cluster alerts.

MKEAPICertExpirationHigh

Root cause

MKE cluster root certificate authority (CA) expires in less than 10 days.

Investigation

  1. Connect to an MKE manager node through SSH.

  2. List the nodes and their statuses:

    docker node ls

  3. Switch to the node marked as leader.

  4. On the leader node, retrieve the CA certificate and inspect its Validity field:

    docker swarm ca | openssl x509 -noout -text

Mitigation

Contact Mirantis support for a detailed procedure on certificate rotation.

See also

Docker documentation: docker swarm ca

MKEAPICertExpirationMedium

Root cause

MKE cluster root CA expires in less than 30 days.

Investigation and mitigation

Refer to MKEAPICertExpirationHigh.