Add terminationGracePeriodSeconds as a helm parameter

[ElijahQuinones]

Is this a bug fix or adding new feature?

This is adding a new feature.

What is this PR about? / Why do we need it?

This PR gives the customer the ability to change their EBS CSI Node Pod termination grace period.

What testing is done?

I ran helm locally on my dev cluster with a

--set node.terminationGracePeriodSeconds=34

and with no terminationGracePeriodSecounds parameter and could see that with no parameter terminationGracePeriodSecounds was set to 30 on my pods and with the
--set node.terminationGracePeriodSeconds=34 i could see that terminationGracePeriodSeconds on my pod was 34 seconds

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: ElijahQuinones (28cb3c2, cc0773a, 92c1f9f, 866c546)

[k8s-ci-robot]

Welcome @ElijahQuinones!

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

[AndrewSirenko]

/ok-to-test

[AndrewSirenko]

Looks like our PR template was overridden for some reason. Would you change your PR description to answer the following questions?

Is this a bug fix or adding new feature?

What is this PR about? / Why do we need it?

What testing is done?

As well as show evidence that this change worked underneath the what testing is done section.

Thank you and congrats on submitting your first PR to our repo!

[ElijahQuinones]

Looks like our PR template was overridden for some reason. Would you change your PR description to answer the following questions?

Is this a bug fix or adding new feature?

What is this PR about? / Why do we need it?

What testing is done?

As well as show evidence that this change worked underneath the what testing is done section.

Thank you and congrats on submitting your first PR to our repo!

Will do

[torredil]

Running make update will auto-generate the updated Kustomize files and fix the pull-aws-ebs-csi-driver-verify job.

Tip: I find running the following makefile targets to be quite helpful before publishing a PR to catch these errors in advance:

make update && make verify && make test

[ConnorJC3]

Need to run make update like Eddie said, otherwise lgtm
/label tide/merge-method-squash
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ConnorJC3

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 [ConnorJC3]

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

[github-actions]

Code Coverage Diff

This PR does not change the code coverage

[AndrewSirenko]

/lgtm