Service Discovery/DNS resolution of un-linked Services

I’m using Rancher 0.56.1 and Alpine based images with DnsMasq (https://github.com/janeczku/docker-alpine-kubernetes).

When I ssh into a running container, I find that I can ping my linked services, but I can’t seem to ping any services that are not linked, whether they are within my stack or in another stack. This is the expected behaviour?

In the current version of Rancher, you should be able to ping containers in the same stack even if it’s not linked, but if it’s in another stack, you cannot ping them right now.

There is this enhancement to get it working for cross stack.

1 Like