mirror of
https://github.com/vmware-tanzu/velero.git
synced 2026-10-22 06:13:00 +00:00
KrishhnaTandGitHub
8c59d546b0
Run the E2E test on kind / setup-test-matrix (push) Failing after 3s
e2e-test-kind.yaml / extract (push) Failing after 7s
Run the E2E test on kind / get-go-version (push) Failing after 8s
Run the E2E test on kind / build (push) Skipped
Run the E2E test on kind / run-e2e-test (push) Skipped
push.yml / extract (push) Failing after 7s
Main CI / get-go-version (push) Failing after 9s
Main CI / Build (push) Skipped
Scorecard supply-chain security / Scorecard analysis (push) Skipped
The e2e suite creates both of its StorageClasses from the provider's file under testdata/storage-class, so running against a cluster whose volumes need a different provisioner or parameters means editing test data every other job also reads. On kind that is the only way to get a class a CSI driver can snapshot. Take the definition as a flag instead. --storage-class-file and --storage-class-file-2 name a manifest each, and the suite keeps creating and deleting what it applied, so nothing adopts resources it did not make. The class names stay fixed. Every spec refers to e2e-storage-class and e2e-storage-class-2, and CreateStorageClassFromYaml already takes a name override, so only the definition needs to vary. An empty --storage-class-file-2 runs without a second StorageClass, and the three cases that map between two of them skip with a message saying how to enable them. Which specs need it cannot be worked out in BeforeSuite, since the label filter is not visible there yet, so this is expressed as an opt-out rather than detection. Signed-off-by: krishhna24 <krishhnatupedev@gmail.com>