Configuring Multiple Ingresses to Use the Same External ELB Port
In a cluster, multiple ingresses can share a 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.
The following table lists listener parameters.
Listener | Annotation | Documentation |
|---|---|---|
Configuring ELB Certificates | kubernetes.io/elb.tls-certificate-ids kubernetes.io/elb.tls-ciphers-policy | |
Using HTTP/2 | kubernetes.io/elb.http2-enable | |
Configuring Timeout for an Ingress | kubernetes.io/elb.keepalive_timeout kubernetes.io/elb.client_timeout kubernetes.io/elb.member_timeout | |
Configuring a Blocklist/Trustlist | kubernetes.io/elb.acl-id kubernetes.io/elb.acl-status kubernetes.io/elb.acl-type | |
Configuring an HTTP/HTTPS Header | kubernetes.io/elb.x-forwarded-port kubernetes.io/elb.x-forwarded-for-port kubernetes.io/elb.x-forwarded-host |
Ensure that the configurations of different listeners for various ingresses are synchronized. To do so, perform the following operations:
- Log in to the CCE console and click the cluster name to access the cluster console.
- In the navigation pane, choose Services & Ingresses. Then, click the Ingresses tab, and choose More > Update in the Operation column.
- 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.