Description of problem: We are using an S3 compatible storage backend and we want to use this for the image-registry as well.
Setting this in config.imageregistry.operator.openshift.io -
spec:
   storage:
    s3:
      bucket: xyz-registry
      region: eu-de
      regionEndpoint: xyz.com

gets overwritten by this - 
spec:
   storage:
    s3:
      bucket: xyz-registry
      encrypt: true
      keyID: ''
      region: eu-de
      regionEndpoint: xyz.com

This causes builds to fail because the registry uses encryption but the backend does not support it. Setting explicitly "encrypt: false" is overwritten to "encrypt: true", we can also see that the "generation" of the resource is incremented by 2.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results: Not able to use S3 storage as backend doesnt support encrypt true

Expected results: Should be able to modify


Additional info: