nfs-subdir-external-provisioner icon indicating copy to clipboard operation
nfs-subdir-external-provisioner copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Support restoring a volume

Open cornfeedhobo opened this issue 2 years ago • 4 comments

What I want

I'd like to be able to destroy a StatefulSet, then optionally un-archive the previous PVC directory and use it to satisfy the claim for a new StatefulSet.

What currently happens

I have to re-populate manually on the NFS server

cornfeedhobo avatar May 20 '22 21:05 cornfeedhobo

Yeah I'd like some sort of automatic mechanism to auto-unarchive or something like that.

BloodyIron avatar May 29 '22 02:05 BloodyIron

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Aug 27 '22 03:08 k8s-triage-robot

I've honestly just switched to csi-driver-nfs, and I appreciate this project existing as an option, but the dynamic-only method here doesn't work for me. And it sure looks like there's no motivation for that to change for this project. Oh well.

BloodyIron avatar Aug 27 '22 18:08 BloodyIron

/remove-lifecycle stale

cornfeedhobo avatar Sep 06 '22 14:09 cornfeedhobo

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Dec 05 '22 14:12 k8s-triage-robot