You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/02/01 12:27:39 UTC
[GitHub] [apisix-ingress-controller] MirtoBusico commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
MirtoBusico commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1026790597
The @gamer22026 suggestion worked for me.
The step I followed:
1) create the namespace
```
kubectl create ns apisix
kubectl label namespace apisix istio-injection=enabled
```
2) get the apisix chart values
```
helm show values apisix/apisix > apisix-values.yaml
```
3) change the lines 115-123 and 355-360
```
...
stream: # L4 proxy (TCP/UDP)
enabled: true
only: false
tcp: # TCP proxy address list
- 9100
- "127.0.0.1:9101"
udp: # UDP proxy address list
- 9200
- "127.0.0.1:9211"
...
dashboard:
enabled: true
ingress-controller:
enabled: true
```
4) installed with:
```
helm install apisix apisix/apisix -f apisix-values.yaml \
--set ingress-controller.config.apisix.serviceNamespace=apisix \
--set ingress-controller.config.apisix.serviceName=apisix-admin \
--namespace apisix
```
Now there is no error and I can define routes
I can also view the route defined in the dashboard.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org