mayadata-io / mayadata-io/d-operators
migrate Local PV to a different node
Open
Nobody has claimed this yet.
local pv
use case
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
After the Local PV is created and node affinity is set
based on kubernetes.io/hostname label, either:
- hostname label changed on the node or
- underlying storage (device) moved to a new node.
The nodeAffinity parameter on Local PV is not editable,
so to change the Local PV to new node some manual steps are
involved:
- Scale down the deployment or sts using the PVC.
- Save the PVC and PV yamls files.
- Delete the PVC and PV
- Modify the saved PV yaml will the node hostname and apply
Note: when re-applying the yamls, the uuid of pv and pvc objects will change, so the metadata around self-UUID,etc needs to be cleared. - Modify the saved PVC yaml for stale references and re-apply.
- Update the PV yaml with the uuid of the newly created PVC
- Scale up the deployment
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the manual Local PV migration steps in this issue and the repository's Kubernetes controller and declarative patterns. The issue does not name files, tests, or a specific implementation; completion criteria would need to define how migration should be supported and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100