wgy-home opened a new issue, #2296: URL: https://github.com/apache/apisix-ingress-controller/issues/2296
### Issue description ```shell # 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): - your Kubernetes cluster version (output of kubectl version): - if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a): -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
