sebgott opened a new issue, #2667: URL: https://github.com/apache/apisix-ingress-controller/issues/2667
### Current Behavior When trying to deploy APISIX in API-driven mode, the ingress controller is not able to find the default GatewayProxy created by the Helm chart. (the patched apisix image is because of this [issue](https://github.com/apache/apisix/issues/12662) in apisix) ```yaml apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization resources: - namespace.yaml - upstream.yaml namespace: apisix helmCharts: - name: apisix repo: https://charts.apiseven.com version: 2.12.4 releaseName: apisix includeCRDs: false valuesFile: values.yaml valuesInline: image: repository: docker.io/sebgot/apisix tag: 3.14.1-redhat-patched-1 apisix: deployment: role: traditional role_traditional: config_provider: yaml etcd: enabled: false ingress-controller: enabled: true config: provider: type: apisix-standalone webhook: enabled: false apisix: adminService: namespace: apisix gatewayProxy: createDefault: true deployment: image: repository: docker.io/apache/apisix-ingress-controlle ``` Looking at the GatewayProxy, we can see that it has been created ```bash k get gatewayproxies -n apisix NAME AGE apisix-config 18m ``` ```yaml apiVersion: apisix.apache.org/v1alpha1 kind: GatewayProxy metadata: name: apisix-config namespace: apisix spec: provider: controlPlane: auth: adminKey: value: *** type: AdminKey service: name: apisix-admin port: 9180 type: ControlPlane ``` This issue might be realted #2591, but here the issue seemed to have been that createDefault was not defined, but it is defined here and the GatewayProxy is created. ### Expected Behavior AIC is deployed and is able to register configured Upstreams and routes. ### Error Logs ```bash 2025-12-01T13:28:30.339Z ERROR controllers.IngressClass controller/ingressclass_controller.go:102 failed to process infrastructure for ingressclass {"ingressclass": "apisix", "error": "failed to get gateway proxy: GatewayProxy.apisix.apache.org \"apisix-config\" not found"} ``` ```bash 2025-12-01T13:49:30.277Z INFO client client/client.go:176 syncing all resources 2025-12-01T13:49:30.277Z INFO client client/client.go:181 no GatewayProxy configs provided ``` Any endpoint related to routes in the apisix admin API just returns 404 not found ```bash curl -X GET http://127.0.0.1:9180/apisix/admin/routes \ -H "X-API-KEY: ***" <html> <head><title>404 Not Found</title></head> <body> <center><h1>404 Not Found</h1></center> <hr><center>openresty</center> <p><em>Powered by <a href="https://apisix.apache.org/";>APISIX</a>.</em></p></body> </html> ``` ### Steps to Reproduce 1. Deploy provided Kustomize config or this ```bash helm install apisix \ --namespace apisix \ --create-namespace \ --set ingress-controller.enabled=true \ --set ingress-controller.apisix.adminService.namespace=apisix \ --set ingress-controller.gatewayProxy.createDefault=true \ --set ingress-controller.webhook.enabled=false \ apisix/apisix ``` 3. Wait for apisix and AIC pods to be ready 4. Try add upstream/route ### Environment - APISIX Ingress controller version: 2.0.0-rc5 - Kubernetes cluster version: 1.32.8 -- 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]
