request help: Crash Loop in Custom Image: Ingress Controller v2.0.0 sidecar pattern conflicts with ADC v0.23.1 "server" command removal

[hebbaa]

Issue description

I am encountering a crash loop when deploying a custom Docker image for the APISIX Ingress Controller v2.0.0.

The Setup:

I am building my own image from source (Ingress Controller v2.0.0).

During the build process, I am pulling the ADC binary v0.23.1 (based on current documentation/scripts).

My Kubernetes Deployment YAML is based on the official v2.0.0 manifests, which configures the ADC sidecar to run as a server:

YAML

args:
  - "server"
  - "--listen"
  - "unix:/sockets/adc.sock"

The Issue: The container fails to start with the following error:

Error: unknown command "server"
Analysis: It appears that ADC v0.23.1 is a pure CLI tool and has removed the server subcommand entirely. However, the architecture for Ingress Controller v2.0.0 (specifically the GatewayProxy pattern) seems to still rely on a long-running ADC sidecar process to handle config syncing.

Questions:

For Ingress Controller v2.0.0, is it still supported to use the newer ADC versions (v0.23.x)? If so, how should the Deployment arguments be configured since the server command is gone?

I would appreciate clarification on the correct version matrix for this setup.

Thanks!

Environment

• your apisix-ingress-controller version (output of apisix-ingress-controller version --long): 2.0.0
• your Kubernetes cluster version (output of kubectl version):
• if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):

[AlinsRan]

You may be missing some environment variables. pls ref:
https://github.com/apache/apisix-helm-chart/blob/c64832b9fcc260b612f356706e011d7a042177dc/charts/apisix-ingress-controller/templates/deployment.yaml#L99-L111

[hebbaa]

The ask is how i can build custom docker image for adc-server? The adc binary doesn't contain server part as is .