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

Stop operator upgrades when there is an unsupported scylla version #2464

Open
mflendrich opened this issue Feb 4, 2025 · 0 comments
Open
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@mflendrich
Copy link
Collaborator

Issue originally authored by tnozicka as #653

Is this a bug report or feature request?

  • Feature Request

What should the feature do:

  • Operator should fail to start (never become ready) when it lists a scylla cluster with an unsupported scylla version. It will stop operator upgrade to prevent managing an unsupported scylla version.
  • Operator won't act on ScyllaClusters with unsupported versions, except for updating status and adding degraded condition with UnsupportedVersion reason. (In case a clusted would be recreated / adopted.)

What is use case behind this feature:
Prevent working with unsupported scylla versions that would break, like when it doesn't have seedless support.

@mflendrich mflendrich added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Feb 4, 2025
@mflendrich mflendrich added the lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. label Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

1 participant