This message was deleted.

@wide-garage-9465 any tips?

did you try host.k3d.internal ?

yeah but my container is not part of kube cluster

you may need to attach that container to docker network.

I am also trying

host.docker.internal

• i usually run a docker registry and a k3d cluster alongside • if my k3d cluster name is

test

and registry is

registry.localhost

I'd simply run

docker network connect k3d-test registry.localhost

thanks @big-librarian-12753 I am trying the same now

@polite-engineer-55788 you mean nodePort maybe? To reach a service inside the cluster from outside the cluster? Should work exactly like that, via <k3d-node-container-name>:<nodePort> or <k3d-node-container-ip>:<nodePort> 🤔 The other way around works just as well as @big-librarian-12753 showed already

yeah that works @wide-garage-9465 , for better clarity i tried using

host.docker.internal:<nodePort>

so it works with any number of agents/server 😄

Yup if the ports are forwarded, that's convenient 👍