martin-schulze-e2m opened a new issue, #974:
URL: https://github.com/apache/apisix-helm-chart/issues/974
I have the following config:
```
apisix:
# standalone api driven mode: enable etcd free configuration via
ingress-controller
# taken from
https://apisix.apache.org/docs/apisix/deployment-modes/#api-driven
deployment:
# mode: standalone this runs `ln -s /apisix-config/apisix.yaml
/usr/local/apisix/conf/apisix.yaml`
role: traditional # deploy dataplane and control plane in the same pod
role_traditional:
config_provider: yaml
etcd:
enabled: false
...
```
Everything is working fine. However, apisix logs are full of this error:
```
2026/06/08 13:38:39 [warn] 52#52: *433281 [lua] health_check.lua:114:
report_failure(): update endpoint: http://etcd.host:2379 to unhealthy, client:
<redacted>, server: , request: "PUT /apisix/admin/configs HTTP/1.1", host:
"<redacted>:9180", request_id: "a1549ed0d3602e27359a72b189752699"ยด
2026/06/08 13:38:39 [warn] 52#52: *433281 [lua] v3.lua:247: _request_uri():
http://etcd.host:2379: failed to parse domain: failed to query the DNS server:
dns server error: 3 name error. Retrying, client: <redacted>, server: ,
request: "PUT /apisix/admin/configs HTTP/1.1", host: "<redacted>:9180",
request_id: "a1549ed0d3602e27359a72b189752699"
```
Why is apisix trying to connect to etcd in standalone mode?
After having a look at the deployment.yml of the chart I noticed that the
`etcd` config is only omitted from the config map when `mode: standalone`.
However in api driven standalone mode, we have `mode: traditional`:
https://github.com/apache/apisix-helm-chart/blob/46c3862bd8cbc8b254024c8354b559a01406dab0/charts/apisix/templates/configmap.yaml#L377-L407
--
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]
