Marco-Zheng commented on issue #377: URL: https://github.com/apache/apisix-ingress-controller/issues/377#issuecomment-820264152
> > Now i have a little confusing is the specific interaction between apisix, apisix-ingress-controller, and k8s, The apisix-ingress-controller will automatically fetch all clients in K8 and automatically resolve to Apisix's upstream(each upstream is bound to a unique k8s service name and may have specific service tags, such as version, etc.). We can then route to the service directly by binding the resolved upstream ID to the route. > > What apisix-ingress-controller resolves is the Kubernetes Service Name/FQDN, not client address. > > Client address is the remote IP address where the requests sent from. It can be configured as IPv4/IPv6/CIDR. Here has a problem, i configure the route /patient/patient/* as below , but it also said that 404 Route Not Found `curl -i -X GET http://ip:host/patient/patient/id -H "Host: httpbin.org" -H 'apikey: superSecretAPIKey'`  It was amazing that there had no route of `/get` which i was update to`/patient/patient/*` can get the reseult.. `curl -i -X GET http://ip:host/get -H "Host: httpbin.org" -H 'apikey: superSecretAPIKey'` ![Uploading image.png…]() -- 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: [email protected]
