mirror of
https://github.com/vmware-tanzu/velero.git
synced 2026-10-22 14:23:00 +00:00
KrishhnaTandGitHub
b7ec0d6264
Run the E2E test on kind / setup-test-matrix (push) Failing after 3s
e2e-test-kind.yaml / extract (push) Failing after 6s
Run the E2E test on kind / get-go-version (push) Failing after 9s
Run the E2E test on kind / build (push) Skipped
Run the E2E test on kind / run-e2e-test (push) Skipped
Run the E2E test on kind / run-csi-e2e-test (push) Skipped
push.yml / extract (push) Failing after 7s
Scorecard supply-chain security / Scorecard analysis (push) Skipped
Main CI / get-go-version (push) Failing after 8s
Main CI / Build (push) Skipped
* e2e: point Kibishii at the kind-csi overlay when CSI is enabled installKibishii maps the cloud platform to a Kibishii overlay directory and already swaps Azure and AWS for their CSI variants when EnableCSI is set. Kind has no such branch, so a CSI run on kind gets the plain kind overlay, whose StorageClass provisions with rancher.io/local-path. Those PVs are hostPath volumes and Velero skips them for both CSI snapshots and PodVolumeBackups, which is why the snapshot cases are guarded off on kind today. Add the kind branch alongside the other two, and move KIBISHII_COMMIT to the commit that adds the overlay. The pin delta is additive: the only difference between the two trees is the new kind-csi directory and its reclaim-policy overlay, so the plain kind overlay that run-e2e-test uses still builds on rancher.io/local-path. Nothing selects a Kibishii case under EnableCSI yet, so this changes no observable behaviour on its own. Narrowing the kind guards and adding a label set to the CSI job follow separately. Signed-off-by: krishhna24 <krishhnatupedev@gmail.com> * Add changelog for #10657 Signed-off-by: krishhna24 <krishhnatupedev@gmail.com> --------- Signed-off-by: krishhna24 <krishhnatupedev@gmail.com>