Accessing containers - --reverse-proxy / --inspector about kubedock HOT 2 CLOSED

I guess this is why the recommendation is that kubedock runs as a sidecar...

from kubedock.

So I guess my question is, what is the expected use case for the --inspector flag? Is there some way I can get testcontainers to provide me with the container's service name rather than the kubedock service name?

In some cases there is no port exposed when starting the container. In that case kubedock doesn't expose ports either. The --inspector flag will query the registry for that specific image to see if there were any default ports exposed via the image itself. If so, it will reverse-proxy/port-forward these ports as well. This will increase compatibility, but note that the occasions where this is required are rare (and can be worked around by exposing them in the test itself).

from kubedock.