Skip to content

Commit 37a22a3

Browse files
authored
Merge pull request #9042 from priyansh17/readme-update/test
[Readme update] Add image registry proxy option to E2E test configuration
2 parents 4e5020d + f0f7b08 commit 37a22a3

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

test/e2e/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,7 @@ These configuration parameters are expected as values to the following command l
8080
1. `--fail-fast`: A switch for for failing fast on meeting error.
8181
1. `--has-vsphere-plugin`: A switch to indicate whether the Velero vSphere plugin is installed for vSphere environment.
8282
1. `--worker-os`: A switch to indicate the workload should be ran on windows or linux OS.
83+
1. `--image-registry-proxy`: specifies a custom image registry proxy to be used for pulling container images.
8384

8485
These configurations or parameters are used to generate install options for Velero for each test suite.
8586

@@ -133,8 +134,7 @@ Below is a mapping between `make` variables to E2E configuration flags.
133134
1. `FAIL_FAST`: `--fail-fast`. Optional.
134135
1. `HAS_VSPHERE_PLUGIN`: `--has-vsphere-plugin`. Optional.
135136
1. `WORKER_OS`: `--worker-os`. Optional.
136-
137-
137+
1. `IMAGE_REGISTRY_PROXY`: `--image-registry-proxy.` Optional.
138138

139139
### Examples
140140

0 commit comments

Comments
 (0)