hebbaa opened a new issue, #2695:
URL: https://github.com/apache/apisix-ingress-controller/issues/2695
### 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):
--
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]
