Add Kubernetes e2e tests of the driver

[jsafrane]

Kubernetes allows to run its e2e tests against a CSI driver: https://github.com/kubernetes/kubernetes/tree/master/test/e2e/storage/external

It will go through all Kubernetes features - dynamic provisioning, topology, subpath, volume expansion, snapshots, cloning... It allows a CSI driver to select features to tests (e.g. no cloning for AWS EBS).

What is necessary:

1. Kubernetes cluster.
2. Upstream tests, see the link above. Basically run ginkgo -focus=... in a specific kubernetes/kubernetes dir.
3. Test manifest describing what to tests (see readme linked above, simple yaml file).

From the other tests in this repo, 1. and 3. look easy, however, getting upstream tests at point 2. may be complicated. Is tester/migration-test-config.yaml something similar?

/feature

[leakingtapan]

Are you trying to test CSI migration with the k/k external test suites or test EBS CSI with the external test? Either way, the tester config file single-az-config.yaml, tells the tester what cluster to spin up and what test to run.

If you want to download k/k source and compile it, you could put it inside the test block before executing the e2e.test binary

[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

[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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.

[ayberk]

/reopen
/lifecycle frozen

[k8s-ci-robot]

@ayberk: Reopened this issue.

In response to this:

/reopen
/lifecycle frozen

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.