Create Backup and then restore the backup but name that does not contains kahu keyword Deployments.

[sanchitgargg]

Issue/Feature Description:
Testcase Precondition:

1. Kahu project installed in given name-space (test-kahu)
2. All below pods should be up and running:
   a. backup service
   b. Meta service with nfs provider
   c. nfs-server
3. Metadata location is created already
4. Namespace test-ns is created and contains some of the kubernetes resources
   5.Namespace restore-ns is created

Testcase steps:

1. Create below backup CR using kubectl command
   (use kubectl create -f <backup.yaml>)
   apiVersion: kahu.io/v1
   kind: Backup
   metadata:
   name: backup-Kahu-0001
   spec:
   includeNamespaces: [test-ns]
   metadataLocation: nfs
2. Use kubectl describe backup -n test-kahu
3. Get inside nfs server pod and check for the content inside mount path given
   (use command kubectl exec -ti -n test-kahu /bin/sh)
4. 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
   excludeResources:

• name: kahu
  kind: Deployment
  isRegex: true
  Expected Result:

1. 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
2. In step 3, verify that
   a) tar file is created with name of backup
   b) After untar file, 3. In step4, verify that
   a) Backed up all and deployments only without kahu in its name.
   For example:
3. kahu-123
4. 123-kahu
5. 123-kahu-456
   Etc. are not restored up
   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)

@sushanthakumar