Baoyuantop commented on issue #13033: URL: https://github.com/apache/apisix/issues/13033#issuecomment-4294202222
Thanks @manueljishi for sharing your configuration. Based on your description, you're using APISIX Ingress Controller with the ApisixRoute CRD in a Kubernetes deployment. This is fundamentally different from the original reporter's setup (standalone Docker APISIX with `service_id` / `upstream_id` references). The symptoms you describe — requests being routed to the wrong Service and upstream not updating after Pod recreation — sound more like an Ingress Controller watch/sync issue rather than an APISIX core routing bug. Suggestions: 1. Please go ahead and test on 3.16.0 as you planned. 2. If the issue persists, I'd recommend opening a **new issue** in the [apache/apisix-ingress-controller](https://github.com/apache/apisix-ingress-controller) repo with: - Full version info for both APISIX and the Ingress Controller - Your Helm values configuration - A minimal reproducible ApisixRoute + Service YAML - APISIX `error.log` and Ingress Controller logs captured during the 404/502 responses 3. This will help the Ingress Controller maintainers investigate more effectively. Looking forward to your 3.16.0 test results. -- 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]
