Self-Hosted: first set of review feedback, especially make it clearer where to wait for up/down scaling

Author: glaubinix

docs/self-hosted/kubernetes-migration-guide.md

@@ -75,69 +75,100 @@ Please note that any changes made in Private Packagist will now be lost and will
 ## Installing Private Packagist Self-Hosted Kubernetes
 If you haven't done so already, now is the time to follow the [installation guide](./kubernetes.md) to install Private Packagist Self-Hosted Kubernetes.
 
-## Restore application data in Kubernetes
+## Import the application data in Private Packagist Self-Hosted Kubernetes
 
-All commands assume that you are logged in to the server where Private Packagist Self-Hosted Kubernetes is installed,
-your working directory contains the three files generated by the previous steps, and that
-Private Packagist Self-Hosted Kubernetes is installed in the Kubernetes namespace "default".
+All commands assume that you are logged in to the server where Private Packagist Self-Hosted Kubernetes is installed
+and your working directory contains the three files generated by the previous steps.
 
-To avoid any data inconsistency, we highly recommend going through the steps below in order and only restart the application
+If you installed Private Packagist Kubernetes in an existing cluster and are not using the default namespace,
+make sure to run the commands in the correct namespace or switch the namespace before running any of the command.
+
+```
+kubectl config set-context --current --namespace=<namespace-name>
+```
+
+To avoid any data inconsistency, we highly recommend going through the steps below in order and only start the application
 once all the data has been restored.
 
 ### Stop the Private Packagist application
 
 ```
-kubectl scale deployment ui repo worker --replicas 0 -n default
+kubectl scale deployment ui repo worker --replicas 0
 ```
 
-### Restore the PostgreSQL database
+To verify that all ui, repo, and worker pods have been run the command below and verify that the pods don't appear in the list anymore.
+```
+kubectl get pods
+```
+
+### Import the PostgreSQL database
 
 Follow the instructions below to restore the PostgreSQL database in the cluster.
 If you are using your own PostgreSQL instance, use the `packagist_db.sql` file directly to import the data into your instance.
 
 Please note that the backup will overwrite any existing data in the database and any changes you made during setup will be lost.
 
+After each scale command, use `kubectl get pods` again to verify that the postgres pod is in the correct running state.
+
 ```
-kubectl scale statefulset postgres --replicas 0 -n default
-kubectl delete pvc postgres-data-postgres-0 -n default
-kubectl scale statefulset postgres --replicas 1 -n default
-cat packagist_db.sql | kubectl exec -it -n default statefulsets/postgres -- psql -U postgres -d packagist_db
+kubectl scale statefulset postgres --replicas 0
+kubectl delete pvc postgres-data-postgres-0
+kubectl scale statefulset postgres --replicas 1
+cat packagist_db.sql | kubectl exec -it statefulsets/postgres -- psql -U postgres -d packagist_db
 ```
 
-### Restore the Redis database
+### Import the Redis database
 
-Follow the instructions below to restore the Redis database in the cluster.
+Follow the instructions below to restore the Redis database for Private Packagist Self-Hosted without an existing Kubernetes cluster.
 If you are using your own Redis instance, use the `packagist_redis.rdb` file directly to [restore Redis from an RDB file](https://redis.io/learn/guides/import#restore-an-rdb-file) or follow the instructions of your hosted service provider.
+If you are installing Private Packagist Self-Hosted in an existing cluster and aren't planning on using your own Redis then please contact us.
+
+After each scale command, use `kubectl get pods` again to verify that the redis pod is in the correct running state.
 
-Follow these steps if you are using Private Packagist Self-Hosted with an embeded Kubernetes cluster
 ```
-export PV_NAME=$(kubectl get pvc -n default redis-data-redis-0 -ojsonpath='{.spec.volumeName}')
+export PV_NAME=$(kubectl get pvc redis-data-redis-0 -ojsonpath='{.spec.volumeName}')
 kubectl scale statefulset -n default redis --replicas 0
 rm /var/openebs/local/$PV_NAME/appendonly.aof
 cp packagist_redis.rdb /var/openebs/local/$PV_NAME/dump.rdb
-kubectl scale statefulset -n default redis --replicas 1
+kubectl scale statefulset redis --replicas 1
 ```
 
-### Restore the dist and artifact files
+### Import the dist and artifact files
+
+Importing the dist and artifact files requires the UI pods to be back online via the command below. This will take a few seconds.
+You can use the second command to verify once 2/2 pods are running.
+```
+kubectl scale statefulset ui --replicas 1
+kubectl get pods -w
+```
 
 Please note that depending on the size of the `packagist_storage.tar.gz` file and the type of blob storage that you have configured
 it can take several minutes for this command to finish.
 
 ```
-kubectl scale statefulset -n default ui --replicas 1
-kubectl cp -n default packagist_storage.tar.gz ui:/tmp/packagist_storage.tar.gz
-kubectl exec -n default ui /srv/manager/bin/console packagist:self-hosted:migrate-storage import /tmp/packagist_storage.tar.gz && rm /tmp/packagist_storage.tar.gz 
+kubectl cp packagist_storage.tar.gz ui:/tmp/packagist_storage.tar.gz
+kubectl exec ui /srv/manager/bin/console packagist:self-hosted:migrate-storage import /tmp/packagist_storage.tar.gz && rm /tmp/packagist_storage.tar.gz 
+
 ```
 
 ### Start the Private Packagist application
 
-Once your data has been restored. Restart the application, log in to Private Packagist, and verify that your organization
-and packages are there again.
+Once your data has been restored. Start the application:
 
 ```
-kubectl scale deployment ui --replicas 1 -n default
+kubectl scale deployment ui --replicas 1
 ```
 
+This can take a few minutes. You can run the command below to see when all pods are back up and running.
+
+```
+kubectl get pods -w
+```
+
+Once the all pods are back up and running. Log in to Private Packagist and verify that your organization is shown in the UI.
+Ideally, run a `composer update` command in one of your projects to assert that the Composer repository and any of the
+background workers run as expected.
+
 ### Adjust domain names
 
 In case you initially set up Private Packagist Self-Hosted Kubernetes with a different domain name, you can now edit the