AlinsRan commented on issue #2708:
URL:
https://github.com/apache/apisix-ingress-controller/issues/2708#issuecomment-3888337417
# Issue Investigation Checklist
## 1. Logs and Runtime Information
### 1.1 Complete Logs
Please provide the full logs during the time when the issue occurred.
#### Ingress Pod
- ingress container logs
- adc-server container logs
- If possible, please enable debug logging and reproduce the issue.
Debug configuration references:
- Ingress debug:
https://github.com/apache/apisix-helm-chart/blob/9d5ad2a28f7e75490e05f9dd977cd29791f13629/charts/apisix-ingress-controller/values.yaml#L80
- ADC debug:
https://github.com/apache/apisix-helm-chart/blob/master/charts/apisix-ingress-controller/values.yaml#L77
#### APISIX Pod
- `error.log`
- `access.log` entries that include `/apisix/admin/configs` API calls
---
## 2. Restart Verification
Please confirm:
- Does restarting `ingress-apisix` resolve the issue?
This helps determine whether the problem originates from the ingress/ADC
side or the APISIX data plane.
---
## 3. Standalone API Configuration Comparison
When the issue occurs:
- Call the standalone API
- Retrieve the data plane configuration **before and after restart**
- Compare the configuration differences
Standalone API reference:
https://apisix.apache.org/zh/docs/apisix/deployment-modes/#example
This step is critical for root cause analysis.
---
## 4. Resource Limits and Usage
Please provide:
- Resource requests/limits for ingress pods
- Resource requests/limits for APISIX pods
- CPU and memory usage when the issue occurs
Insufficient resources may cause sync failures or abnormal behavior.
---
# 2. Configuration Conflict Investigation
## 2.1 GatewayProxy Conflict
Please check whether multiple `GatewayProxy` resources are pointing to the
same data plane.
You can run:
```bash
kubectl get gatewayproxy -A -o yaml
````
Multiple `GatewayProxy` resources sharing the same data plane may cause
configuration conflicts.
---
## 2.2 Multiple Ingress Controllers
Please confirm:
* Whether multiple `apisix-ingress-controller` instances are deployed in the
same Kubernetes cluster
* If yes, whether they are properly isolated (e.g., ingressClass, namespace
scope, etc.)
Improper isolation may also lead to configuration conflicts.
---
# 3. Investigation Goals
The goal is to determine:
* Whether the issue is on the ingress/ADC side or the APISIX data plane side
* Whether there is a configuration conflict
* Whether improper resource limits are causing synchronization failures
--
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]
