Hello Team, Regarding Nginx Ingress Controller: Scenario, we have both QA and U . . .

Arul Raj:
Hello Team,
Regarding Nginx Ingress Controller: Scenario, we have both QA and UAT site hosted on same K8S Cluster in different namespace . Need to have couples of path routed hence we will have a Ingress rules on each namespace. Do we need two ingress controller on each namespace or it can be handled by one as daemon set or just one deployment (with Host name parameter added) ?
What will be the best solution here ? kindly share your thoughts!

Mariusz Gomse:
hello :slightly_smiling_face:

According to my experience it works this way:
• ingress controller is a deployment (e.g. 3 replicas) in default namespace (but can be also in some other)
• in qa and uat namespaces there are Ingress objects which have all needed data (information about host, path etc.)
Ingress controllers deployment is reading data from Ingress objects (from all namespaces) and is able to route the traffic correctly

PS: Usuallly I’ve got also a monitoring namespace additionaly and new Ingress objects ther

Arul Raj:
sounds like a plan, let try this approach

Arul Raj:
Thanks!