Deploy and Use the CCM Component in Registered Clusters-Container Service for Kubernetes(ACK)-阿里云帮助中心

Cloud Controller Manager (CCM) integrates a registered cluster with Alibaba Cloud services. When you create a Kubernetes Service with type: LoadBalancer, CCM automatically provisions and manages a Classic Load Balancer (CLB) instance—including listeners and backend server groups—and keeps it in sync as endpoints and nodes change.

Note

CCM adds only cloud nodes to the CLB backend. On-premises nodes in the registered cluster are not included.

Prerequisites

Before you begin, ensure that you have:

A registered cluster connected to ACK One. See Create an ACK One Registered Cluster
kubectl configured to connect to the cluster. See Obtain cluster kubeconfig and connect to a cluster by using kubectl

How CCM manages load balancers

When you create a Service with type: LoadBalancer, CCM:

Creates a CLB instance and attaches listeners and backend server groups.
Registers cloud nodes in the cluster as CLB backends.
Automatically updates the CLB backend whenever a Service endpoint or a cloud node changes.

Install CCM

Choose one of the following methods.

Install by using onectl

Install onectl on your on-premises machine. See Use onectl to manage registered clusters.

Run the following command:

onectl addon install cloud-controller-manager

Expected output:

Addon cloud-controller-manager, version **** installed.

Install by using the console

Log on to the ACK console. In the left navigation pane, click Clusters.
Click the name of your cluster. In the left navigation pane, choose Configurations > Secrets.
On the Secrets page, click Create from YAML and enter the following content to create a Secret named alibaba-addon-secret.
Note
CCM uses the AccessKey ID and AccessKey secret stored in this Secret to call Alibaba Cloud APIs. Skip this step if the alibaba-addon-secret Secret already exists.
```
apiVersion: v1
kind: Secret
metadata:
  name: alibaba-addon-secret
  namespace: kube-system
type: Opaque
stringData:
  access-key-id: <The AccessKey ID of the RAM user>
  access-key-secret: <The AccessKey secret of the RAM user>
```
In the left navigation pane, choose Operations > Add-ons.
On the Add-ons page, find the Cloud Controller Manager managed component and click Install in the lower-right corner of the card.

What's next

To understand CLB resource behavior and constraints, see Considerations for Service Load Balancer configuration.
To customize CLB settings such as bandwidth, protocol, and access control, see Configure Classic Load Balancer (CLB) by using annotations.