FWIW, we're running an nginx ingress controller on GKE (kube-system
namespace), and use annotations to target some ingress objects to that
controller (from multiple namespaces), exposing just the ingress controller
service.
In our use-case, we expose the ingress controller service using
LoadBalance
The way the GCP Ingress controller is implemented is one IP per
Ingress, and Ingress is always single-namespace (for now). You could
do something like have a Service in your namespace that redirects to a
service in a different namespace, maybe, but I have never tried that.
On Tue, Oct 17, 2017 at
Hi Tim,
Thanks for the response.
We are now left the solution of creating two separate ingress resources for
two namespaces.
So do you suggest some different solution or we must continue with the same?
Thanks.
On Thu, Oct 12, 2017 at 9:38 PM, 'Tim Hockin' via Kubernetes user
discussion and Q&A w
Currently it is not possible to express this.
On Thu, Oct 12, 2017 at 12:21 AM, wrote:
> Hi,
>
> I have two applications deployed in different namespace in Google Kontainer
> engine(GKE). I want to use a single ingress resource (Google Load Balancer)
> to point to both the application using pa
Hi,
I have two applications deployed in different namespace in Google Kontainer
engine(GKE). I want to use a single ingress resource (Google Load Balancer) to
point to both the application using path based routing. Is it possible to have
backend kubernetes services in multiple namespace behind
