Description of problem (please be detailed as possible and provide log
snippets):

ODF-MCO operator logging security credentials.

2022-02-24T10:38:51.867Z	INFO	controller-runtime.manager.controller.secret	Creating a s3 secret	{"reconciler group": "", "reconciler kind": "Secret", "name": "756bd87b55371f0a9a791269d78efdaeb2617fc", "namespace": "spoke-cluster", "secret": {"metadata":{"name":"756bd87b55371f0a9a791269d78efdaeb2617fc","namespace":"openshift-dr-system","creationTimestamp":null,"labels":{"multicluster.odf.openshift.io/created-by":"mirrorpeersecret"}},"data":{"AWS_ACCESS_KEY_ID":"**************************,"AWS_SECRET_ACCESS_KEY":"*******************"},"type":"Opaque"}}



Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Import 2 managed clusters in ACM.
2. Install ODFMCO on the Hub cluster.
3. Install ODF operator on each managed cluster.
4. Create OCS StorageSystem on each managed cluster.
5. Do not install the ODR HUB operator(Ramen hub operator) on the hub cluster.
6. Make sure "openshift-dr-system" is not present.
6. Create MirrorPeer CR with "manageS3" flag enabled.
7. Check ODFMCO operator logs on the openshift-operators namespace. It will log AWS credentials.
 


Actual results:
the cloud API credentials are logged when creating/updating the s3 secret.

Expected results:
Logs should not have any credentials information.

Additional info: