AlinsRan commented on issue #2749:
URL:
https://github.com/apache/apisix-ingress-controller/issues/2749#issuecomment-4539531465
To make it more intuitive, I think there are **two common multi-writer
scenarios** that can produce the same `*_conf_version` symptom.
### Scenario 1: two `GatewayProxy` objects target the same APISIX cluster
```mermaid
flowchart LR
GP1[GatewayProxy A] --> ADC1[ADC cache/version A]
GP2[GatewayProxy B] --> ADC2[ADC cache/version B]
ADC1 --> APISIX[Same APISIX standalone cluster]
ADC2 --> APISIX
```
If `GatewayProxy A` and `GatewayProxy B` point to the same Service/endpoints
and use the same AdminKey, they are effectively **two independent writers** to
the same APISIX target.
Then the sequence can become:
- writer A pushes config and advances `*_conf_version`
- writer B pushes with its own older cache/version view
- APISIX rejects B with `*_conf_version must be greater than or equal to (X)`
### Scenario 2: two ingress-controller deployments manage the same resources
```mermaid
flowchart LR
C1[Controller instance A] --> Cache1[ADC cache A]
C2[Controller instance B] --> Cache2[ADC cache B]
Cache1 --> APISIX[Same APISIX standalone cluster]
Cache2 --> APISIX
```
If there are multiple controller deployments, and they use the same
`controller_name`, they can both reconcile the same `GatewayClass` /
`IngressClass` resources.
That again becomes **two independent writers**, each with its own cache/sync
loop, and the result can look like periodic overwrite/drift or rotating
`*_conf_version` failures.
So I think the first things to check are simply:
1. Is there more than one `GatewayProxy` targeting the same APISIX
Service/endpoints with the same AdminKey?
2. Is there more than one ingress-controller deployment active for the same
`controller_name`?
If both answers are **no**, then it is much more likely to be a standalone
multi-replica / ADC coordination issue instead.
--
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]
