Create ingress controller in namespace Kubernetes

2
votes

I am learning a bit about ingress. It consists of 2 parts:

  • Ingress resource: "How do you want to route requests to the backing services?"
  • Ingress controller: "Listens to Kubernetes API for Ingress resources."

I've deployed an ingress controller in namespace called ingress. I've also deployed a default backend. Now I want to deploy an application (svc, deployment of pods etc).

Do I need to deploy this application also in the namespace ingress? It seems logical to me I have to deploy a new ingress resource for every new application, but how is this working for the Ingress controller?

Do I have to create one ingress controller for every namespace or is it recommended to use on ingress controller over multiple namespaces?

1
namespaceskuberneteskubernetes-ingress

1 Answers

7
votes

The ingress resource must be in the same namespace as the backend service. This can be any namespace doesn't need to be the same as the controller