Open QuanTran91 opened 5 months ago
I did find the root cause, turnout there is another route element that points to unavailable k8s service making entire routes not synchronized.
However, I think that it would be better if APISX show the error but still proceed the next route element instead of stopping the synchronization.
it could be that the information is updated in etcd but not displayed on dashboard. Does this issue exist on apisix too?
I did check, the etcd is not updated (that why the route is not working).
Current Behavior
APSIX does not update the new route config in K8s
Expected Behavior
APSIX should update the new route config in K8s
Error Logs
No error log
Steps to Reproduce
Add new route with double splash and then apply the manifest
Remove the double spash and the apply the manifest