# Ingress understanding

**URL:** <https://forums.suse.com/t/ingress-understanding/17222>\
**Category:** General\
**Created:** [April 21, 2020, 1:57pm UTC](https://forums.suse.com/t/ingress-understanding/17222 "2020-04-21T13:57:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Patrick\_Hermann](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/patrick_hermann/32/6261_2.png) [@Patrick\_Hermann](https://forums.suse.com/u/Patrick_Hermann)\
**Post date:** [April 21, 2020, 1:57pm UTC](https://forums.suse.com/t/ingress-understanding/17222/1 "2020-04-21T13:57:42Z")

</div>

**what i know / have running** : i got a running rancher ha setup (2.4.2) on vsphere w/ a L4 nginx lb in front of it. access the ui and provision new clusters (vsphere node driver) works great. I know I’m not in the cloud and cannot use a L7 LB (apart from nip.ip or metal lb maybe), and deploying workloads and expose them via nodeport works great (so the workloads are available on the specified port on each node a according pod is running on).

**my question** : is it possible to expose (maybe via ingress) applications on any of my running cluster under the domain/adress I can access the rancher ui (in my case: [https://rancher-things.local](https://rancher-things.local/))? like have external (local network, not public) if I would deploy maybe a harbor registry and can somehow expose it like [https://rancherthings.local/harbor](https://rancherthings.local/harbor)? or if this would not work is it possible to deploy a L4 load balancer for accessing applications on or in front of a specific cluster?

thank you.

---

<div class="post-metadata">

**Author:** ![moisei](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/moisei/32/4755_2.png) [@moisei](https://forums.suse.com/u/moisei)\
**Post date:** [April 22, 2020, 6:35am UTC](https://forums.suse.com/t/ingress-understanding/17222/2 "2020-04-22T06:35:13Z")

</div>

Rancher ingress controller is capable to do L7.  
You just have to create a record in your DNS. For the test purposes, use /etc/hosts on the machine when you are going to browse your app.
