You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What did you expect to see?
If there is no resources config defined in the subscription then the resources defined in the CSV should be preserved.
What did you see instead? Under which circumstances?
The resources section in the deployment was overwritten with the empty section from the subscription.
It is not checked if the resource config was defined in the subscription and the resources section of the containers is overwritten with the empty structure.
Bug Report
What did you do?
Created the following subscription where there is no override on the resources:
This is the CSV that has resources section defined:
The deployment created by the olm-operator based on the CSV, with empty resources section:
What did you expect to see?
If there is no resources config defined in the subscription then the resources defined in the CSV should be preserved.
What did you see instead? Under which circumstances?
The resources section in the deployment was overwritten with the empty section from the subscription.
Environment
vagrant@vmvagrant> kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:23:09Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.9", GitCommit:"a17149e1a189050796ced469dbd78d380f2ed5ef", GitTreeState:"clean", BuildDate:"2020-04-16T11:36:15Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Possible Solution
It is not checked if the resource config was defined in the subscription and the resources section of the containers is overwritten with the empty structure.
Additional context
#1334 (comment)
@umangachapagain
The text was updated successfully, but these errors were encountered: