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

[Proposal] Support moving data from one drive to another within the same node #877

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Proposal] Support moving data from one drive to another within the same node #877

wants to merge 1 commit into from

Conversation

Praveenrajmani
Copy link
Collaborator

@Praveenrajmani Praveenrajmani commented Oct 30, 2023 •
edited

This is a feature proposal to support moving of data from one drive to another. Currently, we support moving the references only.

  • By adding another flag --with-data in kubectl directpv move command, creates the job for moving the volumes including data from one drive to another within the same node.
  • New jobs will be created which will create pods to move the data from one drive to another.
  • Until the job completes, the volumes will be in "moving" state and will not be binded. ie, NodeStageVolume calls will fail/wait. Upon successful completion, the volumes will be binded and the pod will be up.

@Praveenrajmani Praveenrajmani changed the title Support moving data from one drive to another within the same node [Proposal] Support moving data from one drive to another within the same node Oct 31, 2023
@Praveenrajmani Praveenrajmani force-pushed the movewithdata branch 7 times, most recently from 375d825 to dbb28fa Compare November 22, 2023 12:59
@Praveenrajmani Praveenrajmani marked this pull request as ready for review November 22, 2023 14:54
@Praveenrajmani Praveenrajmani force-pushed the movewithdata branch 3 times, most recently from ef85e98 to 346eb04 Compare November 23, 2023 03:24
@buccella
Copy link
Contributor

Any chance this gets merged before the next release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@balamurugana balamurugana Awaiting requested review from balamurugana

@r-scheele r-scheele Awaiting requested review from r-scheele

At least 2 approving reviews are required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@Praveenrajmani @buccella