# Ingress Type Load Balancing?

**URL:** <https://discuss.hashicorp.com/t/ingress-type-load-balancing/2366>\
**Category:** Nomad\
**Created:** [August 13, 2019, 8:48pm UTC](https://discuss.hashicorp.com/t/ingress-type-load-balancing/2366 "2019-08-13T20:48:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![greaterfool](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/greaterfool/32/1823_2.png) [@greaterfool](https://discuss.hashicorp.com/u/greaterfool)\
**Post date:** [August 13, 2019, 8:48pm UTC](https://discuss.hashicorp.com/t/ingress-type-load-balancing/2366/1 "2019-08-13T20:48:13Z")

</div>

Hi there, I’m trying to get setup so I can have various services, that if a node or task should fail, will fail over to the new task that will spin up in response to that failure.

ie: [task.host.com](http://task.host.com) would always point to X service, regardless of a node or task failing.

I’m not sure how I should approach this. I’m currently working with a small cluster of nodes which have both Nomad and Consul installed on them.

---

<div class="post-metadata">

**Author:** ![spuder](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/spuder/32/1638_2.png) [@spuder](https://discuss.hashicorp.com/u/spuder)\
**Post date:** [August 13, 2019, 9:02pm UTC](https://discuss.hashicorp.com/t/ingress-type-load-balancing/2366/2 "2019-08-13T21:02:49Z")

</div>

Could you elaborate? Consul should take care of the service discovery for you.

If you have a service `foo`, then all other services can resolve it at `foo.service.consul`. Consul services are load balanced, so you can and should have multiple instances of `foo`.

---

<div class="post-metadata">

**Author:** ![greaterfool](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/greaterfool/32/1823_2.png) [@greaterfool](https://discuss.hashicorp.com/u/greaterfool)\
**Post date:** [August 13, 2019, 9:21pm UTC](https://discuss.hashicorp.com/t/ingress-type-load-balancing/2366/3 "2019-08-13T21:21:00Z")

</div>

Ahh, I mean externally. For example, if I wanted to run a Salt master as a task in Nomad, I’d need an external endpoint for the minions to connect to. Or for example an Nginx server, or any other kind of server that would need to be accessed externally at one consistent location.

---

<div class="post-metadata">

**Author:** ![spuder](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/spuder/32/1638_2.png) [@spuder](https://discuss.hashicorp.com/u/spuder)\
**Post date:** [August 13, 2019, 9:40pm UTC](https://discuss.hashicorp.com/t/ingress-type-load-balancing/2366/4 "2019-08-13T21:40:42Z")

</div>

Couple options

1. If the minions have consul installed, they can automatically connect to `salt.service.consul`
2. If the minions don’t have consul installed, but they do have a shared dns server, you can install consul on your dns server, and then create a new zone for the .consul domain. That way any server in your network could automatically resolve salt.service.consul
3. Fabio or Load balancer - You could point all the minions at a load balancer that has consul installed, or use fabio as a router.