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 deployments and pods are backuped.
In step4, verify that
a) Backed up deployments 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 How to reproduce, in case of a bug: Other Notes / Environment Information: (Please give the env information, log link or any
useful information for this issue)
Issue/Feature Description:
Testcase Precondition:
a. backup service
b. Meta service with nfs provider
c. nfs-server
some of the kubernetes resources
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:
metadataLocation: nfs
includeResources:
kind: Deployment
isRegex: true
includeResources:
kind: Pod
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 deployments and pods are backuped.
a) Backed up deployments 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
How to reproduce, in case of a bug:
Other Notes / Environment Information: (Please give the env information, log link or any
useful information for this issue)
@kalaiselvikks76
The text was updated successfully, but these errors were encountered: