TCP Custom Resource Port Collision Detection Should Consider Ingress Class

[clark1013]

Currently, the TCP Custom Resource collision detection logic does not properly consider ingress classes when checking for address:port conflicts. This prevents multiple ingress controllers with different ingress classes from using the same ports, which is a valid and necessary configuration in multi-tenant environments.
I have drafted a patch to fix this issue. clark1013/kubernetes-ingress@v3.1.6...clark1013:kubernetes-ingress:v3.1.6-patch. Please take a look. Thanks

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.