Make 'aws-efs-csi-driver' helm chart more configurable #1423

[msmohitkumar]

Is this a bug fix or adding new feature?

Feature

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

What testing is done?
"Rendered the Helm chart locally to verify whether the newly templatized values were successfully embedded into the Helm templates."

[linux-foundation-easycla]

• ✅login: msmohitkumar / (8b08df0)
• ✅login: msmohitkumar / (8b08df0, 38a268a)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

Welcome @msmohitkumar!

It looks like this is your first PR to kubernetes-sigs/aws-efs-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-efs-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 @msmohitkumar. 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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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

[msmohitkumar]

/assign @k8s-ci-robot @mortent @Atoms @steved
Could you please review the PR

[k8s-ci-robot]

@msmohitkumar: GitHub didn't allow me to assign the following users: steved.

Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @k8s-ci-robot @mortent @Atoms @steved
Could you please review the PR

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.

[mskanth972]

Hi @msmohitkumar, can you squash the commits to one, I can trigger the tests.