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

Support manual storage expansion in place #1572

Closed
2 of 3 tasks
tnozicka opened this issue Nov 16, 2023 · 2 comments
Closed
2 of 3 tasks

Support manual storage expansion in place #1572

tnozicka opened this issue Nov 16, 2023 · 2 comments
Labels
kind/epic Categorizes issue as an epic. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@tnozicka
Copy link
Contributor

tnozicka commented Nov 16, 2023 •
edited
Loading

We need to test and document a way to grow storage when there is space at the same node. At this point, due to some upstream limitation with StatefulSets this isn't supported in Scylla Operator yet and it needs support from the drivers. Our own driver also needs to support manual expansion in place

Tasks
Preview Give feedback
  1. Support automatic data volume expansion local-csi-driver#5
    kind/feature priority/important-soon triage/accepted
    zimnx
  2. Add e2e test that verifies manual storage expansion on the same node #1571
    kind/feature priority/important-soon triage/accepted
  3. Document and test storage resizing on the same nodes #825
    kind/documentation priority/important-longterm triage/accepted
@scylla-operator-bot scylla-operator-bot bot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Nov 16, 2023
@tnozicka tnozicka self-assigned this Nov 16, 2023
@tnozicka tnozicka added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/epic Categorizes issue as an epic. labels Nov 16, 2023
@scylla-operator-bot scylla-operator-bot bot removed the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Nov 16, 2023
@tnozicka tnozicka changed the title Support manual storage expansion Support manual storage expansion in place Nov 16, 2023
@tnozicka tnozicka mentioned this issue Nov 16, 2023
Closed
@scylla-operator-bot scylla-operator-bot
Copy link
Contributor

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out

/lifecycle stale

@scylla-operator-bot scylla-operator-bot bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 30, 2024
@tnozicka
Copy link
Contributor Author

tnozicka commented Jul 1, 2024

/remove-lifecycle stale
/triage accepted

@scylla-operator-bot scylla-operator-bot bot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 1, 2024
@tnozicka tnozicka removed their assignment Nov 25, 2024
@tnozicka tnozicka closed this as not planned Won't fix, can't repro, duplicate, stale Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/epic Categorizes issue as an epic. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. 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
@tnozicka