Installation of the service account does not keep pull image secrets

[fantapsody]

Type of question

Are you asking about community best practices, how to implement a specific feature, or about general context and help around the operator-sdk?

Question

What did you do?
I had multiple operators developed by us scaffolded by operator-sdk 1.0 installed into the same namespace, the ServiceAccount default was overwritten multiple times and the field pullImageSecrets was removed, and the field metadata.ownerReferences was set to one of the CSV.

What did you expect to see?

• do not overwrite the service account if it already exists
• or preserve pullImageSecrets previously set to the ServiceAccount.

What did you see instead? Under which circumstances?
The pullImageSecrets field was removed from the ServiceAccount default after the installation.

Environment

• operator-lifecycle-manager version:
  v0.15.1

• Kubernetes version information:
  v1.16.13

• Kubernetes cluster kind:
  GKE

Additional context

[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.

[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.