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 automatic data volume expansion #5

Open
Tracked by #1572
, #1575
...
zimnx opened this issue Nov 22, 2022 · 4 comments
Open
Tracked by #1572
, #1575
...

Support automatic data volume expansion #5

zimnx opened this issue Nov 22, 2022 · 4 comments
Assignees
@zimnx
Labels
kind/feature Categorizes issue or PR as related to a new feature. 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

@zimnx
Copy link
Collaborator

zimnx commented Nov 22, 2022 •
edited
Loading

Driver should be able to expand the volume size. With XFS Quotas it should be fairly easy.

Driver should:

  • Implement VolumeExpansion plugin capability.
  • Implement EXPAND_VOLUME controller capability or implement EXPAND_VOLUME node capability or both.
@zimnx zimnx added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 22, 2022
@mykaul
Copy link

mykaul commented Nov 22, 2022

(linked to scylladb/scylla-operator#1103 )

This was referenced Nov 16, 2023
Open
Open
@tnozicka tnozicka added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Nov 16, 2023
@Kavinraja-G
Copy link

@tnozicka -- I was looking to use k8s-local-volume-provisioner in prod envs. Thought of having a look at this volumeExpansion. Does that mean currently we can't able expand the volumes once created via NodeConfig?

Any ETA on this feature? Thanks!

@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 Jul 15, 2024
@tnozicka
Copy link
Member

/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 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zimnx zimnx

Labels
kind/feature Categorizes issue or PR as related to a new feature. 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
4 participants
@zimnx @mykaul @tnozicka @Kavinraja-G