Sandeep-Raj-49 opened a new issue, #2654: URL: https://github.com/apache/apisix-ingress-controller/issues/2654
### Description Details: - ApisixRoute CRD resources are correctly created in Kubernetes and have status Accepted. - ApisixPluginConfig CRDs (referenced by routes) exist and show as synced. - The APISIX Ingress Controller logs show no errors but do not reflect sync of these CRDs into APISIX routes. - Manual creation of equivalent routes in the UI/admin API immediately makes routes functional. - The APISIX core version is 2.12.0 (installed via Helm chart). - The APISIX ingress controller version is 2.0.0-rc4. CLUSTER: Amazon EKS. - Ingress controller and APISIX are deployed in the same namespace ( apache-apisix ) - Tried adjusting resource sync intervals and namespaces without success. - I have verified network access, RBAC, and DNS; the admin API key is correct. ### Environment - APISIX version (run apisix version): 3.14.0 - Operating system (run uname -a): Linux apisix-58ff4c9fb6-6m9km 6.12.40 apache/apisix#1 SMP PREEMPT_DYNAMIC Mon Sep 8 23:26:50 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux - OpenResty / Nginx version (run openresty -V or nginx -V): nginx version: openresty/1.27.1.2 - etcd version, if relevant (run curl [http://127.0.0.1:9090/v1/server_info):](http://127.0.0.1:9090/v1/server_info%60):) - APISIX Dashboard version, if relevant: - Plugin runner version, for issues related to plugin runners: - LuaRocks version, for installation issues (run luarocks --version): -- 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]
