feat: Add option to provision StorageClasses

[gazal-k]

Is this a bug fix or adding new feature?
New feature in the helm chart

What is this PR about? / Why do we need it?
Most application charts don't usually create StorageClasses. They create PVCs. This is extending the work done in #274. The chart itself is kind of broken unless image.tag is set to "master". #291 will probably address that.

What testing is done?
Installed the chart with the following custom values:

image:
  tag: "master"

serviceAccount:
  annotations:
    eks.amazonaws.com/role-arn: arn:aws:iam::<accountId>:role/<roleName>

storageClasses:
- name: efs-sc
  mountOptions:
  - tls
  parameters:
    provisioningMode: efs-ap
    fileSystemId: fs-<id>
    directoryPerms: "700"

Then tried creating a PVC and a pod that used it:

---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: efs-claim
spec:
  accessModes:
    - ReadWriteMany
  storageClassName: efs-sc
  resources:
    requests:
      storage: 5Gi
---
apiVersion: v1
kind: Pod
metadata:
  name: efs-app
spec:
  containers:
    - name: app
      image: centos
      command: ["/bin/sh"]
      args: ["-c", "while true; do echo $(date -u) >> /data/out; sleep 5; done"]
      volumeMounts:
        - name: persistent-storage
          mountPath: /data
  volumes:
    - name: persistent-storage
      persistentVolumeClaim:
        claimName: efs-claim

Verified the following:

• PV was provisioned.
• EFS access point was created.
• test pod was writing to EFS as expected.

[k8s-ci-robot]

Hi @gazal-k. 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.

[ayberk]

/ok-to-test

[ayberk]

/lgtm
/approve

[gazal-k]

@gazal-k: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
pull-aws-efs-csi-driver-e2e 4723e9f link /test pull-aws-efs-csi-driver-e2e
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

The test failures in here don't really seem to be related to this change.

[ayberk]

/retest

[wongma7]

/lgtm

fyi @kbasv I'm dropping an lgtm but please review as well

[wongma7]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ayberk, gazal-k, 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

[kbasv]

/lgtm

[k8s-ci-robot]

@kbasv: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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.