Makes sense. Thanks.
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group,
Thanks for your reply.
Not port-forwarding from inside. Just from host (using minikube). I happened to
write an app that binds to 127.0.0.1 and stumbled on this behavior
(inconsistency?) Is there somewhere you could point me to that talks about 0
being the normal way to go? Just trying to learn
Just started exploring kubernetes, and ran into this. Haven't found any
docs or clear statements of best practice. The only thing I found was this
note in the container.v1 spec describing the port field:
Any port which is listening on the default "0.0.0.0" address inside a
> container will be a
