Exposing services under rancher dns name

I’ve noticed that accessing longhorn for example is done with the following address in my on-prem setup

and I wonder if there’s an option to do the same with other services or if it’s possible as an alternative to expose and app1 and app2 as app1.rancher and app2.rancher for example.


The proxy is generic and you can use for any service; /k8s/clusters/<id> gets you to the k8s API for that cluster, and /api/v1/namespaces/<ns>/services/[scheme:]<service>[:port]/proxy[/path] gets you to the pods that service targets. Access Services Running on Clusters | Kubernetes