What determines of a service under "Service Discovery" gets a clickable link?

I’m trying to deploy a helm chart (kibana) that I’d like access to through the rancher UI, the same way I can access the Grafana server after installing the Monitoring package from the marketplace.

I’ve been looking through the configs for the different services and pods we have installed in the cluster and I can’t for the life of me figure out how Rancher decides if it’s going to create such a link or not.

To round off a potential XY problem, I’m trying to get an ELK/EFK stack installed on our cluster to collect cluster wide logs and present them through Kibana. All the install documentation and examples I can find have you installing the components and then using kubectl port-forward so you can visit the websites via localhost – which is fine for dev/testing but not for production use. We’re self hosted on VMWare with a single IP metallb providing loadbalancer services.

Thanks in advance for any pointers!

Edit: Meant EFK not ECK.