LB instances not coming up on EKS

[prabalsharma]

Describe the bug
On EKS LB instances for kubecf-router-public = 0/3, kubecf-ssh-proxy-public=3/3 and kubecf-tcp-router-public=0/3
This looks similar to the issue we had with scf on EKS
https://documentation.suse.com/suse-cap/1.5.1/html/cap-guides/cha-cap-depl-eks.html#sec-cap-install-scf-eks

Before traffic is routed to EKS load balancers, health checks are performed on them. These health checks require access to ports on the tcp-router service, which are only opened by request via cf map-route and other associated commands.
Use kubectl patch to patch the tcp-router service to expose a port to the EKS load balancer so the health checks can be completed.

https://github.com/SUSE/cloudfoundry/wiki/Load-balancers-in-AWS-EKS#aws-eks-specific-issue-with-scfuaa-deployment-and-solution

To Reproduce
Deploy kubecf on EKS. Check LBs on EKS UI

Expected behavior
Post kubecf deployment check instances of LBs on AWS. All instances won't come up

Environment

• cf-operator-v0.4.2-201.gc4ad274e.tgz
• kubecf-3.0.0-1f48733.tgz

[prabalsharma]

just to be clear, this is a CAP2 blocker

[f0rmiga]

Will be fixed by #300 and #301.

[f0rmiga]

Fixed on 58399a3 and f82059d.