mirrors/velero
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/velero.git synced 2026-05-02 13:25:48 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #9042 from priyansh17/readme-update/test
Some checks failed
Run the E2E test on kind / build (push) Failing after 7m12s
Details
Run the E2E test on kind / setup-test-matrix (push) Successful in 4s
Details
Run the E2E test on kind / run-e2e-test (push) Has been skipped
Details
Main CI / Build (push) Failing after 1m3s
Details

Browse Source 
[Readme update] Add image registry proxy option to E2E test configuration
This commit is contained in:
Xun Jiang/Bruce Jiang
2025-06-25 21:13:51 +08:00
committed by GitHub
parent 4e5020d463 f0f7b08265
commit 37a22a3f56
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
test/e2e/README.md
View File

@@ -80,6 +80,7 @@ These configuration parameters are expected as values to the following command l
1. `--fail-fast`: A switch for for failing fast on meeting error.
1. `--has-vsphere-plugin`: A switch to indicate whether the Velero vSphere plugin is installed for vSphere environment.
1. `--worker-os`: A switch to indicate the workload should be ran on windows or linux OS.
1. `--image-registry-proxy`: specifies a custom image registry proxy to be used for pulling container images.
These configurations or parameters are used to generate install options for Velero for each test suite.
@@ -133,8 +134,7 @@ Below is a mapping between `make` variables to E2E configuration flags.
1. `FAIL_FAST`: `--fail-fast`. Optional.
1. `HAS_VSPHERE_PLUGIN`: `--has-vsphere-plugin`. Optional.
1. `WORKER_OS`: `--worker-os`. Optional.
1. `IMAGE_REGISTRY_PROXY`: `--image-registry-proxy.` Optional.
### Examples