TRT-1822: Make registry available from squid proxy as well#1702
TRT-1822: Make registry available from squid proxy as well#1702stbenjam wants to merge 1 commit intoopenshift-metal3:masterfrom
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Not sure if this works from dev-scripts: /payload-job periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-ipv6-techpreview |
8cfd0fc to
451d83f
Compare
|
/hold It's still not working :( |
|
/test ci/prow/e2e-metal-ipi-bm |
|
@stbenjam: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
DetailsIn response to this:
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-sigs/prow repository. |
|
/test e2e-metal-ipi-bm |
|
@stbenjam: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
openshift-tests now runs some tests by extracting additional binaries from the payload, but on disconnected installs we need to be able to reach the mirror from the build cluster.
Once we know the provisioning network's IP for the local registry, this modifies any running squid container to include this in /etc/hosts so it's reachable.