How to access Rancher when k3s is installed with --no-deploy=servicelb

Trying to set up k3s with MetalLB as load balancer, with the goal of providing external access to k3s hosted apps.

I’d also like to use Rancher to admin the k3s cluster.

So, I install k3s with the --no-deploy=servicelb option, then proceed with Rancher installation as per Rancher docs (using Helm).
Problem is that I can’t get the Rancher UI to show, even after exposing it using `kubectl expose …``

MetalLB as such works just fine, I can expose a test workload using kubectl expose deployment... and things work as expected. I just cannot get things working with the Rancher UI…

Any pointers to using Rancher with k3s and MetalLB?