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.

Sign up for GitHub

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

Jump to bottom

Document and test storage resizing on the same nodes #2453

Open
mflendrich opened this issue Feb 4, 2025 · 1 comment
Open

Document and test storage resizing on the same nodes #2453

mflendrich opened this issue Feb 4, 2025 · 1 comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. 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 #825

Given StatefulSet don't reconcile storage changes we can't yet easily handle it in the operator seamlessly and we should at least document a manual procedure. Something in the lines of:

  • orphan delete the scyllacluster
  • orphan delete the statefulsets
  • create the scyllacluster with higher storage request
  • resize the existing PVC, if the storage class supports it, replace the nodes if it doesn't
  • trigger a scyllacuster rollout
@mflendrich mflendrich added kind/documentation Categorizes issue or PR as related to documentation. 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 mentioned this issue Feb 4, 2025
Closed
@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
@mflendrich
Copy link
Collaborator Author

The scope is to carry the community PR #2243 through completion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/documentation Categorizes issue or PR as related to documentation. 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
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mflendrich