bzp2010 commented on issue #2654: URL: https://github.com/apache/apisix-ingress-controller/issues/2654#issuecomment-3565108220
> It shows as "True" but the route doesn't work. ``` 2025-11-19T09:06:47Z warn client/client.go:173 no GatewayProxy configs provided ``` This indicates that no Gateway Proxy Custom Resource has been configured. Please verify this. This requires using the Helm installation with the `--set ingress-controller.gatewayProxy.createDefault=true` flag to create the default GatewayProxy, or creating it manually. Subsequently, your IngressClass must reference this GatewayProxy, which is a specific requirement differing from 1.x. Please verify that your environment has been correctly configured with the above. Use the `helm template` command to check what the K8s manifest should look like. ref: https://apisix.apache.org/docs/ingress-controller/install/ > If I create the same route via admin API / UI, the route wont be visibile when I do kubectl get apisixroute There has never been a reverse sync feature, and we shall never implement such functionality. Reverse sync: Allows an externally created resource to be inspected by AIC from APISIX Admin API for creation as a Kubernetes Cluster Resource (CR). I seriously advise against this practice. Not only does it undermine the constraints of declarative configuration, but it also places your business at risk. Should logical conflicts arise between resources configured via AIC and those configured through the Admin API or Dashboard, the gateway's forwarding behaviour becomes unpredictable. -- 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]
