Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce the spec.Package field to the Operator API #69

Closed
3 tasks done
awgreene opened this issue Nov 29, 2022 · 4 comments
Closed
3 tasks done

Introduce the spec.Package field to the Operator API #69

awgreene opened this issue Nov 29, 2022 · 4 comments
Assignees

Comments

@awgreene
Copy link
Member

awgreene commented Nov 29, 2022

@joelanford
Copy link
Member

Looks like Tim was ahead of us on the GA Milestone issue: #60

@dmesser
Copy link

dmesser commented Dec 1, 2022

Will this have any implications on later asks to add a desiredVersion to the spec block ?

@awgreene
Copy link
Member Author

awgreene commented Dec 2, 2022

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.

@joelanford
Copy link
Member

Closed by #80

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

4 participants