Pods should be able to communicate across namespaces by default. Can you clarify what you tried that isn't working?
On Mon, Oct 10, 2016 at 3:33 AM, Jo Ho <johnandrewhor...@gmail.com> wrote: > Hi, > I have been looking at ways to have pods and services communicate with each > other when they are in different namespaces. Is there an official way of > doing this? I have looked at setting up services and external routes, but my > preference is to minimise "knowledge leak" from the namespaces i.e. to not > have to have the requirement for the orginating pod to have to have > knowledge of the endpoint service (that is to say, it would be good to have > the equest to be transparent) > Is this possible or does the orginating pod have to specify the fqdn of the > service in the other namespace? is there a way of proxying the request so > the originating pod can talk to the proxy and the proxy deals with the > communication to the other service in the other namespace? > 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, 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.
