Operators that rely on library-go's Apply{DaemonSet,Deployment} function were previously responsible for detecting changes to a managed resource's spec or changes to external resources and forcing a reload. All operators should be updated to use the revised Apply* methods recently merged to library-go [1] to ensure consistent behavior in responding to changes in external resources or changes to the spec of a managed deployment or daemonset. 1: https://github.com/openshift/library-go/pull/773
Still need to update the service ca operator for 4.5.
Note that this is an umbrella bz. As per the linked github PRs, if testing is to be done, it should be done for all updated operators.
No regression issue found related in QE latest 4.5 nightly builds' functional tests and upgrade tests so far. Specifically take openshiftapiserver for example, rolling out has no regression issue (tested in 4.5.0-0.nightly-2020-06-18-210518 env) $ oc edit project.config cluster # add below ... spec: projectRequestMessage: xxia test projectRequestMessage change ... $ oc get openshiftapiserver cluster -o yaml ... spec: ... projectConfig: projectRequestMessage: xxia test projectRequestMessage change ... $ oc get po -n openshift-apiserver # can see rolling out success.
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. https://access.redhat.com/errata/RHBA-2020:2409