# Node affinity for Ingress

**URL:** <https://forums.suse.com/t/node-affinity-for-ingress/6431>\
**Category:** General\
**Created:** [May 22, 2017, 12:21pm UTC](https://forums.suse.com/t/node-affinity-for-ingress/6431 "2017-05-22T12:21:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![laszlocloud](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/laszlocloud/32/2439_2.png) [@laszlocloud](https://forums.suse.com/u/laszlocloud)\
**Post date:** [May 22, 2017, 12:21pm UTC](https://forums.suse.com/t/node-affinity-for-ingress/6431/1 "2017-05-22T12:21:17Z")

</div>

Is there a way to tell the Ingress controller to launch the Load Balancers with a specific node affinity?

I’d like to scale the Ingress to two, and add those two nodes to an Azure Load Balancer.

---

<div class="post-metadata">

**Author:** ![laszlocloud](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/laszlocloud/32/2439_2.png) [@laszlocloud](https://forums.suse.com/u/laszlocloud)\
**Post date:** [May 22, 2017, 12:29pm UTC](https://forums.suse.com/t/node-affinity-for-ingress/6431/2 "2017-05-22T12:29:31Z")

</div>

Not just for Ingress. When I simply create my service definition with “type: LoadBalancer” Rancher launches a LoadBalancer container right on my etcd node 🙂

---

<div class="post-metadata">

**Author:** ![laszlocloud](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/laszlocloud/32/2439_2.png) [@laszlocloud](https://forums.suse.com/u/laszlocloud)\
**Post date:** [May 22, 2017, 12:38pm UTC](https://forums.suse.com/t/node-affinity-for-ingress/6431/3 "2017-05-22T12:38:12Z")

</div>

Okay, perhaps scheduling the LB on all hosts is the answer for my question: [http://docs.rancher.com/rancher/v1.6/en/kubernetes/ingress/#example-of-a-load-balancer-scheduled-on-all-hosts](http://docs.rancher.com/rancher/v1.6/en/kubernetes/ingress/#example-of-a-load-balancer-scheduled-on-all-hosts)

I was coming with the premise that there is a dedicated LB for all services. Like the Router in Openshift on the “infra” nodes. It’s not quite the case, since Rancher launches an LB per Ingress definition. Seems having a global Ingress and one Ingress config is the way to go.

---

<div class="post-metadata">

**Author:** ![laszlocloud](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/laszlocloud/32/2439_2.png) [@laszlocloud](https://forums.suse.com/u/laszlocloud)\
**Post date:** [May 22, 2017, 12:39pm UTC](https://forums.suse.com/t/node-affinity-for-ingress/6431/4 "2017-05-22T12:39:23Z")

</div>

lol, literally one paragraph bellow: [http://docs.rancher.com/rancher/v1.6/en/kubernetes/ingress/#example-of-scheduling-a-load-balancer-on-a-host](http://docs.rancher.com/rancher/v1.6/en/kubernetes/ingress/#example-of-scheduling-a-load-balancer-on-a-host)

Nice. Nothing to see here 🙂