Add e2e tests

[leakingtapan]

Is your feature request related to a problem? Please describe.
We should add e2e test for supported features:

• static provisioning
• RWX mode from multiple pods
• encryption in transit

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[leakingtapan]

/remove-lifecycle stale

[wongma7]

/assign
I'll write tests.
Integrating them with CI is a different story.

[wongma7]

Running upstream e2e tests works, but we should skip Disruptive for now.
"static provisioning", we get for free.
"encryption in transit", maybe, depending on how much we want to test. Is checking that mount option "tls" is present sufficient?

Summarizing 2 Failures:

[Fail] EFS CSI [Driver: efs.csi.aws.com] [Testpattern: Pre-provisioned PV (default fs)] subPath [It] should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
/Users/mattwon/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/vendor/k8s.io/kubernetes/test/e2e/storage/utils/utils.go:212

[Fail] EFS CSI [Driver: efs.csi.aws.com] [Testpattern: Pre-provisioned PV (default fs)] subPath [It] should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
/Users/mattwon/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/vendor/k8s.io/kubernetes/test/e2e/storage/utils/utils.go:212

Ran 24 of 142 Specs in 1192.911 seconds
FAIL! -- 22 Passed | 2 Failed | 0 Pending | 118 Skipped
--- FAIL: TestEFSCSI (1192.91s)

[leakingtapan]

Integrating them with CI is a different story.

SGTM. Let's create a different issue to track this if you are going to focus on e2e test case for this issue.

Is checking that mount option "tls" is present sufficient?

This is the least we can do, but this approach also provides the least value. Can we do better?

[wongma7]

'should concurrently access the single volume from pods on different node' will cover RWX mode from multiple pods.

Will look into other ways to verify traffic is actually encrypted. May be tricky, might need to start a privileged pod on the node to for example check if there is an stunnel process for the mount

[leakingtapan]

/close

[k8s-ci-robot]

@leakingtapan: Closing this issue.

In response to this:

/close

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.