Container Service for Kubernetes (ACK) provides the cluster check feature. You can use this feature to check whether your cluster meets the requirements for updates or migration before you get started.
Prerequisites
An ACK cluster is created. For more information, see Create an ACK Serverless cluster.
The cluster runs as expected. You can log on to the ACK console, navigate to the Clusters page, and then check whether the cluster is in the Running state.
Table of contents
Introduction to cluster check
ACK provides a variety of cluster check features, including cluster update check, cluster migration check, component installation check, component update check. A precheck is automatically triggered before a cluster is updated or migrated, a component is installed or updated. The operation is performed only if the cluster passes the precheck. You can also manually trigger a cluster check without specifying any parameters to check the resources, components, and configurations of your cluster and view optimization suggestions. We recommend that you periodically check and maintain your cluster to mitigate potential risks.
Procedure
The procedures for cluster update check, component check, cluster migration check, and are similar.
Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, click the name of the cluster that you want to manage and choose in the left-side navigation pane.
In the left-side navigation pane of Container Intelligence Service console, choose a check item below Cluster Check and follow the instructions. ACK cluster check consists of update check, component check, migration check, and node pool check.
After the check is performed, you can view the progress and report on the check page.
View the report
After the cluster update check is complete, you can fix issues based on the suggestions displayed on the Report page.
The report displays the following flags:
Normal: No actions are required.
Warning: Confirm the severity of each issue. Troubleshoot the issues that may cause cluster anomalies.
Error: Troubleshoot the issues at the earliest opportunity to avoid cluster errors.
You can click the flag of a check item to view information about the instance that is checked and the result. The result includes the content of the check, the possible impacts, and the suggestions on how to fix the issues. You can handle the issues based on the impacts and suggestions.
Using deprecated APIs is considered an exception in a cluster update check. Security risks exist when you use deprecated APIs.