Jenkins,jenkins-agent-maven,jenkins-agent-nodejs imagestreams could be imported successfully from payload in the disconnect cluster, and don't be overrided by samplesRegistry.
Verified in 4.4.0-0.nightly-2020-05-25-115719
@XiuJuan my understanding of that card is that it essentially optimizes pull through. It does not provide a path for disabling pull through.
Before the card https://issues.redhat.com/browse/IR-34 implements, and samplesRegistry can't override jenkins imagestreams anymore, we should add release note how to do workaround.
Perhaps I was not explicit enough, but https://issues.redhat.com/browse/IR-34 really does not have a bearing on
the jenkins related imagestreams and mirrors related to disconnected or registry override.
That said, we've got another round of doc improvements cooking with https://bugzilla.redhat.com/show_bug.cgi?id=1830946#c2
based on more customer experience,
where among other things clarification around the jenkins* imagestream special case is part of the updates I asked for.
If we want to craft a release note in the interim while Brandi sorts out that change, I'm amenable to that. Please work
with her directly on that. Does QE open BZs against docs to ask for release notes?
Open a doc bug #1841018 for 4.4 .
4.5 release note is under reviewing, will raise up this issue.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.