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

[Adityashar]

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

We have a use-case where we need to scrape metrics from the following containers running in the controller deployment and node daemonset:

1. liveness-prove
2. csi-provisioner
3. csi-driver-registrar

Our requirement is to add / update the arguments passed to these containers.

Describe the solution you'd like in detail A clear and concise description of what you want to happen.

A simple helm templating block to be added in each of the containers and their values made available through the values.yaml file.

Additional context Add any other context or screenshots about the feature request here.

The latest chart of aws-ebs-csi-driver has this implemented and can be used as a starting point. Eg https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/master/charts/aws-ebs-csi-driver/templates/_node.tpl#L152

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale