# Rancher Ingress controller HaProxy or Nginx

**URL:** <https://forums.suse.com/t/rancher-ingress-controller-haproxy-or-nginx/10248>\
**Category:** Rancher 1.x\
**Created:** [May 2, 2018, 3:38pm UTC](https://forums.suse.com/t/rancher-ingress-controller-haproxy-or-nginx/10248 "2018-05-02T15:38:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![StoneFury](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/stonefury/32/3909_2.png) [@StoneFury](https://forums.suse.com/u/StoneFury)\
**Post date:** [May 2, 2018, 3:38pm UTC](https://forums.suse.com/t/rancher-ingress-controller-haproxy-or-nginx/10248/1 "2018-05-02T15:38:14Z")

</div>

So in prior versions the rancher ingress controller was haproxy based. Is this going to continue or has Rancher moved to favor Nginx? I was just reading the 2.0 GA announcement and I read that RKE uses an nginx controller. Just curious, trying to nail down what Rancher is going with so I can focus on learning that LB.

tnx

---

<div class="post-metadata">

**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\
**Post date:** [May 3, 2018, 6:04am UTC](https://forums.suse.com/t/rancher-ingress-controller-haproxy-or-nginx/10248/2 "2018-05-03T06:04:50Z")

</div>

The nginx ingress controller is the defacto standard and that is what we’re deploying with RKE/Rancher.

---

<div class="post-metadata">

**Author:** ![Justin\_DynamicD](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/justin_dynamicd/32/3997_2.png) [@Justin\_DynamicD](https://forums.suse.com/u/Justin_DynamicD)\
**Post date:** [May 5, 2018, 2:23am UTC](https://forums.suse.com/t/rancher-ingress-controller-haproxy-or-nginx/10248/3 "2018-05-05T02:23:23Z")

</div>

That’s … unfortunate, mostly because Nginx is a web proxy, not a load balancer unless you pay for the “plus” version making it a terrible choice, defacto standard or not. Haproxy or even something like traefic will at least grant real load balancing and metrics.

I guess the silver lining is the more I leverage Google/Azure/AWS managed services the less this matters as they all integrate tightly with their own LB solutions. I imagine I could even deploy the main rancher container onto those services and just avoid that inefficiency all together.

---

<div class="post-metadata">

**Author:** ![StoneFury](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/stonefury/32/3909_2.png) [@StoneFury](https://forums.suse.com/u/StoneFury)\
**Post date:** [May 5, 2018, 3:39am UTC](https://forums.suse.com/t/rancher-ingress-controller-haproxy-or-nginx/10248/4 "2018-05-05T03:39:53Z")

</div>

Have you deployed an AWS load balancing using Rancher? Is it required to use the ELB support in the community repo? I can’t seem to get my community repo to load into Rancher yet.

---

<div class="post-metadata">

**Author:** ![courcelm](https://avatars.discourse-cdn.com/v4/letter/c/a8b319/32.png) [@courcelm](https://forums.suse.com/u/courcelm)\
**Post date:** [May 8, 2018, 12:32pm UTC](https://forums.suse.com/t/rancher-ingress-controller-haproxy-or-nginx/10248/5 "2018-05-08T12:32:19Z")

</div>

Hello,  
I tried Rancher 2.0 last week and I am also missing the HAProxy from Rancher 1.

I often did routing like this:

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/f/fb1f2094cb668319f6b75dd3fbd3acef6583aa5e.png)

I didn’t figure out how to do this in Rancher 2.0. Right now this is a blocker for me to adopt Rancher 2.0.
