Ensure Cluster Check triggered at least once per week for Kubernetes Clusters

MediumLevel 1Manual reviewalibaba

Description

Kubernetes Engine's cluster check feature helps you verify the system nodes and components healthy status. When you trigger the checking, the process would check on the health state of each node in your cluster and also the cluster configuration as kubelet\docker daemon\kernel and network iptables configuration, if ... Kubernetes Engine uses the node's health status to determine if a node needs to be repaired. A node reporting a Ready status is considered healthy. Reported as a manual review item: the benchmark audit needs console review or organisational judgement.

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

Using the management console: 1. Logon to ACK console 2. Select the target cluster and open the More pop-menu for advance options on cluster. 3. Select Overview page on left column and check if the Last check status is Normal. 4. Verify the checking time and details in Global Check.

How it is fixed

Fix method: Guidance or infrastructure patch

Using the management console: 1. Logon to ACK console 2. Select the target cluster and open the More pop-menu for advance options on cluster 3. Select Global Check and click the Start button to trigger the checking

Properties

Operating systems: Any
Tags: alibabaack
Reference: CIS Alibaba Cloud Foundation Benchmark v2.0.1 - 7.4 Ensure Cluster Check triggered at least once per week for Kubernetes Clusters