-
Notifications
You must be signed in to change notification settings - Fork 40.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow KUBE_TEST_REPO_LIST to be a remote url as well #108429
Allow KUBE_TEST_REPO_LIST to be a remote url as well #108429
Conversation
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
@dims: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/release-note-none |
/sig testing /assign @BenTheElder @liggitt |
/hold for testing |
/retest |
/test pull-kubernetes-e2e-gce-registry-sandbox |
(note only those images that are configured using the KUBE_TEST_REPO_LIST will be picked up from the alternate repos) /hold cancel |
/retest |
/skip |
/lgtm |
/test pull-kubernetes-e2e-gce-registry-sandbox |
/hold
Looks like some well intentioned fixes broke things: |
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
/test pull-kubernetes-e2e-gce-registry-sandbox |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
/lgtm |
/hold cancel pull-kubernetes-e2e-gce-registry-sandbox is now 💚 |
/test pull-kubernetes-unit |
/retest |
/release-note-edit
|
…08429-upstream-release-1.23 Automated cherry pick of #108429: Allow KUBE_TEST_REPO_LIST to be a remote url as well
KUBE_TEST_REPO_LIST originally was just a file path location. In this PR we add support so it could contain a remote url as well.
Why do we need this?
If you look at how this env var (pointing to a yaml file) is being used for example in:
https://github.com/kubernetes/test-infra/blob/e3b05747b13fa4c629fa96a8a3aa42b642ae1888/kubetest/aksengine.go#L1264-L1288
you will see that the yaml file is downloaded from the remote url and then saved into an intermediate file and then the KUBE_TEST_REPO_LIST is set to the location of file on disk. Let's just get rid of the intermediate step.
This will help
/kind cleanup
Signed-off-by: Davanum Srinivas davanum@gmail.com
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: