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

Pin Operators To Specific Versions #33

Open
tylerauerbeck opened this issue Jul 31, 2021 · 3 comments
Open

Pin Operators To Specific Versions #33

tylerauerbeck opened this issue Jul 31, 2021 · 3 comments
Assignees

Comments

@tylerauerbeck
Copy link
Contributor

Mentioned this in #32 but we can loop this in at a later point:

To avoid the workaround, is there a possibility of maybe just pinning CRW to a "healthy version"? I haven't looked too much at the problem, but wherever we end up we probably want to avoid having the operator upgrade things mid-run. So would probably be good to just pick a point to pin to once we land on something that works.

cc/ @springdo @eformat @ckavili

@springdo
Copy link
Contributor

+1

@jfilipcz jfilipcz self-assigned this Mar 4, 2022
@ckavili
Copy link
Contributor

ckavili commented Mar 16, 2022

I guess for now we are tracking them with separate values file came with this #105 right, @jfilipcz?

@jfilipcz
Copy link
Contributor

jfilipcz commented Mar 16, 2022

That's unfortunately only part of work that needs to be done. Other is preparation of Mirror that will hold the operators index image, creation of Custom CatalogSource on target environment etc. This file is good enough as long as versions are still present in original operators index image

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

No branches or pull requests

4 participants