Version

3.6.1

What Kubernetes platforms are you running on?

Rancher

Steps to reproduce

Step 1: Deploy Default Nginx-Ingress
Deploy the default nginx-ingress controller with the default ingressClass set to nginx.

Step 2: Deploy Namespace-Specific Nginx-Ingress
Deploy a namespace-specific nginx-ingress controller with the ingressClass set to nginx-team-c.

Step 3: Create VirtualServer Resources
Create three VirtualServer resources with the following configurations:

• VirtualServer A: No ingressClassName specified.
• VirtualServer B: ingressClassName set to nginx.
• VirtualServer C: ingressClassName set to nginx-team-c.

Expected Behavior
The expected behavior is that
- VirtualServer A and B are handled by the default nginx ingress controller,
- VirtualServer C is handled by the nginx-team-c ingress controller.

Observed Behavior
However, it has been observed that VirtualServer A is being handled by both the nginx and nginx-team-c ingress controllers, which is not the expected behavior.

If VirtualServer A includes some customized configurations that depend on third-party plugin (for example include a GeoIP file) only integrated with nginx-team-c and the ingressClassName was missed by somebody, then the current behavior will break the default nginx ingress.