Monitor ACK Pro cluster control plane via ARMS Prometheus and follow access best practices.
Prerequisites
-
Available only for ACK Pro clusters running Kubernetes 1.16 or later.
-
Application Real-Time Monitoring Service (ARMS) is activated.
-
The ack-arms-prometheus add-on is installed. ack-arms-prometheus component is installed.
View control plane component dashboards
-
Log on to the ACK console. In the left navigation pane, click Clusters.
-
On the Clusters page, click the name of your cluster. In the left navigation pane, click .
-
On the Prometheus Monitoring page, click the Key Component Monitoring tab.
This tab displays dashboards for ACK Pro API server, ACK Pro etcd, ACK Pro kube-scheduler, ACK Pro cloud-controller-manager, and ACK Pro kube-controller-manager.
NoteTo get the latest dashboards, upgrade the ack-arms-prometheus add-on to the latest version in ACK add-on management. update the ack-arms-prometheus component .
Best practices for accessing control plane components
Follow these practices when accessing control plane components to improve stability for large-scale clusters with 100+ nodes and many Kubernetes resources.
-
To reduce API server and etcd load, read data with informers and listers.
-
For full LIST operations, add the
resourceVersion=0parameter to read from the API server cache instead of etcd. To read directly from etcd, paginate with thelimitparameter. -
Use
Protobuffor API serialization to reduce memory and bandwidth compared to JSON. See Alternate representations of resources. -
Clean up unused Kubernetes resources, such as ConfigMaps, Secrets, and PVCs. Keep pending pods under 1,000 — excess pods overload the kube-apiserver, kube-controller-manager, and kube-scheduler.
-
Monitor control plane resource usage, especially CPU and memory. Sustained high usage can cause OOM errors. If usage stays high, clean up unused resources, optimize client behavior, or split workloads across clusters.
-
Some open-source components heavily load the control plane. Follow community optimization guidance. For example, Argo Workflows recommends specific settings to reduce API load; enable the related configuration when you use Argo Workflows. See Running At Massive Scale.
References
|
Control plane component |
Dashboard |
Description |
Reference |
|
kube-apiserver |
ACK Pro API server |
Metrics, dashboard usage, and troubleshooting for kube-apiserver. |
|
|
cloud-controller-manager |
ACK Pro cloud-controller-manager |
Metrics, dashboard usage, and troubleshooting for cloud-controller-manager. |
|
|
etcd |
ACK Pro etcd |
Metrics, dashboard usage, and troubleshooting for etcd. |
|
|
kube-controller-manager |
ACK Pro kube-controller-manager |
Metrics and dashboard usage for kube-controller-manager. |
|
|
kube-scheduler |
ACK Pro kube-scheduler |
Metrics, dashboard usage, and troubleshooting for kube-scheduler. |
|
|
Custom Prometheus monitoring and alerting |
Custom dashboard name |
Collect metrics and configure alerts for ACK Pro control plane components, such as the API server, etcd, kube-scheduler, KCM, and CCM, with a self-managed Prometheus instance. |