Re: [kubernetes-users] services and namespaces

Part of the point of Services is that you don't have to discover the port - you can use known ports. That said, we also serve SRV records, so if you know the name of the port you want, you can find the number. On Fri, May 12, 2017 at 8:56 AM, wrote: > Back to service

Re: [kubernetes-users] services and namespaces

Back to service reference across namespace, sure the FQDN can be used to point to service in different namspace. I wonder how to find out the service port value. In the same namespace, this can be obtained via the environment value _PORT. Please share thanks -- You received this message

Re: [kubernetes-users] services and namespaces

Sort of, see the services without selectors: https://kubernetes.io/docs/concepts/services-networking/service/#without-selectors On Tue, May 9, 2017 at 10:21 AM 'Ahmet Alp Balkan' via Kubernetes user discussion and Q wrote: > Documentation on DNS records: >

Re: [kubernetes-users] services and namespaces

Documentation on DNS records: https://kubernetes.io/docs/concepts/services- networking/dns-pod-service/ Side-question: is it possible to create a Service that points to pods in namespaces different than the Service itself? On Tue, May 9, 2017 at 12:56 AM, 'David Oppenheimer' via Kubernetes user

Re: [kubernetes-users] services and namespaces

If you have service A in namespace N, then you can reach it from namespace N as "A" and from any namespace as "A.N" On Mon, May 8, 2017 at 8:03 AM, Ashic Mahtab wrote: > What's the relationship between services and namespaces? I'm creating an > ExternalName service

[kubernetes-users] services and namespaces

What's the relationship between services and namespaces? I'm creating an ExternalName service called elasticsearch. If I put it in it's own namespace, an app running in a different namespace can't seem to resolve the service. Is there a way to deploy a service so that all namespaces can access