Just like cluster-samples-operator already does for Jenkins itself and the Node.js and Maven agents, it should also overwrite the jenkins-agent-base imagestream so that users always get an image corresponding to their release of OpenShift.
@XiuJuan - verification simply entails confirming that the images for the IST in the jenkins-agent-base imagestream in the openshift namespace comes from the install payload
Verified with 4.7.0-0.nightly-2020-10-24-155529. $oc describe is jenkins-agent-base -n openshift Name: jenkins-agent-base Namespace: openshift Created: 7 hours ago Labels: samples.operator.openshift.io/managed=true Annotations: openshift.io/image.dockerRepositoryCheck=2020-10-26T00:53:04Z samples.operator.openshift.io/version=4.7.0-0.nightly-2020-10-24-155529 Image Repository: image-registry.openshift-image-registry.svc:5000/openshift/jenkins-agent-base Image Lookup: local=false Unique Images: 1 Tags: 1 latest tagged from quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:7581ce480fb2028abc438d6c539566ef138a5845c74cecfab8cd41133ce185f5 prefer registry pullthrough when referencing this tag Provides a Jenkins Base Agent to extend Jenkins agents Tags: jenkins * quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:7581ce480fb2028abc438d6c539566ef138a5845c74cecfab8cd41133ce185f5 7 hours ago
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633