Basic information and release notes for the CCM - Container Compute Service

The cloud controller manager (CCM) provides features to manage load balancing for cross-node communication. This topic introduces the CCM and describes the usage notes and release notes for the component.

Introduction

The CCM allows you to integrate Kubernetes with Alibaba Cloud services, such as Classic Load Balancer (CLB) and Virtual Private Cloud (VPC). CLB is formerly known as Server Load Balancer (SLB). The CCM provides the following features:

If you set Type=LoadBalancer for a Service, the CCM automatically creates a CLB instance for the Service, and configures listeners and backend server groups. When the endpoints of a Service change or the cluster virtual nodes change, the CCM automatically updates the vServer groups of the CLB instance created for the Service.

Usage notes

The CCM automatically creates CLB instances or Network Load Balancer (NLB) instances for Services, and configures listeners and backend server groups. For more information, see Considerations for configuring a LoadBalancer Service.
The CCM allows you to add annotations in Service configurations to customize load balancing. For more information, see Add annotations to the YAML file of a Service to configure CLB instances.
If your cluster fails a precheck before you update the CCM, refer to Troubleshoot precheck failures during CCM update to resolve the issue.

Release notes

June 2024

Version	Release date	Description	Impact
v2.8.3	2024-06-30	New features: The Addon Token authorization mode is supported. The `service.beta.kubernetes.io/alibaba-cloud-loadbalancer-server-group-type` annotation can be used to create NLB server groups of the IP type. For more information about the types and description of NBL server groups, see Overview of NLB server groups. Improvements: Direct access from clients to the Kubernetes API server is supported to prevent stale data generated due to data caching. The logic for creating NLB server groups is optimized to prevent the system from repeatedly creating server groups. IP address verification is performed when you add the IP addresses of elastic network interfaces (ENIs) that are allocated to pods to CLB instances. The verification is performed to ensure that the IP addresses fall within the CIDR block of the VPC where the cluster resides.	No impact on workloads