-
Notifications
You must be signed in to change notification settings - Fork 64
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
Relax Version restrictions #544
Comments
It would be ideal to look at this more wholistically, for example, can the version be detected via management API so that the user doesn't have to supply it at all? In general, we have ongoing problems with the CRDs where we allow specification of a given option in more than one place. This is an example of that, because the version is really set via the |
What is missing?
Make Cassandra and DSE version validation a little more forgiving so we don't have to keep revisiting it every time new server versions come out.
Why is this needed?
There are Version validations for Cassandra/DSE that become a little tedious to maintain as the server versions move forward. For example, #542. It would be easier if we didn't have to revisit this when Cassandra 6 comes out or DSE 8, etc...
The text was updated successfully, but these errors were encountered: