bug: ADC execution error

[hanxinimm]

Current Behavior

I'm using APISIX in standalone mode with ADC (Autonomous Decentralized Control). After modifying the configs via APISIX Admin API on port 9180, the apisix-ingress-controller keeps throwing errors. What am I doing wrong?
I tried deleting the APISIX Pod, which caused all configurations to be lost. Even after re-syncing the configurations, the issue persists.

21T06:28:29.552Z ERROR provider.executor client/executor.go:142 failed to run http sync for server {"server": "http://10.1.237.161:9180", "error": "ServerAddr: http://10.1.237.161:9180, Err: http://10.1.237.161:9180: consumers_conf_version must be greater than or equal to (3314986)"}
2026-04-21T06:28:29.552Z ERROR provider.client client/client.go:269 failed to execute adc command {"config": {"name":"GatewayProxy/ingress-apisix/apisix-config","serverAddrs":["http://10.1.237.161:9180"],"tlsVerify":false}, "error": "ADC execution error for GatewayProxy/ingress-apisix/apisix-config: [ServerAddr: http://10.1.237.161:9180, Err: http://10.1.237.161:9180: consumers_conf_version must be greater than or equal to (3314986)]"}
2026-04-21T06:28:29.553Z ERROR provider.client client/client.go:210 failed to sync resources {"name": "GatewayProxy/ingress-apisix/apisix-config", "error": "ADC execution errors: [ADC execution error for GatewayProxy/ingress-apisix/apisix-config: [ServerAddr: http://10.1.237.161:9180, Err: http://10.1.237.161:9180: consumers_conf_version must be greater than or equal to (3314986)]]"}
2026-04-21T06:28:29.553Z ERROR provider apisix/provider.go:282 failed to sync {"error": "failed to sync 1 configs: GatewayProxy/ingress-apisix/apisix-config"}

Expected Behavior

No response

Error Logs

No response

Steps to Reproduce

helm install apisix apisix/apisix
--namespace ingress-apisix
--create-namespace
--set apisix.deployment.role=traditional
--set apisix.deployment.role_traditional.config_provider=yaml
--set etcd.enabled=false
--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
--skip-crds
2. put config with /apisix/admin/configs

Environment

• APISIX Ingress controller version (run apisix-ingress-controller version --long)
• apisix-ingress-controller:2.0.1
• Kubernetes cluster version (run kubectl version)
• OS version if running APISIX Ingress controller in a bare-metal environment (run uname -a)

[Baoyuantop]

Hi @hanxinimm, thanks for reporting this issue.

Based on the error logs, the root cause is a configuration version conflict.

The error consumers_conf_version must be greater than or equal to (3314986) originates from APISIX's standalone mode Admin API (apisix/admin/standalone.lua). This API requires that the configuration version number must be monotonically increasing — the new consumers_conf_version cannot be lower than the currently stored version.

You mentioned modifying configurations directly via the Admin API (port 9180) before the Ingress Controller sync. This pushed the consumers_conf_version to a high value (3314986). When the Ingress Controller subsequently tries to sync its managed configuration via ADC, its version number is lower than what APISIX has stored, so the request gets rejected.

The issue persists after deleting the APISIX Pod likely because the ADC Server maintains its own cache (via the CacheKey mechanism), or the Ingress Controller still carries the old version number when re-syncing.

Recommended solutions:

1. Avoid mixed management: When APISIX is managed by the Ingress Controller, do not modify configurations directly via the Admin API. All changes should go through Kubernetes CRDs or the Ingress Controller workflow.
2. Recovery steps: To recover from the current state, try cleaning up both sides simultaneously — delete the APISIX Pod and restart the Ingress Controller Pod to clear the ADC cache, ensuring version numbers are re-aligned.