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?

How to build the adc server for custom docker image ?

I would appreciate clarification on the above .

[bzp2010]

https://github.com/api7/adc/blob/main/apps/cli/src/main.ts#L7-L8
https://github.com/api7/adc/blob/main/apps/cli/src/command/index.ts#L58-L82
https://github.com/apache/apisix-helm-chart/blob/master/charts/apisix-ingress-controller/templates/deployment.yaml#L105-L107

The server mode certainly exists, but it relies on proprietary environment variable configurations, which are internal details. You wouldn't know this fact when setting up your own Deployment, but it's included in the official Helm chart, where you can learn about it.

It is recommended to use official artifacts rather than exploring on your own, as many internal details are not explicitly documented. Unless you fully understand what you're doing, why would you build and deploy it yourself? You don't even know the basic state of the project's architecture and codebase.