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 2021/04/15 05:18:51 UTC
[GitHub] [apisix-ingress-controller] tokers commented on issue #377: client address cannot be automatically resolved to upstream by apisix-ingress-conroller
tokers commented on issue #377:
URL: https://github.com/apache/apisix-ingress-controller/issues/377#issuecomment-820105512
> 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.
--
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:
users@infra.apache.org