stricklandye opened a new issue, #2644: URL: https://github.com/apache/apisix-ingress-controller/issues/2644
### Current Behavior Hi there. I just follow the [doc](https://apisix.apache.org/docs/ingress-controller/getting-started/get-apisix-ingress-controller/) to install apisix ingress controller with a specified etcd host , here is : ```shell helm install apisix \ --version 2.10.1 \ --namespace ingress-apisix \ --create-namespace \ --set apisix.deployment.role=traditional \ --set apisix.deployment.role_traditional.config_provider=yaml \ --set etcd.enabled=false \ --set etcd.host=http://172.16.150.18:2379 \ --set ingress-controller.enabled=true \ --set ingress-controller.config.provider.type=apisix-standalone \ --set ingress-controller.apisix.adminService.namespace=ingress-apisix \ --set ingress-controller.gatewayProxy.createDefault=true \ apisix/apisix ``` but the apisix stucks in `CrashLoopBackOff` status and the log is: ``` /usr/local/openresty//luajit/bin/luajit ./apisix/cli/apisix.lua init /usr/local/openresty//luajit/bin/luajit ./apisix/cli/apisix.lua init_etcd request etcd endpoint 'http://etcd.host:2379/version' error, closed all etcd nodes are unavailable │ Warning! Request etcd endpoint 'http://etcd.host:2379/version' error, closed, retry time=1 Warning! Request etcd endpoint 'http://etcd.host:2379/version' error, closed, retry time=2 ``` So it seems the command args not works as expected. How ever the ectd pod works fine :) ```shell curl http://172.16.150.18:2379/version {"etcdserver":"3.5.12","etcdcluster":"3.5.0"} ``` ### Expected Behavior _No response_ ### Error Logs _No response_ ### Steps to Reproduce 1. Install etcd through helm chart 2. setting etcd.host manually ### Environment version info: ``` apisix ingress-apisix 1 2025-11-02 19:29:40.084123006 +0800 CST deployed apisix-2.10.1 3.11.0 ``` -- 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]
