Inversion of Control for Load Balancer routes

Currently it, the only way to configure the L4/L7 routing for a loadbalancer is through the use of labels on the load balancer container (
I’m even having difficulty finding these exact settings in the API itself.

I’m wondering if any has thought about inverting this and allowing services to declare their attachment to a specific load balancer. I realize that this then introduces some issues around merging rules and such, but I just wanted to bring it up.

Or would this be something better left to another service that could continuously watch services in Rancher and update the LB accordingly?

There are selector links that may be what you are trying to achieve, but we are currently missing L7 support for selector links.