Help Center/ Cloud Container Engine/ User Guide/ Networking/ Ingresses/ LoadBalancer Ingresses/ Configuring Multiple Ingresses to Use the Same Load Balancer
Updated on 2025-09-15 GMT+08:00

Configuring Multiple Ingresses to Use the Same Load Balancer

Multiple Ingresses Accessing the Same External ELB Port

In a cluster, you can configure multiple ingresses to use the same ELB listener, allowing them to use the same port on a single load balancer. If two ingresses have different listener configurations, the listener configuration of the earlier ingress (known as the first route) will be used.

Figure 1 Diagram for multiple ingresses to use the same external ELB port

The following table lists listener parameters.

Listener

Annotation

Helpful Links

Configuring ELB Certificates

kubernetes.io/elb.tls-certificate-ids

kubernetes.io/elb.tls-ciphers-policy

Configuring an HTTPS Certificate for a LoadBalancer Ingress

Using HTTP/2

kubernetes.io/elb.http2-enable

Configuring HTTP/2 for a LoadBalancer Ingress

Configuring Timeout for an Ingress

kubernetes.io/elb.keepalive_timeout

kubernetes.io/elb.client_timeout

kubernetes.io/elb.member_timeout

Configuring Timeout for a LoadBalancer Ingress

Ensure that the configurations of different listeners for various ingresses are synchronized. To do so, perform the following operations:

  1. Log in to the CCE console and click the cluster name to access the cluster console.
  2. In the navigation pane, choose Services & Ingresses. Then, click the Ingresses tab, and choose More > Update in the Operation column.
  3. Synchronize Configuration is available if the listener configuration of the ingress differs from that of the ELB. Click Synchronize Configuration. Then, the listener configuration will be automatically synchronized.

Multiple Ingresses Associated with the Same Service Accessing the Same ELB Port

When you create an ingress, CCE automatically adds a backend server group on the ELB based on the associated Service.

In a cluster, if multiple ingresses access the same ELB port and are associated with the same Service and port, only one backend server group will be created on the ELB. The configuration applied to this backend server group will be that of the first ingress created (referred to as the first route). If ingresses use multiple load balancers to access the same Service, multiple backend server groups will be created. In this case, the sequence of ingress configurations does not matter.

Figure 2 Diagram for multiple ingresses associated with the same Service to access the same ELB port

The following table lists backend server settings.

Backend Server Setting

Annotation

Helpful Link

Slow start

kubernetes.io/elb.slowstart

Configuring a Slow Start for a LoadBalancer Ingress