Add EBS gp3 support

[samjo-nyang]

Is this a bug fix or adding new feature?
Adding new feature

What is this PR about? / Why do we need it?
Support a new volume type gp3 (https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ebs-general-purpose-volumes-gp3/)

What testing is done?

• make succeeded
• make sanity-test succeeded
• manual gp3 pvc testing (with my internal EKS cluster) succeeded

implements #628

However, docker run -v "$PWD":/go -it golang:1.14.1-buster make test triggers a lot of dependency update. Is this expected and should be in this PR? How can I update aws-sdk only?

[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: [email protected]

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 @samjo-nyang!

It looks like this is your first PR to kubernetes-sigs/aws-ebs-csi-driver 🎉. 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-sigs/aws-ebs-csi-driver 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 @samjo-nyang. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

[samjo-nyang]

I signed it

[coveralls]

Pull Request Test Coverage Report for Build 1333

• 22 of 22 (100.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.5%) to 81.713%

---

Totals
Change from base Build 1331:	0.5%
Covered Lines:	1622
Relevant Lines:	1985

---

💛 - Coveralls

[ayberk]

This is great, thank you!

[ayberk]

Again, great work. Thank you!

We should probably change the default type to gp3 as it's cheaper and faster. What do you think @wongma7?

[wongma7]

/ok-to-test

IMO we can make gp3 the default if we release the change in a new minor version, by default the performance is equal or better, only throughput is a bit more complicated since for gp2 it might involve "burst credits" but I don't think we need to worry about it. Also there are volume type specific service quotas, so for example if a user has increased their gp2 TiB quota, they must remember to increase their gp3 one as well, but again I don't think this is worth worrying about just somethin to note.

[samjo-nyang]

I think that all feedback are applied and all tests are passed.

• change default volume type to gp3
• add a new option "iops"
• fix readme.md

@ayberk @wongma7 @Jan-M
Is there anything left to do?

[ayberk]

Thank you @samjo-nyang! /lgtm, but let's wait for one more review.

One minor request, can you squash your commits? Ideally we should have one commit for updating the SDK and another one for gp3 support, but you can simply squash into one.

[wongma7]

/lgtm
/approve
thank you, we will make a release shortly!!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: samjo-nyang, wongma7

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:

• OWNERS [wongma7]

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