All Products
Search
Document Center

Container Service for Kubernetes:Collect the logs of control plane components in ACK Edge clusters

Last Updated:Mar 26, 2026

When a control plane component behaves unexpectedly — API errors, scheduling failures, OOM kills — you need its logs to diagnose the issue. ACK Edge lets you collect control plane component logs from an ACK Edge cluster into a Simple Log Service (SLS) project in your Alibaba Cloud account, where you can search and analyze them.

Prerequisites

Before you begin, make sure that you have:

Six components are collected by default. Components with default collection disabled (cluster-autoscaler, ack-goatscaler, and kuberay-operator) require separate enablement. See Supported components for details.

Enable log collection

  1. Log on to the ACK console. In the left navigation pane, click Clusters.

  2. On the Clusters page, find your cluster and click its name. In the left-side pane, choose Operations > Log Center.

  3. On the Log Center page, click the Control Plane Component Logs tab, then click Enable Component Log Collection. The system installs the log collection component. After installation completes, collected logs appear on the page.

View logs

View logs in the ACK console

Two navigation paths lead to the same log view.

From Cluster information:

  1. On the cluster details page, click the Basic Information tab.

  2. On the right side of Control Plane Component Logs, click View.

  3. Use the drop-down menu in the upper-left corner to select a component.

From Operations:

  1. In the left-side pane of the cluster details page, choose Operations > Log Center.

  2. Use the drop-down menu in the upper-left corner to select a component.

View logs in the Simple Log Service console

  1. Log on to the Simple Log Service console.

  2. In the Projects section, click the name of the SLS project used by your ACK cluster.

  3. In Log Storage > Logstores, select the Logstore for the component you want to inspect.

For query syntax, see Index-based query and analysis.

Logstores for control plane components

Each control plane component writes to a dedicated SLS Logstore. Use the Logstore name to locate the right log stream when querying in the SLS console.

Six components are collected by default. To enable collection for the remaining three, update the list of components for log collection.

For background on Kubernetes control plane components, see Kubernetes Components.

Component Logstore Collected by default What it logs
kube-apiserver apiserver Yes Exposes the Kubernetes API.
kube-controller-manager kcm Yes Activity from the core control loops (core control links) embedded in Kubernetes.
kube-scheduler scheduler Yes Pod scheduling decisions from the default Kubernetes scheduler.
Cloud Controller Manager ccm Yes Integration events between Kubernetes and Alibaba Cloud services, including Classic Load Balancer (CLB) and Virtual Private Cloud (VPC). CLB was formerly known as Server Load Balancer (SLB).
controlplane-events controlplane-events Yes Operational events from control plane components, such as out-of-memory (OOM) kills.
ALB Ingress controller alb Yes Provides a unified entry for Services based on Application Load Balancer (ALB).
cluster-autoscaler cluster-autoscaler No Node autoscaling component for ACK.
ack-goatscaler ack-goatscaler No Instant elasticity events for ACK nodes.
kuberay-operator kuberay-operator No Ray cluster management events, including scheduling, elastic quota, and resource priority decisions.

Disable log collection

  1. On the Clusters page, find your cluster and click its name. In the left-side pane, choose Operations > Log Center.

  2. On the Log Center page, click the Control Plane Component Logs tab, then click Close.

What's next