vonsch commented on issue #10422:
URL: https://github.com/apache/apisix/issues/10422#issuecomment-2296821617
Is it possible this issue is related to usage of builtin etcd? We have
following configuration in our apisix-ingress-controller helmchart values.yaml:
```
config:
...
etcdserver:
enabled: true
image:
repository: docker.io/apache/apisix
tag: 3.9.1-debian
```
We are curious if it would be worthy to switch out of builtin etcd to the
standalone full-fledged etcd cluster for better isolation if this is etcd
related issue or not.
Related to number of routes for testing - on our testing cluster, where we
hit this issue cca , we have currently 11 `apisixroutes.apisix.apache.org` CRDs
(much higher number of production clusters) with total of 270 backends in form
like (some of them have more complex match stanzas, some of them also using
regex_uri etc)
```
- backends:
- serviceName: xxx-service
servicePort: 9040
match:
exprs:
- op: RegexMatch
subject:
scope: Path
value: /api/v\d+/schemas/result
hosts:
- xxx.yyy.com
paths:
- /api/*
name: asdasdasdasd-some-random-name
plugins:
- config:
http_to_https: true
enable: true
name: redirect
priority: 999
timeout:
read: 182s
...
- backends:
- serviceName: xxx-yyy
servicePort: 9092
match:
hosts:
- xxx.yyy.com
paths:
- /analyze
- /components
- /dashboards
- /modeler
- /metrics
- /
- /*
name: some-random-name
plugins:
- config:
http_to_https: true
enable: true
name: redirect
- config:
regex_uri:
- ^/(analyze|components|dashboards|metrics|modeler)$
- /$1/
enable: true
name: proxy-rewrite
priority: 101
timeout:
read: 182s
```
--
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]
