feat: use annotation to filter AWS LB target nodes

[foobarfran]

What type of PR is this?
/kind feature
/area provider/aws

What this PR does / why we need it:
This pull request allows to target specific nodes in AWS LoadBalancer Services, using an annotation to specify a comma separated list of key=values, used to match node labels.
A common scenario is to use pod affinity to target specific nodes, this PR allows to extend that behaviour to the service level having the following improvements:

• Keep traffic in the instances that can answer requests
• When we use externalTrafficPolicy: Local in our service, we get rid of the Unhealthy ec2 instances in the aws target groups for those nodes that doesn't have any pods for the service, improving the TG monitoring simplicity
• For large clusters, we prevent to rapidly reach the target limit in the target group, specially if the service exposes multiple ports.

Which issue(s) this PR fixes:
Fixes (kubernetes/cloud-provider-aws#58)

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Added service.beta.kubernetes.io/aws-load-balancer-target-node-labels annotation to target nodes in AWS LoadBalancer Services

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

@foobarfran: The label(s) area/ cannot be applied, because the repository doesn't have them

In response to this:

What type of PR is this?
/kind feature
/area provider/aws

What this PR does / why we need it:
This pull request allows to target specific nodes in AWS LoadBalancer Services, using an annotation to specify a comma separated list of key=values, used to match node labels.
A common scenario is to use pod affinity to target specific nodes, this PR allows to extend that behaviour to the service level having the following improvements:

• Keep traffic in the instances that can answer requests
• When we use externalTrafficPolicy: Local in our service, we get rid of the Unhealthy ec2 instances in the aws target groups for those nodes that doesn't have any pods for the service, improving the TG monitoring simplicity
• For large clusters, we prevent to rapidly reach the target limit in the target group, specially if the service exposes multiple ports.

Which issue(s) this PR fixes:
Fixes (kubernetes/cloud-provider-aws#58)

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Added service.beta.kubernetes.io/aws-load-balancer-target-node-labels annotation to target nodes in AWS LoadBalancer Services

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @foobarfran!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @foobarfran. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[foobarfran]

/cc @M00nF1sh

[M00nF1sh]

/ok-to-test
/lgtm

[foobarfran]

/retest

[M00nF1sh]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: foobarfran, M00nF1sh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• staging/src/k8s.io/legacy-cloud-providers/aws/OWNERS [M00nF1sh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[foobarfran]

/retest

[foobarfran]

/retest

[foobarfran]

/retest

[foobarfran]

/retest

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[foobarfran]

/retest

[foobarfran]

/retest

[foobarfran]

/retest