Restic volumes not restored when remapping namespace #3650
-
Hello, I am trying to restore a volume backed up using the restic integration into a different namespace. However the As far as I understand the design documentation pv-cloning.md and the restic integration limitations cloning a volume into a different namespace should be possible right? During my investigation I found this line which might be the culprit. To my understanding this creates the Steps to reproduce
# app.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: task-pv-claim
spec:
storageClassName: manual
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 3Gi
---
apiVersion: v1
kind: Pod
metadata:
name: task-pv-pod
spec:
volumes:
- name: task-pv-storage
persistentVolumeClaim:
claimName: task-pv-claim
containers:
- name: task-pv-container
image: nginx
ports:
- containerPort: 80
name: "http-server"
volumeMounts:
- mountPath: "/usr/share/nginx/html"
name: task-pv-storage
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
@thecodinglab There was a related issue that we recently fixed. #3475 |
Beta Was this translation helpful? Give feedback.
@thecodinglab There was a related issue that we recently fixed. #3475
Can you please try this out with the latest
v1.5.4
or thev1.6
release and reopen/mark unanswered if it isn't resolved?