<p>I assume you've created your nginx ingress controller in it's own namespace? By default it's called <code>ingress-nginx</code>.</p>

<p>You can create your second Nginx Ingress controller in a seperate namespace so that it's logically isolated from your first. You'll need to give it a different name, but I see no reason why you can't do that.</p>

<p>Doing so will spin up a seperate AWS ELB, which you can then map to your new DNS record and then you can slowly migrate your services over.</p>

CC BY-SA 4.0
2018-09-18T20:23:47.477Z
Great, thanks, didn't know I could do that. I'll give it a try and update on that.
Jonathan Perry
CC BY-SA 4.0
2018-09-17T19:18:41.000Z
2018-09-17T19:18:41.000Z
Caledonia91
<p>We currently have at our company a Kubernetes cluster with an ingress controller that manages the traffic of the services and their endpoints.</p>

<p>We want to change our URL gradually, first add the new URL to point to the same services that are currently being used by the old URL, and once we see that everything works fine, we'll just make the old URL redirect to the new one.</p>

<p>That's the plan in a gist, however, I have no idea where to start. Do I add another ingress controller that is just copied from the one we currently have and update the SSL certificate to match the new URL?</p>

<p>Thanks!</p>

CC BY-SA 4.0
2018-09-16T21:51:17.743Z
What kind of Ingress Controller (Nginx?) are you using and in what cloud environment?
Caledonia91
CC BY-SA 4.0
2018-09-17T09:43:25.790Z
I use nginx, with AWS
Jonathan Perry
<kubernetes><ingress>
Multiple Ingress controllers in Kubernetes
Jonathan Perry
# Multiple Ingress controllers in Kubernetes

(Asked by: username_0 on 2018-09-16)

We currently have at our company a Kubernetes cluster with an ingress controller that manages the traffic of the services and their endpoints.

We want to change our URL gradually, first add the new URL to point to the same services that are currently being used by the old URL, and once we see that everything works fine, we'll just make the old URL redirect to the new one.

That's the plan in a gist, however, I have no idea where to start. Do I add another ingress controller that is just copied from the one we currently have and update the SSL certificate to match the new URL?

Thanks!

**Tags:** kubernetes, ingress

> **Comments:**
> **username_1**: What kind of Ingress Controller (Nginx?) are you using and in what cloud environment?  
> **username_0**: I use nginx, with AWS  

---

## 1 answers

### Answer by username_1 on 2018-09-17. Score: 1

I assume you've created your nginx ingress controller in it's own namespace? By default it's called `ingress-nginx`.

You can create your second Nginx Ingress controller in a seperate namespace so that it's logically isolated from your first. You'll need to give it a different name, but I see no reason why you can't do that.

Doing so will spin up a seperate AWS ELB, which you can then map to your new DNS record and then you can slowly migrate your services over.

> **Comments:**
> **username_0**: Great, thanks, didn't know I could do that. I'll give it a try and update on that.  

---

