Answers: <p>I would suggest at least one for production and one for npe.  The nginx-ingress helm chart appears to only support setting a scope to all namespaces or just one namespace (a frustrating limitation not in other ingress controller options):</p>
  
  <p><a href="https://github.com/helm/charts/tree/master/stable/nginx-ingress" rel="nofollow noreferrer">https://github.com/helm/charts/tree/master/stable/nginx-ingress</a></p>
  
  <p><code>controller.scope.namespace</code></p>
  
Answers: CC BY-SA 4.0
Answers: 2019-09-30T13:39:17.520Z
Answers: Or simply don't use helm, it's really simple to deploy ingress-nginx without it.
Answers: Gothrek
Answers: CC BY-SA 4.0
Answers: 2019-09-24T14:04:09.690Z
Answers: 2019-09-24T14:04:09.690Z
Answers: erk
Body: <p>I have a kubernetes cluster in Azure. In this i have three namespaces:</p>
  
  <ol>
  <li>development</li>
  <li>staging</li>
  <li>production</li>
  </ol>
  
  <p>I have installed nginx ingress controller into its own namespace, ingress-nginx. I am kind of new to the ingress part, and I cant seem to find anywhere any advice if I should have a controller pr namespace, or share one controller with all.</p>
  
  <p>Should I have one that is shared or install one pr. namespace? What is the pattern here?</p>
  
Tags: <kubernetes><nginx><ingress>
Title: Kubernetes nginx ingress controller - one pr. environment?
UserDisplayName: mslot
ThreadText: # Kubernetes nginx ingress controller - one pr. environment?
  
  (Asked by: username_0 on 2019-09-22)
  
  I have a kubernetes cluster in Azure. In this i have three namespaces:
  
  1. development
  2. staging
  3. production
  
  I have installed nginx ingress controller into its own namespace, ingress-nginx. I am kind of new to the ingress part, and I cant seem to find anywhere any advice if I should have a controller pr namespace, or share one controller with all.
  
  Should I have one that is shared or install one pr. namespace? What is the pattern here?
  
  **Tags:** kubernetes, nginx, ingress
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-09-24. Score: 2
  
  I would suggest at least one for production and one for npe. The nginx-ingress helm chart appears to only support setting a scope to all namespaces or just one namespace (a frustrating limitation not in other ingress controller options):
  
  <https://github.com/helm/charts/tree/master/stable/nginx-ingress>
  
  `controller.scope.namespace`
  
  > **Comments:**
  > **username_2**: Or simply don't use helm, it's really simple to deploy ingress-nginx without it.  
  
  ---
  
  