Description of problem: Creating a AWS NLB through openshift-ingress-operator creates AWS LB Target groups with all Nodes

Version-Release number of selected component (if applicable): 4.14

How reproducible:

• create a ROSA cluster
• optional: create an additional MachinePool
• create an additional NLB ingressController according to docs, using a nodeSelector and appropriate tolerations

Actual results:

• an ingresscontroller is created, spawning new router pods
• on AWS side a new NLB is created
• this new NLB has 2 Target Groups for http/https traffic
• However, all OCP nodes are in this Target Group

Expected results:

• only the Nodes specified in the nodeSelector should be in the target group
• as an alternative, it should be possible to set an existing Security Group when creating an ingresscontroller -> NLB

Additional info:

• I assume the latter could be possible with AWSNetworkLoadBalancerParameters , however there is no documentation or code comment of what this should look like