ventaubain opened a new issue, #10344:
URL: https://github.com/apache/apisix/issues/10344

   ### Description
   
   I have a cluster with services meshed by linkerd. Load balancing can be done 
by Apisix ingress and/or linkerd but I don't know how both can collaborate.
   
   Linkerd load balancing description:
   
   `For destinations that are in Kubernetes, Linkerd will look up the IP 
address in the Kubernetes API. If the IP address corresponds to a Service, 
Linkerd will load balance across the endpoints of that Service and apply any 
policy from that Service’s [Service 
Profile](https://linkerd.io/2.14/features/service-profiles/). On the other 
hand, if the IP address corresponds to a Pod, Linkerd will not perform any load 
balancing or apply any [Service 
Profiles](https://linkerd.io/2.14/features/service-profiles/).`
   
   Apisix does load balancing with `ApisixUpstream`
   `ApisixUpstream is a Kubernetes CRD object that abstracts out a Kubernetes 
service and makes it richer by adding load balancing, health check, retry, and 
timeouts. It is designed to have the same name as the Kubernetes service.`
   
   So, with these definitions, Linkerd applies load balancing when requests are 
sent to a Service and Apisix abstracts a Service and this one does load 
balancing. What will be the comportment of the request according this 
architecture ?
   
   
   ### Environment
   
   - APISIX version (run `apisix version`):
   - Operating system (run `uname -a`):
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


-- 
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]

Reply via email to