request help: Will the controller not automatically synchronize with the old ingress?

[wgy-home]

Issue description

# kubectl get ingress -n dev 
NAME               CLASS    HOSTS                           ADDRESS   PORTS   AGE
apisix-dashboard   apisix   apisix-dashboard.inchtek.tech             80      33m
root@master-01:/etc/kubeasz# kubectl get pods -n dev 
NAME                                         READY   STATUS    RESTARTS      AGE
apisix-85f74bd4f6-dnj5h                      1/1     Running   0             33m
apisix-dashboard-757774b56f-74s46            1/1     Running   4 (32m ago)   33m
apisix-etcd-0                                1/1     Running   0             33m
apisix-etcd-1                                1/1     Running   0             33m
apisix-etcd-2                                1/1     Running   0             33m
apisix-ingress-controller-845ccb9598-m6fws   1/1     Running   0             13m

Deploy apisix and aipsix-ingress-controller through helm, and enable the ingress of the dashboard, because after the ingress is created, the controller has not been started yet.

After waiting for the controller to start, ingress does not automatically create a route. Why?

But I can successfully create the route after manually deleting the ingress and rebuilding it.

controller version ：apisix-ingress-controller:1.7.0

Environment

• your apisix-ingress-controller version (output of apisix-ingress-controller version --long): 1.7.0
• your Kubernetes cluster version (output of kubectl version): Server Version: v1.30.1
• if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a): Linux master-01 5.15.0-117-generic chore: prometheus metrics handler #127-Ubuntu SMP Fri Jul 5 20:13:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux