Fix dropped namespace in url parsing

[leth]

Causes problems if you try and connect from one namespace to another.

[tomwilkie]

How so? These addresses are interpreted by kuberesolver as a k8s service name here: https://github.com/sercand/kuberesolver/blob/v1.0.0/balancer.go#L46

By putting a dot in there, you're telling kuberesolver to pick a port name I think... which does leave the question how the port number syntax ever worked.

[leth]

How so?

Connecting to foo.bar.svc.cluster.local results in a connection to foo + the current namespace, this works if your current namespace is also bar, but not otherwise.

I was seeing a there is no address available error from GRPC.

By putting a dot in there, you're telling kuberesolver to pick a port name I think... which does leave the question how the port number syntax ever worked.

I think you mixed up . and :?

[bboreham]

Empirically, we omit .svc.cluster.local when using this feature and connect to querier.cortex:9095 or whatever.

[leth]

🤷‍♂️ I worked around this issue by not using the loadbalancer.

I only hit this issue because in factoring out some common code I accidentally added the loadbalancer to places we weren't using one before.