Description of problem:
A cluster admin can make arbitrary changes to the image registry's deployment, and the image registry operator will leave these changes in place as long as other configuration has not changed.
Version-Release number of selected component (if applicable): 4.1.z
How reproducible: Always
Steps to Reproduce:
1. `oc edit deployment image-registry -n openshift-image-registry`
2. Add an environment variable to the pod template spec - ex: name: FOO, value: BAR
3. Wait for the registry deployment to roll out
Added environment variable is present in the image registry pod.
Image registry operator undoes the edit to the pod template spec, and when rollouts complete the registry pods do not contain the added environment variable.
at a minimum these changes should be getting stomped on our next sync/reconcile loop (not sure what the interval is on that these days). if they are not, that's definitely a bug.
The pull request is merged.
Verified on 4.4.0-0.nightly-2020-02-06-230833, the changes made in image-registry deployment will be reverted.
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.