Operator installation fails when using imagePullSecret linked to the default service account

[srinivasannanduri]

Bug Report

What did you do?
We are working on an operator that installs via OLM and the images are from a private registry. The operator uses default Service Account (in CSV). Hence, we create a (secret) imagePullSecret to our private image registry and link it to the 'default' service account before we install the operator. The deployment of the operator, updates the default Service Account and removes the linked imagePullSecret from the ServiceAccount. This causes the deployment of the operator to fail. Once we recreate the secret and the link to the Service Account and following it up with pod recreation [delete the pod (for reconcile to happen), the recreated pod just picks it up right] it works. When we define a Service Account and use the one that we created, the issue doesn't appear

What did you expect to see?
Operator deployment succeeds with the given imagePullSecret in default service account

What did you see instead? Under which circumstances?
Deployment of the operator failed

Environment
v1.0.0

• Kubernetes version information:

  oc v3.11.0+0cbc58b
    kubernetes v1.11.0+d4cacc0
    features: Basic-Auth
    kubernetes v1.18.3+6c42de8

• Kubernetes cluster kind:
  Openshift

Possible Solution

Additional context
Add any other context about the problem here.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.