Run kubernetes e2e tests without migration

[jsafrane]

E2E tests for CSI migration are added in #294. We need the same e2e tests also with plain CSI driver, without migration.

In other words, install the driver and run upstream e2e tests with the CSI driver (with the driver in StorageClass, no migration), as described in https://github.com/kubernetes/kubernetes/blob/master/test/e2e/storage/external/README.md.

Since most of the work (cluster & driver installation) is already done, it could be a simple ginkgo command in a new prow job.

/feature

[leakingtapan]

Another additional work is the current testing script is not that configurable for tuning feature gates (hard coded to enabled migration). I have already written a new framework (which is more configurable) for e2e testing, I need make changes to create 1.16+ cluster (due to kops is not yet officially released to 1.16+ cluster)

The other idea is we can combine the upstream e2e testing suites with the existing e2e suites instead of creating new make target. So that it will be run as part of make testing-e2e-single-az or make testing-e2e-multi-az

[leakingtapan]

due to kops is not yet officially released to 1.16+ cluster

I just switched to use kops 1.16 alpha: #409

[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.

[AndyXiangLi]

We already add external e2e test in PR
This can be closed when upstream test-infra update our CI kubernetes/test-infra#20747

[ayberk]

OK let me close this one. I'll get that merged today.

/close

[k8s-ci-robot]

@ayberk: Closing this issue.

In response to this:

OK let me close this one. I'll get that merged today.

/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.