feat: Add ability to configure emptyDir params (sizeLimit, mediium)

[mkilchhofer]

Is this a bug fix or adding new feature?

It adds a new feature

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

We use both the EBS and the EFS CSI drivers. The EBS driver offers this capability already:

• fix: Add parameters for tuning revisionHistoryLimit and emptyDir volumes aws-ebs-csi-driver#1840
• kubernetes-sigs/aws-ebs-csi-driver@3cc74df#diff-38890fc178a6bb362418969605e8650e75296dedaf1eef29dc3b21400ff36676L220

What testing is done?

$ helm template aws-efs-csi-driver .
(..)
          securityContext:
            allowPrivilegeEscalation: false
            readOnlyRootFilesystem: true
      volumes:
        - name: socket-dir
          emptyDir: {}     # <-- see here
---
# Source: aws-efs-csi-driver/templates/csidriver.yaml
apiVersion: storage.k8s.io/v1
(..)

And with customized emptyDir:

$ helm template aws-efs-csi-driver . --set controller.socketDirVolume.emptyDir.sizeLimit=100Mi
(..)
          securityContext:
            allowPrivilegeEscalation: false
            readOnlyRootFilesystem: true
      volumes:
        - name: socket-dir
          emptyDir:           # <-- see here
            sizeLimit: 100Mi  # 
---
# Source: aws-efs-csi-driver/templates/csidriver.yaml
apiVersion: storage.k8s.io/v1
(..)

[k8s-ci-robot]

Welcome @mkilchhofer!

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 @mkilchhofer. Thanks for your PR.

I'm waiting for a github.com 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.

[mkilchhofer]

Friendly reminder @dankova22 and @wongma7

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mbevc1, mkilchhofer
Once this PR has been reviewed and has the lgtm label, please assign wongma7 for approval. For more information see the 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