Transit runs more than one Ingress controller in the cluster and must ensure a new portal Ingress is handled by the nginx implementation. What should they set?
Select an answer to reveal the explanation.
Short Explanation
When several controllers share a cluster, IngressClass is the name tag that says “this rule set is for nginx,” not the other edge. Point the Ingress at the right class so the right controller claims it.
Full Explanation
IngressClass associates Ingress objects with a particular controller implementation. In multi-controller clusters, setting the correct class prevents the wrong controller from ignoring or mishandling the resource. PriorityClass, topology spread on the Ingress kind, and externalTrafficPolicy renaming do not select Ingress controllers.