[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-835276611 Got it. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-834242867 > > when I run in kubeSphere，I got some warn message like this： > > 2021-05-07T17:45:11+08:00 warn controller/endpoint.go:93 service kube-system/kube-scheduler was deleted > > 2021-05-07T17:45:11+08:00 warn controller/endpoint.go:93 service default/ceph.com-rbd was deleted > > 2021-05-07T17:45:11+08:00 warn controller/endpoint.go:93 service default/ceph.com-cephfs was deleted > > 2021-05-07T17:45:12+08:00 warn controller/endpoint.go:93 service kube-system/kube-controller-manager was deleted > > 2021-05-07T17:45:13+08:00 warn controller/endpoint.go:93 service kube-system/kube-scheduler was deleted > > 2021-05-07T17:45:13+08:00 warn controller/endpoint.go:93 service default/ceph.com-rbd was deleted > > 2021-05-07T17:45:13+08:00 warn controller/endpoint.go:93 service default/ceph.com-cephfs was deleted > > 2021-05-07T17:45:14+08:00 warn controller/endpoint.go:93 service kube-system/kube-controller-manager was deleted > > and also I found that no route was published to the apisix-gateway! > > this is bug of apisix ingress controller? > > These logs are redundant but harmless, also, You don't give any useful contexts, I cannot judge whether this is a bug. If you want to report your problem in detail, please create another issue, thanks! -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-834242577 > when I run in kubeSphere，I got some warn message like this： > > 2021-05-07T17:45:11+08:00 warn controller/endpoint.go:93 service kube-system/kube-scheduler was deleted > 2021-05-07T17:45:11+08:00 warn controller/endpoint.go:93 service default/ceph.com-rbd was deleted > 2021-05-07T17:45:11+08:00 warn controller/endpoint.go:93 service default/ceph.com-cephfs was deleted > 2021-05-07T17:45:12+08:00 warn controller/endpoint.go:93 service kube-system/kube-controller-manager was deleted > 2021-05-07T17:45:13+08:00 warn controller/endpoint.go:93 service kube-system/kube-scheduler was deleted > 2021-05-07T17:45:13+08:00 warn controller/endpoint.go:93 service default/ceph.com-rbd was deleted > 2021-05-07T17:45:13+08:00 warn controller/endpoint.go:93 service default/ceph.com-cephfs was deleted > 2021-05-07T17:45:14+08:00 warn controller/endpoint.go:93 service kube-system/kube-controller-manager was deleted > > and also I found that no route was published to the apisix-gateway! > > this is bug of apisix ingress controller? These logs are redundant but harmless, also, You don't give any useful contexts, I cannot judge whether this is a bug. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-830995674 > But when I entry apisix pod request my http server is connect. see ... > > ``` > [root@k8smaster01 ~]# kubectl -n ws get pods -owide > NAMEREADY STATUSRESTARTS AGEIP NODE NOMINATED NODE READINESS GATES > apisix-gw-deployment-7bf998c895-ckprd 1/1 Running 0 85d10.244.1.3 k8snode04 > apisix-ingress-controller-fb9fc6579-prlzk 1/1 Running 0 99m10.244.12.24 k8snode07 > myhttp-794dc65cdc-ph2f9 1/1 Running 0 136d 10.244.4.198 k8snode02 > test-network-776895fdbd-8xb7p 1/1 Running 0 54d10.244.3.75k8snode01 > [root@k8smaster01 ~]# kubectl -n ws exec -it apisix-gw-deployment-7bf998c895-ckprd -- curl http://myhttp-svc:9527 > Hello world ,The runtime os is [ linux ], Now member is [ myhttp-794dc65cdc-ph2f9 ] > [root@k8smaster01 ~]# kubectl -n ws exec -it apisix-gw-deployment-7bf998c895-ckprd -- curl http://myhttp-svc:9527/dbsecurity > Hello world ,The runtime os is [ linux ], Now member is [ myhttp-794dc65cdc-ph2f9 ] > [root@k8smaster01 ~]# ls > anaconda-ks.cfg dd.txt epel-release-latest-7.noarch.rpm sudo-1.9.5-3.el6.x86_64.rpm test.sh xengine-dev-configmap.yaml > [root@k8smaster01 ~]# kubectl -n ws exec -it apisix-gw-deployment-7bf998c895-ckprd -- curl http://10.244.4.198:9527 > Hello world ,The runtime os is [ linux ], Now member is [ myhttp-794dc65cdc-ph2f9 ] > [root@k8smaster01 ~]# > ``` > > And apisix pod have some error log . > > ``` > 10.244.12.24 - - [02/May/2021:15:08:53 +0800] apisix-gw-lb:9080 "GET /apisix/admin/upstreams/fe7b69e0 HTTP/1.1" 404 39 0.002 "-" "Go-http-client/1.1" - - - "http://apisix-gw-lb; > 10.244.12.24 - - [02/May/2021:15:08:53 +0800] apisix-gw-lb:9080 "GET /apisix/admin/upstreams/4157840a HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-gw-lb; > 10.244.12.24 - - [02/May/2021:15:08:53 +0800] apisix-gw-lb:9080 "GET /apisix/admin/upstreams/313d7085 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-gw-lb; > 10.244.12.24 - - [02/May/2021:15:11:53 +0800] apisix-gw-lb:9080 "GET /apisix/admin/upstreams/fe7b69e0 HTTP/1.1" 404 39 0.002 "-" "Go-http-client/1.1" - - - "http://apisix-gw-lb; > 10.244.12.24 - - [02/May/2021:15:11:53 +0800] apisix-gw-lb:9080 "GET /apisix/admin/upstreams/4157840a HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-gw-lb; > 10.244.12.24 - - [02/May/2021:15:11:53 +0800] apisix-gw-lb:9080 "GET /apisix/admin/upstreams/313d7085 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-gw-lb; > 10.244.12.24 - - [02/May/2021:15:14:53 +0800] apisix-gw-lb:9080 "GET /apisix/admin/upstreams/fe7b69e0 HTTP/1.1" 404 39 0.002 "-" "Go-http-client/1.1" - - - "http://apisix-gw-lb; > 10.244.12.24 - - [02/May/2021:15:14:53 +0800] apisix-gw-lb:9080 "GET /apisix/admin/upstreams/4157840a HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-gw-lb; > 10.244.12.24 - - [02/May/2021:15:14:53 +0800] apisix-gw-lb:9080 "GET /apisix/admin/upstreams/313d7085 HTTP/1.1" 404 39 0.004 "-" "Go-http-client/1.1" - - - "http://apisix-gw-lb; > 10.244.12.24 - - [02/May/2021:15:17:53 +0800] apisix-gw-lb:9080 "GET /apisix/admin/upstreams/fe7b69e0 HTTP/1.1" 404 39 0.003 "-" "Go-http-client/1.1" - - - "http://apisix-gw-lb; > 10.244.12.24 - - [02/May/2021:15:17:53 +0800] apisix-gw-lb:9080 "GET /apisix/admin/upstreams/4157840a HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-gw-lb; > 10.244.12.24 - - [02/May/2021:15:17:53 +0800] apisix-gw-lb:9080 "GET /apisix/admin/upstreams/313d7085 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-gw-lb > ``` > > my ApisixRoute : > > ```yaml > apiVersion: apisix.apache.org/v1 > kind: ApisixRoute > metadata: > name: myhttp > spec: > rules: > - host: storm.myhttp.io > http: > paths: > - backend: > serviceName: myhttp-svc > servicePort: 9527 > path: /* > ``` > > my server information: > > ``` > # deployment > Name: myhttp > Namespace: ws > CreationTimestamp: Thu, 19 Nov 2020 14:37:32 +0800 > Labels: app=myhttp > Annotations:deployment.kubernetes.io/revision: 8 > Selector: app=myhttp > Replicas: 1 desired | 1 updated | 1 total | 1 available | 0 unavailable > StrategyType: RollingUpdate > MinReadySeconds:0 > RollingUpdateStrategy: 25% max unavailable, 25% max surge
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-825400637 > @tokers And why APISIX logs many upstream 404 request？ > > ``` > 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/152e4f9e HTTP/1.1" 404 39 0.002 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; > 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/606b3be0 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; > 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/76a75cec HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; > 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/76a75cec HTTP/1.1" 404 39 0.002 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; > 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/857c0d11 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; > 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/fcd5c4d6 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; > 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/5b9e2a1 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; > 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/10986d9 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; > 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/5b6fae7c HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; > 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/5e521191 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; > 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/7abcf232 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; > ``` The endpoints controller inside apisix-ingress-controller will try to fetch the Upstream object so it can apply the newest endpoints set to upstream node, if the object not found, it means the endpoints/service is not related with any ApisixRoute objects, and endpoints controller will ignore it. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-823969789 @wjx8382 Have you ever seen how many routes are there in APISIX? -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-823299160
> > From the configuration snippet the `allow_admin` was rendered correctly,
so it should work, would you like to try the `0.5.0` version, it was released
few days ago.
>
> After using the `0.5.0` version,apisix-ingress-controller logs
>
> ```
> 2021-04-20T15:26:34+08:00 warncontroller/apisix_route.go:205 sync
ApisixRoute failed, will retry {"object":
{"Type":1,"Object":{"Key":"tools/httpserver-route","OldObject":null,"GroupVersion":"apisix.apache.org/v2alpha1"},"Tombstone":null},
"error": "2 errors occurred:\n\t* object missing primary index\n\t* object
missing primary index\n\n"}
> ```
>
> In addition, why `helm install apisix` will also generate
apisix-ingress-controller, but its version is `0.4.0`, `helm install
apisix-ingress-controller` will generate apisix-ingress-controller which
version is `0.5.0`, which should I use?
The error `object missing primary index` occurred basically due to you wrote
some route on apisix-dashboard. It's **NOT** a recommended way.
> In addition, why helm install apisix will also generate
apisix-ingress-controller, but its version is 0.4.0, helm install
apisix-ingress-controller will generate apisix-ingress-controller which version
is 0.5.0, which should I use?
We recommend you to use the `0.5.0` release.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-822434727 From the configuration snippet the `allow_admin` was rendered correctly, so it should work, would you like to try the `0.5.0` version, it was released few days ago. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-821056240 @wjx8382 Could you please paste the `config-default.yaml` and `config.yaml` in the APISIX pod? -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-821022251
> @tokers After I tweak the `allow.ipList` in
`apisix-helm-chart/charts/apisix/values.yaml`,there are still errors.
>
> ```
> allow:
> # The ip range for allowing access to Apache APISIX
> ipList:
> - 127.0.0.1/24
> - 172.16.110.186
> - 10.233.99.249
> ```
>
> apisix-ingress-controller logs
>
> ```
> 2021-04-16T14:31:58+08:00 warnapisix/upstream.go:113 upstream not
found{"fullname": "tools_httpbin-85d57ddd75-wtmwh_80", "url":
"http://apisix-admin:9180/apisix/admin/upstreams/5e521191;, "cluster": ""}
> 2021-04-16T14:31:58+08:00 error state/builder.go:191failed to
create upstream tools_httpbin-85d57ddd75-wtmwh_80: unexpected status code 403;
error message:
> 403 Forbidden
>
> 403 Forbidden
> openresty
>
>
> ```
>
> APISIX logs
>
> ```
> 10.233.99.249 - - [16/Apr/2021:06:31:45 +] apisix-admin:9180 "GET
/apisix/admin/upstreams/5e521191 HTTP/1.1" 404 39 0.000 "-"
"Go-http-client/1.1" - - - "http://apisix-admin:9180;
> 10.233.99.249 - - [16/Apr/2021:06:31:58 +] apisix-admin:9180 "GET
/apisix/admin/upstreams/5e521191 HTTP/1.1" 404 39 0.002 "-"
"Go-http-client/1.1" - - - "http://apisix-admin:9180;
> ```
Are you sure the IP of apisix-ingress-controller is configured correctly?
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-819276970 @wjx8382 Your APISIX Admin API doesn't allow apisix-ingress-controller to access it. Please tweak the `allow.ipList` option, https://github.com/apache/apisix-helm-chart/blob/master/charts/apisix/values.yaml#L124. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-819178628 @wjx8382 You should change the log level, you can set it to `debug` by adding a `--set` option when using helm install. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-818648270
Maybe there are some internal bugs, could you paste the error log of
apisix-ingress-controller.
Just paste the result of `kubectl logs -f {apisix-ingress-controller pod
name}`.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-818440741 I found these routes were created by apisix-dashboard, just do not mix the use of apisix-ingress-controller and manual dashboard confiugration. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-818440525 It seems that there are some other routes in your APISIX cluster? How are they created? -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-818383744
> @tokers Why does `kubectl exec -it -n tools apisix-7987b5b7f-tmrk7 -- curl
http://127.0.0.1:9080/headers -H 'Host: local.httpbin.org'` returns
`{"error_msg":"404 Route Not Found"}`
>
> ```
> # httpbin-route.yaml
> apiVersion: apisix.apache.org/v2alpha1
> kind: ApisixRoute
> metadata:
> name: httpserver-route
> spec:
> http:
> - name: rule1
> match:
> hosts:
> - local.httpbin.org
> paths:
> - /*
> backend:
> serviceName: httpbin-85d57ddd75-wtmwh
> servicePort: 80
> ```
Could you access the apisix admin API by
```
kubectl exec -it -n tools apisix-7987b5b7f-tmrk7 -- curl
http://127.0.0.1:9180/apisix/admin/routes
```
To see the routes?
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-817686675 > I have installed APISIX, how can I access httpbin through apisix > > > > > apisix-ingress-controller itself is not the proxy component but the controller to control the proxy plane (APISIX), you should access APISIX instead. By the way, did you install APISIX? > > > > > > > > > Our service is client-->nginx-->ingress-nginx-->service-->pod. I want to replace ingress-nginx with apisix. Should I use APISIX instead of apisix-ingress-controller? (I have installed APISIX:2.3-alpine) > > > > > > No, you need both the apisix-ingress-controller and APISIX. Just as I said above, apisix-ingress-controller is the control plane and APISIX is the data plane that processes the traffic. Even in ingress-nginx, there are two components, the one is nginx (DP) and the other is the controller (CP). > > I have installed APISIX, how can I access httpbin through apisix? See http://apisix.apache.org/docs/ingress-controller/practices/proxy-the-httpbin-service for details. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-817495354 > > apisix-ingress-controller itself is not the proxy component but the controller to control the proxy plane (APISIX), you should access APISIX instead. By the way, did you install APISIX? > > Our service is client-->nginx-->ingress-nginx-->service-->pod. I want to replace ingress-nginx with apisix. Should I use APISIX instead of apisix-ingress-controller? (I have installed APISIX:2.3-alpine) No, you need both the apisix-ingress-controller and APISIX. Just as I said above, apisix-ingress-controller is the control plane and APISIX is the data plane that processes the traffic. Even in ingress-nginx, there are two components, the one is nginx (DP) and the other is the controller (CP). -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #356: request help: KubeSphere setup
tokers commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-817075481 apisix-ingress-controller itself is not the proxy component but the controller to control the proxy plane (APISIX), you should acesss APISIX instead. By the way, have you installed APISIX? -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
