What Should I Do If a Loadbalancer Ingress' Forwarding Rule Matching Does Not Work as Expected?

Symptom

When multiple forwarding rules are configured for an ingress, a request may match more than one rule. In such cases, traffic may be routed to an unexpected backend.

Possible Cause

This issue typically occurs when the forwarding rule priorities on the load balancer do not align with expectations. By default, the load balancer orders forwarding rules based on domain and URL matching logic. If the advanced forwarding policy feature is enabled, the load balancer assigns rule priorities based on the order in which you created them. Without explicit priority control, the final matching result may differ from what you expected.

For details about the forwarding policy priorities, see Forwarding Policy Priorities of LoadBalancer Ingresses.

If there are multiple similar path rules, you can configure the forwarding policy priorities to ensure that traffic is routed as expected. This prevents service exceptions caused by default sorting.

Solution

1. Check whether the advanced forwarding policy feature is enabled for a listener.
   1. Log in to the CCE console and click the cluster name to access the cluster console.
   2. In the navigation pane, choose Services and Ingresses. In the right pane, click the Ingresses tab.
   3. Locate the row containing the ingress and click the load balancer name to go to its details page.

      

   4. Click the Listeners tab, locate the listener based on the protocol and port, click the listener name, and check whether Advanced Forwarding is enabled.

      

2. If it is, customize the forwarding policy priorities using, for example, kubernetes.io/elb.ingress-order and kubernetes.io/elb.rule-priority-enabled. For details, see Configuring the Priorities of Forwarding Rules for LoadBalancer Ingresses.