regend opened a new issue, #2576:
URL: https://github.com/apache/apisix-ingress-controller/issues/2576

   ### Current Behavior
   
   When one of the routers in APISIX is configured with a Kubernetes service 
whose endpoint does not exist (e.g., due to misconfiguration or other reasons), 
it causes the entire APISIX instance to malfunction, and the ingress logs show 
the following error:
   `2025-09-24T03:31:58Z    error   adc/adc.go:431  failed to execute adc 
command   {"error": "ADC execution error for apisix/apisix-config: [ServerAddr: 
http://apisix-admin.apisix:9180, Err: failed to sync resources: Error: Lint 
configuration\nThe following errors were found in configuration:\n#1 Expected 
array, received null at service: \"dev2_dev2-xqd-biz-base-censor_0-1\", field: 
\"upstream.nodes\"\n#2 Expected array, received null at service: 
\"dev2_dev2-xqd-biz-base-censor_0-0\", field: \"upstream.nodes\"\n, exit err: 
exit status 1]", "config": 
{"name":"apisix/apisix-config","serverAddrs":["http://apisix-admin.apisix:9180"],"tlsVerify":false}}`
   
   
   
   ### Expected Behavior
   
   Expected behavior: If a single router's service configuration is incorrect, 
only that specific router should be affected, without impacting the entire 
APISIX instance globally.
   
   
   
   ### Error Logs
   
   _No response_
   
   ### Steps to Reproduce
   
   1. update k8s service make it wrong and endpoint not exist
   2. watch ingress-controller logs
   
   ### Environment
   
   - APISIX Ingress controller version (run `apisix-ingress-controller version 
--long`)
   - Kubernetes cluster version (run `kubectl version`)
   - OS version if running APISIX Ingress controller in a bare-metal 
environment (run `uname -a`)
   apisix:3.13.0
   apisix-ingress-controller:2.0.0-rc3


-- 
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]

Reply via email to