kubernetes: Make CSI test suite timeouts configurable
What would you like to be added:
Current external CSI tests expect that pods can start in 5 minutes. This startup includes dynamic provisioning (if WaitForFirstConsumer
is enabled), scheduling, volume attach and mount.
The timeout is extended to 10 minutes for snapshot restore and cloning tests.
Both timeouts (and maybe others) are hardcoded in the code base now. They should be configurable.
Why is this needed:
This suite is to be used by 3rd party driver vendors to test their CSI drivers. Different storage drivers can be slower, especially when dynamically provisioning a volume.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 17 (14 by maintainers)
Snapshot restore and Cloning test use
TestVolumeClientSlow
, which allows 15 minutes.https://github.com/kubernetes/kubernetes/blob/0cdd5365a1d0c8ccad93bf5d12fbf54ec69deb0e/test/e2e/storage/testsuites/provisioning.go#L260
https://github.com/kubernetes/kubernetes/blob/b748c702d995dc4c26dfc1a12fb4beb5d8de91ae/test/e2e/framework/pod/wait.go#L64