CCE Ingress Controller Description
Component introduction
The CCE Ingress Controller component implements Kubernetes Ingress semantics based on Baidu AI Cloud’s Application Load Balancer (BLB), providing Layer 7 (HTTP and HTTPS) load balancing capabilities.
Component function
After users create a BLB ingress in the CCE console or create an Ingress resource with the annotation kubernetes.io/ingress.class: cce using YAML, the CCE Ingress Controller component configures corresponding parameters on the application BLB and EIP according to the forwarding rules defined in the ingress resource object and the configuration information in the annotation, thereby realizing the load balancing semantics of the ingress resource object.
Note
- The CCE Ingress Controller functions as a control plane component, with no data traffic flowing through it. Avoid manually adjusting the replica count of this component.
Install component
- Sign in to the Baidu AI Cloud official website and enter the management console.
- Select Product Tour - Containers - Cloud Container Engine and click to enter the CCE management console.
- Click Cluster Management - Cluster List in the left navigation bar.
- Click on the target cluster name in the Cluster List page to navigate to the cluster management page.
- On the Cluster Management page, click O&M & Management > Component Management.
- Select the CCE Ingress Controller component from the component management list and click Install
- Click the OK button in the confirmation dialog to complete the component installation.
Description:
- The CCE Ingress Controller is a managed component in managed clusters and is deployed on Baidu AI Cloud CCE without user intervention for operation and maintenance. In independent clusters, it is deployed on cluster nodes, requiring user operation and maintenance.
- Only components labeled as [Managed] signify that they are deployed as managed components on Baidu AI Cloud CCE.
Deployment status
After installing the CCE Ingress Controller component, the following objects will be deployed in the Kubernetes cluster:
| Object name | Namespace | Resource type | Resource usage |
|---|---|---|---|
| cce-ingress-controller-cce-reserved | kube-system | - | ConfigMap |
| cce-ingress-controller | kube-system | Count of replicas: 3, CPU: 200 m, Memory: 500Mi | Deployment |
| cce-ingress-clusterrole | kube-system | - | ClusterRole |
| cce-ingress-binding | kube-system | - | ClusterRoleBinding |
| cce-ingress-serviceaccount | kube-system | - | ServiceAccount |
Version records
| Version No. | Cluster version compatibility | Update time | Update content | Limitations and impacts |
|---|---|---|---|---|
| 1.3.16 | CCE/v1.18+ | 2024-08-29 | Fix the issue where IP addresses within the VPC might be emptied | None |
| 1.3.15 | CCE/v1.18+ | 2024-08-07 | Support configuring the callback waiting time parameter for the eip creation API | None |
| 1.3.14 | CCE/v1.18+ | 2024-07-01 | None | |
| 1.3.13 | CCE/v1.18+ | 2024-05-28 | None | |
| 1.3.12 | CCE/v1.18/v1.20/v1.22/v1.24/v1.26 | 2024.03.19 | Resolve log issues | None |
| 1.3.11 | CCE/v1.18/v1.20/v1.22/v1.24/v1.26 | 2023.11.22 | Fix the BLB health check port issue | None |
| 1.3.10 | CCE/v1.18/v1.20/v1.22/v1.24/v1.26 | 2023.10.28 | Support health check configurations | None |
| 1.3.9 | CCE/v1.18/v1.20/v1.22/v1.24/v1.26 | 2023-08-18 | Bind tags for ingress-related BLBs and EIPs | None |
| 1.3.8 | CCE/v1.18/v1.20/v1.22/v1.24/v1.26 | 2023-08-11 | Improve listener configurations: Support configuring EIP bandwidth ; support enabling the deletion protection function for BLBs by default |
None |
| 1.3.7 | CCE/v1.18/v1.20/v1.22/v1.24/v1.26 | 2023-07-24 | Internal optimizations | None |
| 1.3.6 | CCE/v1.18/v1.20/v1.22/v1.24/v1.26 | 2023-05-17 | Support configuring the default EIP bill type ; fix the issue of ignoring cordoned nodes ; support session persistence configuration, scheduling algorithms and XFF |
None |
| 1.3.5 | CCE/v1.18/v1.20/v1.22 | 2023-01-17 | Cancel updates to fields such as BLB Name ; add a switch for Pod direct connection function ; fix the service port matching error ; be compatible with 1.22 version clusters |
None |
| 1.3.4 | CCE/v1.18/v1.20 | 2022-06-22 | Support XFF and Real-IP ; fix several issues |
None |
| 1.3.3 | CCE/v1.18/v1.20 | 2022-05-24 | Be compatible with old-version forwarding rules | None |
