Replies: 2 comments 1 reply
-
Btw is a user, I would appreciate it if any requirements were enforced in code. That is if I attempt an unsupported upgrade then I would like a clear error message informing me of this written somewhere where I am most likely to see it. |
Beta Was this translation helpful? Give feedback.
-
Given that whatever we end up officially supporting, we should also be automatically testing. I'd say we should only officially support upgrading one minor version at a time, or at most skipping one minor, given that we officially support 3 minor releases at a time. So:
Regarding clearly erroring out on unsupported version bumps, this could be definitely done by the helm chart itself. Doing that from Crossplane itself would require having the version stored somewhere, which I don't think we have at the moment, but would be feasible. However, on one side I agree we should warn users they are doing something we don't officially support, but I would not fully prevent them from doing so if they are willing to assume such risk. So I would at least add a way to bypass it, if we decided to prevent that by default (which I would vote against). |
Beta Was this translation helpful? Give feedback.
-
In #4557 a user had issues upgrading from v1.7.0 to v1.13.2.
What is our "supported" upgrade path?
How far back do we want to support upgrades from/to?
What should have been the (generic) recommendation for this user?
How should we capture the API changes that would result in this kind of behavior?
Beta Was this translation helpful? Give feedback.
All reactions