tokers commented on issue #676: URL: https://github.com/apache/apisix-ingress-controller/issues/676#issuecomment-917421716
> > > The apisix-dashboard service has the type "NodePort"(http://172.16.100.101:31803), while the test backend service "httpbin" has the type "ClusterIP"(http://10.102.62.126:80) > > > The route proxied "local.httpbin.org/httpbin" to the service "httpbin", curl http://local.httpbin.org:31803/httpbin was redirected to apisix-dashboard, that's the problem. > > > > > > You sent requests to apisix-dashboard (`:31803`), so of course you saw the apisix-dashboard. By the way, have you add resolution for domain `local.httpbin.org`? How did it map to the Kubernetes worker node or the LB IP? > > @tokers thanks, doesn't the apisix-dashboard act as a api-gateway? That is, by adding a path to the host, all requests matched the path are forward to the real backend service. So, if http://172.16.100.101:31803 is the apisix-dashboard, then http://172.16.100.101:31803/httpbin is the "httpbin" service. > "local.httpbin.org" is resolved by /etc/hosts, this is not the problem. Ofcourse not 😂, APISIX Dashboard is a management component of APISIX. Indeed you don't require it as the APISIX Ingress Controller already acts as the manager of APISIX cluster. You should send requests to APISIX cluster, i.e. the `apisix-gateway` service. -- 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]
