bug: ApisixIngress synced failed: failed to get upstream aries-dev_aries-authorization-service: not found

[zt4123]

Current Behavior

Uable to get apisix upstream, it was looking for an upstream with wrong name.

Expected Behavior

upstream aries-authorization-service should be found, instead of aries-dev_aries-authorization-service

Error Logs

2024-04-12T04:00:59+08:00 warn apisix/cluster.go:1164 upstream not found {"id": "60c33191", "url": "http://apisix-admin.ingress-apisix.svc.cluster.local:9180/apisix/admin/upstreams/60c33191", "cluster": "default"}
2024-04-12T04:00:59+08:00 error apisix/apisix_upstream.go:333 failed to get upstream aries-dev_aries-authorization-service: not found
2024-04-12T04:00:59+08:00 warn apisix/apisix_upstream.go:489 sync ApisixUpstream failed, will retry {"object": {"Type":4,"Object":{"Key":"aries-dev/aries-authorization-service","OldObject":null,"GroupVersion":"apisix.apache.org/v2"},"OldObject":null,"Tombstone":null}, "error": "not found"}

Steps to Reproduce

1. install apisix helm chart 2. create a new upstream in namespace aries-dev 3. check ingress-controller logs, it's looking for upstream with wrong name, APISIX concatenated the namespace name with upstream name: aries-dev_aries-authorization-service

Environment

• APISIX Ingress controller version (run apisix-ingress-controller version --long) 0.14.0
• Kubernetes cluster version
  Client Version: v1.28.3
  Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
  Server Version: v1.27.7-gke.1121002