Well, binding to 127 addresses means nobody else can access you. Binding to a specific IP is just not the "normal" thing to do in network programming, in my experience. Unless you know something specific, 0 is the best option. E.g. you might have more than one network interface, and 0 is the only way to catch them all without enumerating them.
On Fri, Dec 15, 2017 at 4:56 PM, <dietrich.schu...@lightbend.com> wrote: > 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 more about this... > > -- > 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, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. -- 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, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
