<p>When I edit the <strong>image-registry</strong> Deployment (in the openshift-image-registry Namespace/Project), the modified fields are automatically reverted/rolled-back on Save.</p>
<p>My understanding is that Deployments control/manage some resources (i.e., ReplicaSets), but what Resource/CustomResource/CustomResourceDefinition controls/manages Deployments?</p>
<p>I'm unsure how to set a different securityContext &gt; fsGroup for my image-registry pod because the Deployment changes I make are being reverted/rolled-back.</p>

DizzyThermal
<p>That resource is managed by the image-registry operator. You can check for yourself with <code>oc get clusteroperator image-registry</code> and edit the configuration for the operator with <code>oc edit configs.imageregistry.operator.openshift.io</code>.</p>
<p>It is possible to set the image-registry operator in <code>Unmanaged</code> state, by editing <code>configs.imageregistry.operator.openshift.io</code> and setting <code>managementState</code> to <code>Unmanaged</code>. This would prevent the operator from actively managing its components and should allow you to change the ReplicaSet without the operator reverting your changes. Please note that setting the operator in Unmanaged state is not supported by Red Hat.</p>
<p>You can find more in depth documentation on the registry in the <a href="https://docs.openshift.com/container-platform/4.8/registry/architecture-component-imageregistry.html" rel="nofollow noreferrer">registry chapter</a> of the OpenShift documentation.</p>
