Doc operator resources and automated PVC copy

docs/2._Development/Helm/1-create-helm-operator.md

@@ -43,6 +43,22 @@ permissions to manage is to `helm template` your Helm chart and grep the output
 helm template helm-charts/nexus-cern | egrep -e '^apiVersion' -e '^kind:'
 ```
 
+## Set up resources for the operator pod
+
+Default resources will almost certainly be insufficient for the operator, it will run out of memory when watching resources.
+
+Locate the TODO in `config/manager/manager.yaml` and set custom resources (adjust from observed values once the operator is running)
+
+```yaml
+        resources:
+              requests:
+                cpu: "100m"
+                memory: "256Mi"
+              limits:
+                cpu: "2"
+                memory: "1Gi"
+```
+
 ## Set up CI
 
 Use the following `.gitlab-ci.yml`, updating `IMAGE_TAG_BASE`.

docs/99._CookBook/copy-files-manually-between-pvcs.md

-# Copy files manually between PVCs
+# Copy files between PVCs
 
 One of the common operations to perform within a migration is to move files (assets) between the old instance and the new one.
 
+## Semi-automated process to copy files from OKD3 to OKD4
+
+For semi-automated migrations to app-catalogue, one can use this script from paas-migration: <https://gitlab.cern.ch/paas-tools/paas-migration/-/tree/master/migration/rsync-pvc-contents.sh>
+
+See example usage in <https://gitlab.cern.ch/paas-tools/paas-migration/-/tree/master/migration/migrate-nexus.sh>
+
+## Manual process to copy files from OpenShift 3 to OKD4
+
 In brief, this can be easily done by provisioning a temporary pod, mount both (or several, depending the needs) volumes, and copy files over.
 
 In the following example, let's copy files from an instance in OKD3 to OKD4. Note that this procedure can be also applied to OKD4 -> OKD4 if needed.
@@ -9,8 +17,6 @@ In the following example, let's copy files from an instance in OKD3 to OKD4. Not
 !!! info
     To perform such operations, the performer user must belong to the `openshift-admins` e-group, having administrator permissions to the targeted clusters. As a consequence of belonging to the `openshift-admins` e-group, the performer user will have also access to the Openstack projects, also needed to fetch the appropriate access keys, etc.
 
-## Copy files from OpenShift 3 to OKD4
-
 ```bash
 # Login as admtrobo into OKD3
 oc login --server=https://openshift.cern.ch -u <username>