Reputation: 11
I'm working on a new AKS project - this is a POC for now. but I'm trying to understand what is best when delivering a production cluster.
I want to use AKS with an Azure Internal Loadbalancer and then use Traefik as my ingress controller. Regardless of the controller, I assume this the best practice for routing traffic to the front end rather than exposing the controller directly?
I have setup AKS with ACR and the internal load balancer, but for some reason, the backend pools contain all the nodes of each node pool in 1 backend pool. regardless if the pool of nodes is meant for different services - this doesn't seem right or is it that the controller will run on all nodes within all pools? therefor I just route the traffic to the controller?
Hope this makes sense, I'm sure this will lead to more questions, but for now, this will help me with the design.
Upvotes: 1
Views: 886
Reputation: 72171
Yes, this is the design behind this. All of the nodes might contain the pods for your service. So there is no way load balancer knows which nodes have the service and which dont. Do to prevent constant add\remove nodes from the backend, it just assigns all the nodes to the backend pool
Upvotes: 1