You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
root@rohan-virtual-machine:/home/rohan/openebs/cstor-operators# kubectl create ns test-backup
namespace/test-backup created
root@rohan-virtual-machine:/home/rohan/openebs/cstor-operators# kubectl get pvc -n test-backup
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
demo-cstor-vol Bound pvc-d85191ca-0b87-4dbd-a8ff-57503d4ef8d4 5Gi RWO cstor-csi-stripe 52s
root@rohan-virtual-machine:/home/rohan/openebs/cstor-operators# kubectl get all -n test-backup
NAME READY STATUS RESTARTS AGE
pod/busybox 1/1 Running 0 14s
What steps did you take and what happened:
I was trying to backup and restore a namespace. A busybox pod is running in the namespace and has a PVC attached.
PVC was provisioned by following the steps on https://github.com/openebs/cstor-operators/blob/master/docs/tutorial/volumes/snapshot.md
Steps followed for backup/restore
Create a namespace and deploy a pod.
Create backup job
Restore from that backup
PVC details
What did you expect to happen:
Restore should have been successful and PVC should have been attached to the pod
Environment:
velero version
): v1.4.0velero client config get features
):kubectl version
): 1.18/etc/os-release
):The text was updated successfully, but these errors were encountered: