Keep in mind that ExternalName makes TLS more complicated. If you can get
past that, it should empower this sort of soft link. Manually managed
services also exist, if you have an IP for the target, rather than a name.
On Oct 11, 2016 8:25 AM, "Rodrigo Campos" wrote:
> Oh external Name is alrea
Oh external Name is already in? Awesome! :-)
On Tuesday, October 11, 2016, Matthias Rampke wrote:
> I want something like this too, for the following use case:
>
> We create one namespace for each system (a collection of components) and
> environment (staging/production/green/blue). Now, the mea
I want something like this too, for the following use case:
We create one namespace for each system (a collection of components) and
environment (staging/production/green/blue). Now, the meaning of
environment is specific to the system. Some systems create new ephemeral
environments for each branc
I agree that the intention isn't exactly clear, but I can throw out some
options. You could set up an ExternalName service in A, which produces a
CNAME in DNS. You could set up a proxy pod and Service which would do more
than DNS.
On Oct 11, 2016 7:00 AM, "Rodrigo Campos" wrote:
I don't see th
I don't see the gain, really. It seems complicated with no good reason.
But sure, create a service in ns A named like the service in B you want to
access (or whatever) and make a pod that proxies the service. If it's http,
you can use nginx or something like that.
But why do you want that? Are yo
I am looking for a pod in namespace A to access a service in namespace B
via a service in namespace A which proxies the request (so only the proxy
service needs to know about namespace B etc)
Is this possible?
On Monday, October 10, 2016 at 6:33:44 PM UTC+1, Daniel Smith wrote:
> I think the re
I think the request is for e.g. a version of Ingress that runs within
namespace A and exposes services running in namespace B under new DNS
names. Or auto-populated headless services.
On Mon, Oct 10, 2016 at 8:23 AM, 'Tim Hockin' via Kubernetes user
discussion and Q&A wrote:
> Pods should be abl
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 wrote:
> Hi,
> I have been looking at ways to have pods and services communicate with each
> other when they are in different namespaces. Is
