2c8a156579
Automatic merge from submit-queue e2e tests for VSAN policy support in Kubernetes for vSphere Following e2e test cases have been implemented for VSAN policy support in Kubernetes for vSphere. These e2e tests are for PR #42974 which out for review. A total of 8 test cases for below mentioned 5 different scenarios are implemented. Test cases: 1. Validation of VSAN capabilities. - hostFailuresToTolerate : Minimum 1 and Max 3. Should be integer. - stripeWidth: Minimum is 1 and Maximum is 12. Should be integer. - proportionalCapacity: Expressed in percentage. Should be between 0 and 100. Should be integer. - iopsLimit: Should be greater than 0. Should be integer. 2. Use a VSAN testbed setup. Try valid VSAN capabilities which are supported by VSAN testbed. Make sure the disk is created with policy configured with it. - Ex: Using hostFailuresToTolerate=0 and cacheReservation=12 Ex: diskStripes=1 and objectSpaceReservation=30 3. Use a VSAN testbed setup. Try valid VSAN capabilities which are not supported by VSAN testbed. Make sure that the disk creation fails and PVC status is pending. 4. Try using VSAN capabilities on a non-VSAN datastore. PVC status will be pending and it errors to the user saying to VSAN capabilities are not supported on a non-VSAN testbed. 5. Try all 1 to 5 with custom datastore specified by the user. @jeffvance @divyenpatel **Release note**: ```release-note None ``` |
||
|---|---|---|
| .. | ||
| e2e | ||
| e2e_federation | ||
| e2e_node | ||
| fixtures | ||
| images | ||
| integration | ||
| kubemark | ||
| list | ||
| soak | ||
| utils | ||
| BUILD | ||
| OWNERS | ||
| test_owners.csv | ||