Kong Ingress Annotation notworking

I have two Kong Ingress

Ingress 1
annotations:
    konghq.com/regex-priority: "1"

    - path: /xxx/(.*)
    pathType: ImplementationSpecific

And

Ingress 2
   annotations:
    konghq.com/regex-priority: "2"

    - path: /xxx/yyy/(.*)
    pathType: ImplementationSpecific

I want request /xxx/yyy/zzz go to Ingress 2 but It always go to Ingress 1.
How can i fix it ? Thanks

Offhand, those look correct. If you check the admin API, are you actually seeing all of those settings correctly propagate? Do the controller container logs indicate that it was unable to sync configuration correctly?

@traines I don’t see any error log in pods

Not sure. I can’t replicate it; the higher-priority route is chosen. Does your actual config from the admin API look different?

15:18:34-0700 esenin $ curl -ks https://localhost:7777/routes | jq ".data[] | .name,.paths[0],.id,.regex_priority" 
"default.one.00"
"/xxx/(.*)"
"d4db9958-23f6-55f7-91d5-8e2e10f4a50f"
1
"default.two.00"
"/xxx/yyy/(.*)"
"ba785bc9-42dc-5d12-8f23-95ca250f7e80"
2
"default.httpbin.00"
"/httpbin"
"df821a3e-b066-59cb-b366-476d531106d2"
100

15:18:57-0700 esenin $ curl -sv -H "kong-debug: 1" 192.168.16.0/xxx/yyy/zzz 2>&1 | grep Kong-Route                
< Kong-Route-Id: ba785bc9-42dc-5d12-8f23-95ca250f7e80
< Kong-Route-Name: default.two.00

If you see similar configuration, i.e. the priorities and paths are indeed being created correctly by the controller, you may want to submit an issue to the gateway team: Issues · Kong/kong · GitHub