You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tried to access the registry k3d-registry.localhost:12345 from a pod in the k3d cluster
$ kubectl run -i --rm --tty busybox --image=busybox --restart=Never -- sh
/ # wget -qO- http://k3d-registry.localhost:12345/v2/_catalog
wget: can't connect to remote host (172.19.0.2): Connection refused
What did you expect to happen
Since registry is exposed on :12345, and k3d injects this domain in coredns' NodeHosts, http://k3d-registry.localhost:12345/ should be accessible from within the cluster. Instead k3d-registry.localhost:5000 is accessible. I don't want to use host.k3d.internal:12345 as it requires us to tweak the domains at application layer, which isn't ideal.
If we map k3d-registry.localhost to host system's IP (like we do for host.k3d.internal), instead of the registry IP, then the above works as expected.
What did you do
How was the cluster created?
What did you do afterwards?
Tried to access the registry
k3d-registry.localhost:12345
from a pod in the k3d clusterWhat did you expect to happen
Since registry is exposed on
:12345
, and k3d injects this domain in coredns' NodeHosts,http://k3d-registry.localhost:12345/
should be accessible from within the cluster. Insteadk3d-registry.localhost:5000
is accessible. I don't want to usehost.k3d.internal:12345
as it requires us to tweak the domains at application layer, which isn't ideal.If we map
k3d-registry.localhost
to host system's IP (like we do for host.k3d.internal), instead of the registry IP, then the above works as expected.Screenshots or terminal output
Which OS & Architecture
Debian on WSL2
Which version of
k3d
k3d version v5.6.0
k3s version v1.27.4-k3s1 (default)
Which version of docker
The text was updated successfully, but these errors were encountered: