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
Get inside nfs server pod and check for the content inside mount path given
(use command kubectl exec -ti -n test-kahu /bin/sh)
Create a restore CR on new namespace (restore-ns)
apiVersion: kahu.io/v1
kind: Restore
metadata:
name: restore-Kahu-0001
Spec:
backupName: backup-Kahu-0001
namespaceMapping:
test-ns : restore-ns
Expected Result:
In step 2,
a) Verify that backup stage is Finished and State is Completed
b) Verify the resource list in status shows all the required resources
In step 3, verify that
a) tar file is created with name of backup
b) After untar file, All pods and the specific deployment mentioned are backuped.
In step4, verify that
a) Backed up specific deployment and pods are up in new namespace restore-ns
Why this issue to fixed / feature is needed(give scenarios or use cases):
This is a testcase which is to automated to make sure deployment is properly backed up and
Restored.
The text was updated successfully, but these errors were encountered:
Testcase Precondition:
a. backup service
b. Meta service with nfs provider
c. nfs-server
5.Namespace restore-ns is created
Testcase steps:
(use kubectl create -f <backup.yaml>)
apiVersion: kahu.io/v1
kind: Backup
metadata:
name: backup-Kahu-0001
spec:
includeNamespaces: [test-ns]
metadataLocation: nfs
includeResources:
kind: Pod
isRegex: true
kind: Deployment
isRegex: true
(use command kubectl exec -ti -n test-kahu /bin/sh)
apiVersion: kahu.io/v1
kind: Restore
metadata:
name: restore-Kahu-0001
Spec:
backupName: backup-Kahu-0001
namespaceMapping:
test-ns : restore-ns
Expected Result:
a) Verify that backup stage is Finished and State is Completed
b) Verify the resource list in status shows all the required resources
a) tar file is created with name of backup
b) After untar file, All pods and the specific deployment mentioned are backuped.
a) Backed up specific deployment and pods are up in new namespace restore-ns
Why this issue to fixed / feature is needed(give scenarios or use cases):
This is a testcase which is to automated to make sure deployment is properly backed up and
Restored.
The text was updated successfully, but these errors were encountered: