Update Percona XtraDB Cluster Backup And Restore (#308)

Signed-off-by: SK Ali Arman <arman@appscode.com>

Author: sheikh-arman

docs/addons/percona-xtradb/cluster/examples/backupconfiguration.yaml

@@ -6,7 +6,7 @@ metadata:
 spec:
   schedule: "*/5 * * * *"
   task:
-    name: perconaxtradb-backup-5.7
+    name: perconaxtradb-backup-8.0
   repository:
     name: gcs-repo-xtradb-cluster
   target:

docs/addons/percona-xtradb/cluster/examples/restored-xtradb-cluster.yaml

@@ -4,7 +4,7 @@ metadata:
   name: restored-xtradb-cluster
   namespace: demo
 spec:
-  version: "5.7-cluster"
+  version: "8.0.40"
   replicas: 3
   authSecret:
     name: sample-xtradb-cluster-auth

docs/addons/percona-xtradb/cluster/examples/restoresession.yaml

@@ -5,9 +5,14 @@ metadata:
   namespace: demo
 spec:
   task:
-    name: perconaxtradb-restore-5.7
+    name: perconaxtradb-restore-8.0
   repository:
     name: gcs-repo-xtradb-cluster
+  runtimeSettings:
+    container:
+      securityContext:
+        runAsGroup: 1001
+        runAsUser: 1001
   target:
     replicas: 3
     ref:

docs/addons/percona-xtradb/cluster/examples/sample-xtradb-cluster.yaml

@@ -4,7 +4,7 @@ metadata:
   name: sample-xtradb-cluster
   namespace: demo
 spec:
-  version: "5.7-cluster"
+  version: "8.0.40"
   replicas: 3
   storageType: Durable
   storage:

docs/addons/percona-xtradb/cluster/index.md

@@ -59,7 +59,7 @@ metadata:
   name: sample-xtradb-cluster
   namespace: demo
 spec:
-  version: "5.7-cluster"
+  version: "8.0.40"
   replicas: 3
   storageType: Durable
   storage:
@@ -86,7 +86,7 @@ Let's check if the database is ready to use,
 ```bash
 $  kubectl get px -n demo sample-xtradb-cluster
 NAME                    VERSION       STATUS    AGE
-sample-xtradb-cluster   5.7-cluster   Ready     7m46s
+sample-xtradb-cluster   8.0.40        Ready     7m46s
 ```
 
 The database is `Ready`. Verify that KubeDB has created a Secret and a Service for this database using the following commands,
@@ -159,7 +159,7 @@ spec:
   secret:
     name: sample-xtradb-cluster-auth
   type: kubedb.com/perconaxtradb
-  version: "5.7-cluster"
+  version: "8.0.40"
 ```
 
 Stash uses the AppBinding CRD to connect with the target database. It requires the following two fields to be set in the AppBinding's `.spec` section.
@@ -342,7 +342,7 @@ metadata:
 spec:
   schedule: "*/5 * * * *"
   task:
-    name: perconaxtradb-backup-5.7
+    name: perconaxtradb-backup-8.0
   repository:
     name: gcs-repo-xtradb-cluster
   target:
@@ -376,7 +376,7 @@ If everything goes well, the phase of the `BackupConfiguration` should be `Ready
 ```bash
 $ kubectl get backupconfiguration -n demo
 NAME                           TASK                       SCHEDULE      PAUSED   PHASE      AGE
-sample-xtradb-cluster-backup   perconaxtradb-backup-5.7   */5 * * * *            Ready      11s
+sample-xtradb-cluster-backup   perconaxtradb-backup-8.0   */5 * * * *            Ready      11s
 ```
 
 
@@ -447,7 +447,7 @@ Now, wait for a moment. Stash will pause the BackupConfiguration. Verify that th
 ```console
 $ kubectl get backupconfiguration -n demo sample-xtradb-cluster-backup
 NAME                           TASK                          SCHEDULE      PAUSED   PHASE   AGE
-sample-xtradb-cluster-backup   perconaxtradb-backup-5.7      */5 * * * *   true     Ready   50m
+sample-xtradb-cluster-backup   perconaxtradb-backup-8.0      */5 * * * *   true     Ready   50m
 ```
 
 Notice the `PAUSED` column. Value `true` for this field means that the BackupConfiguration has been paused.
@@ -468,7 +468,7 @@ metadata:
   name: restored-xtradb-cluster
   namespace: demo
 spec:
-  version: "5.7-cluster"
+  version: "8.0.40"
   replicas: 3
   authSecret:
     name: sample-xtradb-cluster-auth
@@ -497,7 +497,7 @@ If you check the database status, you will see it is stuck in **`Provisioning`**
 ```bash
 $ kubectl get px -n demo restored-xtradb-cluster
 NAME                      VERSION       STATUS         AGE
-restored-xtradb-cluster   5.7-cluster   Provisioning   4m10s
+restored-xtradb-cluster   8.0.40   Provisioning   4m10s
 ```
 
 #### Create RestoreSession
@@ -516,9 +516,14 @@ metadata:
   namespace: demo
 spec:
   task:
-    name: perconaxtradb-restore-5.7
+    name: perconaxtradb-restore-8.0
   repository:
     name: gcs-repo-xtradb-cluster
+  runtimeSettings:
+    container:
+      securityContext:
+        runAsGroup: 1001
+        runAsUser: 1001
   target:
     replicas: 3
     ref:
@@ -584,9 +589,9 @@ At first, check if the database has gone into **`Running`** state,
 ```bash
 $ kubectl get px -n demo restored-xtradb-cluster --watch
 NAME                      VERSION       STATUS         AGE
-restored-xtradb-cluster   5.7-cluster   Provisioning   3m36s
-restored-xtradb-cluster   5.7-cluster   Provisioning   4m4s
-restored-xtradb-cluster   5.7-cluster   Ready          4m4s
+restored-xtradb-cluster   8.0.40   Provisioning   3m36s
+restored-xtradb-cluster   8.0.40   Provisioning   4m4s
+restored-xtradb-cluster   8.0.40   Ready          4m4s
 ```
 
 Now, find out the database Pod,