subscription configuration causes operator deployment rolling update after initialization

[horis233]

Type of question

I found when we set the subscription configuration, the operator deployment will be restarted in two steps:

1. OLM operator creates the operator deployment according to the `.spec.install.deployment from the CSV.
2. Catalog operator updates the operator deployment by the subscription configuration.

That will cause operator deployment to get rolling updated during the installation.

Because the subscription configuration is applied after the operator is created, my concern is what if a user creates the operator CR after the operator is initialized but not been applied the subscription configuration yet. It may cause the operator to reconcile the CR ad get unexpected behaviour.

Could the subscription configuration be applied to the operator deployment when it is initialized, instead of updating the deployment after it is installed?

Question

What did you do? A clear and concise description of the steps you took (or insert a code snippet).

What did you expect to see? A clear and concise description of what you expected to happen (or insert a code snippet).

What did you see instead? Under which circumstances? A clear and concise description of what you expected to happen (or insert a code snippet).

Environment

• operator-lifecycle-manager version: 0.17.0

• Kubernetes version information: Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.0+bd9e442", GitCommit:"bd9e4421804c212e6ac7ee074050096f08dda543", GitTreeState:"clean", BuildDate:"2021-02-11T23:05:38Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}

• Kubernetes cluster kind: OCP Additional context Add any other context about the question here.

[exdx]

Is this reproducible in a consistent way? If so, we should prioritize. For now, we will put this on the backlog.