feat: Add ALPN policy annotation for NLB TLS listeners

[alimx07]

What type of PR is this?
/kind feature

What this PR does / why we need it:
Adds service.beta.kubernetes.io/aws-load-balancer-alpn-policy annotation to configure the ALPN policy on NLB TLS listeners. Valid values are HTTP1Only, HTTP2Only, HTTP2Optional, HTTP2Preferred, and None. Applied only when aws-load-balancer-ssl-cert is also set. Removing the annotation from an existing service explicitly resets the listener to None.

Which issue(s) this PR fixes:
Fixes #1309

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Add `service.beta.kubernetes.io/aws-load-balancer-alpn-policy` annotation to configure the ALPN policy on NLB TLS listeners. Valid values: `HTTP1Only`, `HTTP2Only`, `HTTP2Optional`, `HTTP2Preferred`, `None`. Requires `aws-load-balancer-ssl-cert` to be set.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign bridgetkromhout for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

Welcome @alimx07!

It looks like this is your first PR to kubernetes/cloud-provider-aws 🎉. 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/cloud-provider-aws 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 @alimx07. 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.

Details

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-sigs/prow repository.

[alimx07]

/kind feature

[alimx07]

/cc @kmala

[kmala]

Since the listener supports multiple ALPN policies, we should also support multiple i think?

[alimx07]

Hi @kmala , While that sounds reasonable, the AWS SDK actually only allows one ALPN policy per listener as they state here. So I though of keeping it as single string for simplicity. Ofc, keeping it slice with one string will do the job also.

[kmala]

interesting that its a list but only single value is supported.

[alimx07]

Hi @kmala, If you have time, could you look at this again. Thanks in advance!

[kmala]

/ok-to-test

[kmala]

/triage accepted

[kmala]

/lgtm