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
Create a GA Milestone issue that captures that the spec.Package field will likely need to be changed in order to support other sourcing techniques. For example, installing a bundle image directly
Will this have any implications on later asks to add a desiredVersion to the spec block ?
We've created an issue to track the need to install from things other than catalogs (for example, installing the operator from a bundle image url). This will likely lead to a design where that supports multiple types of source declarations, one of which will meet the needs to specify packageName + version.
The text was updated successfully, but these errors were encountered: