sig-storage-local-static-provisioner
sig-storage-local-static-provisioner copied to clipboard
3.0.0 enhancements
This is a track issue for the next major release 3.0.0. Backward incompatible changes can be made if they can simplify design, code implementation, or improve UX.
Proposals:
- Local cloud controller:
- Used to recover workloads using local PVs from data loss in the cloud https://docs.google.com/document/d/1SA9epEwA3jPwibRV0ccQwJ2UfZXoeUYKyNxNegt0vn4/edit?usp=drive_web&ouid=101493314076334303906
- addresses https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/issues/181#issuecomment-611895448
- Versioned component config API
- Able to clean PV before discovering it as a new PV: https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/issues/143
- Provide generic solutions for most scenarios in the volume preparation phase
- yamls or generic agent e.g. https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/pull/103
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/remove-lifecycle stale /lifecycle frozen
I was wondering if anybody has made any progress yet on the local cloud controller? It would be a great feature to have to not have to delete PVs manually when nodes get replaced
@cofyc any further progress on 3.0.0?