Skip to content

[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

Open
aelbarkani opened this issue May 24, 2020 · 4 comments
Open

[RFE] Better control of what operator version is deployed #1544

aelbarkani opened this issue May 24, 2020 · 4 comments
Labels
triage/unresolved Indicates an issue that can not or will not be resolved.

Comments

@aelbarkani
Copy link

aelbarkani commented May 24, 2020

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.

@stale
Copy link

stale bot commented Jul 23, 2020

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.

@stale stale bot added the wontfix label Jul 23, 2020
@openshift-ci-robot openshift-ci-robot added triage/unresolved Indicates an issue that can not or will not be resolved. and removed wontfix labels Jul 24, 2020
@stale
Copy link

stale bot commented Sep 22, 2020

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.

@stale
Copy link

stale bot commented Nov 22, 2020

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.

@stale
Copy link

stale bot commented Jan 22, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/unresolved Indicates an issue that can not or will not be resolved.
Projects
None yet
Development

No branches or pull requests

2 participants