Docs fixes

Signed-off-by: Marcin Ciszak <[email protected]>

Author: marcinc

docs/user/backup.md

@@ -156,9 +156,9 @@ spec:
   schedule: '*/30 * * * *'
   backupTemplate:
     executor:
-      provider: mysqldump
-      databases:
-        - test
+      mysqldump:
+        databases:
+          - test
     storageProvider:
       s3:
         endpoint: ocitenancy.compat.objectstorage.ociregion.oraclecloud.com

docs/user/clusters.md

@@ -183,6 +183,7 @@ apiVersion: mysql.oracle.com/v1alpha1
 kind: Cluster
 metadata:
   name: mysql-cluster-with-config
+spec:
   members: 3
   config:
     name: mycnf
@@ -198,6 +199,20 @@ apiVersion: mysql.oracle.com/v1alpha1
 kind: Cluster
 metadata:
   name: mysql-cluster-with-custom-serverid
+spec:
   members: 3
   baseServerId: 42
 ```
+
+### Create a cluster with specific version of MySQL Server
+
+By default, the MySQL Operator starts a cluster with MySQL Server version set to minimum supported version defined by the Operator. This can be overriden in the cluster spec given the version used is equal to or higher than minimum supported version.
+
+```yaml
+apiVersion: mysql.oracle.com/v1alpha1
+kind: Cluster
+metadata:
+  name: mysql-cluster-with-custom-server-version
+spec:
+  version: 8.0.12
+```

docs/user/restore.md

@@ -5,8 +5,8 @@ The MySQL Operator supports the notion of restoring a cluster from an existing b
 ## On-demand restores
 
 You can request a restore from a previous backup at any time by submitting a
-Restore custom resource to the operator. The backupRef is the name of the
-backup that you wish to restore, and the clusterRef is the name of the
+Restore custom resource to the operator. The backup is the name of the
+backup that you wish to restore, and the cluster is the name of the
 destination cluster of the restore operation.
 
 ```yaml
@@ -15,8 +15,8 @@ kind: Restore
 metadata:
   name: example-restore
 spec:
-  clusterRef:
+  cluster:
     name: mycluster
-  backupRef:
+  backup:
     name: mysql-backup
 ```