Ensure that the Cluster Check feature is triggered at least once per week to guarantee proactive health monitoring for your ACK clusters, minimizing downtime and optimizing the reliability of your containerized applications. By default, Cluster Check is not automatically triggered, the cluster inspection can be started using the Container Service for Kubernetes (ACK) console.
Enabling the Cluster Check monitoring feature in Container Service for Kubernetes (ACK) ensures automated health checks on the ACK cluster, proactively identifying and resolving issues. This enhances overall cluster stability and reliability, minimizing downtime and optimizing the performance of containerized applications.
Audit
To determine if Cluster Check is triggered at least once per week, perform the following operations:
Remediation / Resolution
To ensure that Cluster Check is triggered periodically for your ACK clusters, perform the following operations:
References
- Alibaba Cloud Documentation
- Work with cluster check
- Cluster check items and suggestions on how to fix cluster issues
- Alibaba Cloud CLI Documentation
- View all clusters
- ListClusterChecks
- RunClusterCheck