<p><strong>what i know / have running</strong>:
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). </p>

<p><strong>my question</strong>:
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: <a href="https://rancher-things.local" rel="nofollow noreferrer">https://rancher-things.local</a>)? like have external (local network, not public) if I would deploy maybe a harbor registry and can somehow expose it like <a href="https://rancherthings.local/harbor" rel="nofollow noreferrer">https://rancherthings.local/harbor</a>? 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?</p>

<p>thank you. </p>

Patrick Hermann
<p>There should be ingress resource already which exposes the rancher ui. You can edit the ingress and add a path <code>/harbor</code> to route the traffic to service for harbor.</p>

<pre><code>  paths:
  - path: /harbor
    backend:
      serviceName: harbor
      servicePort: 80
</code></pre>
