title: What is the max number of ingress objects that can be created in nginx-ingress for kubernetes
body: <p>We have a multi tenant application and for each tenant we provision separate container image.
  Likewise we create a subdomain for each tenant which will be redirected to its own container.
  There might be a scenario where 1000s of tenants can exist and its dynamic.</p>
  <p>So it has become necessary for us to consider the limitations in ingress controllers for Kubernetes in general before choosing. Especially the nginx-ingress.</p>
  <ol>
  <li><p>Is there any max limitation on number of Ingress resources or rules inside ingress that can be created? Or will there be any performance or scaling issues when too many ingress resources are created ?</p>
  </li>
  <li><p>Is it better to add a new rule(for each subdomain) in same ingress resource or to create separate ingress resource for each subdomain ?</p>
  </li>
  </ol>