sebgott commented on issue #2667: URL: https://github.com/apache/apisix-ingress-controller/issues/2667#issuecomment-3605844536
I notice that the ingress class is seemingly referring to a GatewayProxy in the default namespace which is not correct. I changed it to "apisix" instead and after restarting the ingress controller, it no longer logs the ```no GatewayProxy configs provided```error. I still get 404 on any defined routes, but I think this might be a bug with the changes I made the my patched apisix img([this](https://github.com/apache/apisix/issues/12662#:~:text=2%20weeks%20ago-,I%20tested,-out%20%40Falven%20proposed)) as the apisix.yaml file does not exist anymore for some reason. ```yaml apiVersion: networking.k8s.io/v1 kind: IngressClass metadata: name: apisix spec: controller: apisix.apache.org/apisix-ingress-controller parameters: apiGroup: apisix.apache.org kind: GatewayProxy name: apisix-config namespace: default scope: Namespace ``` Issue is probably resolved, but why would this refer to the default namespace? I cannot see any way to change this in the helm chart at least? -- 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]
