-
Notifications
You must be signed in to change notification settings - Fork 553
[RFE] Better control of what operator version is deployed #1544
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
Comments
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. |
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. |
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. |
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. |
Feature Request
Is your feature request related to a problem? Please describe.
The way the operator is deployed through Subscriptions makes almost impossible to control what version of an operator is deployed. The solution proposed here consist of using startingCSV field + installPlanApproval: Manual in the Subscription. Than can be a relevant solution when managing a single cluster or a small number of clusters, but it's very difficult when you have dozens of clusters that need to be managed in an industrialized way (for example through GitOps).
Describe the solution you'd like
Adding an "endingCSV" field may be a possible solution.
The text was updated successfully, but these errors were encountered: