Container Service Kubernetes clusters allow you to reuse Server Load Balancer (SLB) instances. You can bind one SLB instance to multiple applications that are deployed in a Container Service Kubernetes cluster in Enterprise Distributed Application Service (EDAS) to save resources. This way, fixed IP addresses are also provided for the applications so that operations and maintenance (O&M) become easier.
- The Cloud Controller Manager (CCM) component of the Container Service Kubernetes cluster
is upgraded. For more information about how to upgrade the component, see Manage system components.
Container Service Kubernetes clusters have multiple templates. The CCM component is upgraded to the following versions for the managed Kubernetes cluster template and the dedicated Kubernetes cluster template:
Notice If you do not upgrade the CCM component of the Container Service Kubernetes cluster, the SLB instance fails to be reused. The existing listeners of the SLB instance are deleted and the application traffic may drop to zero.
- The CCM version of a managed Kubernetes cluster is V184.108.40.206-g93c7140-aliyun or later.
- The CCM version of a dedicated Kubernetes cluster is v220.127.116.11-g3f39653-aliyun or later.
- Create an SLB instance.
- When you bind an SLB instance on the Application Overview page in the EDAS console, you cannot reuse the SLB instance that is purchased (created) in the EDAS console.
- The created SLB instance must be in the same virtual private cloud (VPC) as the application to which the SLB instance is to be bound.
- The limits of using SLB are learned. For more information, see Limits.
Reuse an SLB instance
To reuse an SLB instance, bind an existing SLB instance to an application. The procedure for binding an existing SLB instance is the same as that for binding a new SLB instance. The difference only lies in selecting an SLB instance. For more information about the procedure, see Bind SLB instances.
This section describes notes when you reuse an SLB instance.
- Select SLB: Select the SLB instance that you created in the SLB console from the drop-down list on the right side, rather than the SLB instance that is purchased in the EDAS console.
- SLB Port: The port must be an unused container port.