cleaning-crio-storage: update docs to protect against removing network plugins first

crictl is not smart enough to wait to remove the network plugin pods first. To work around this, the
caller must remove non-HostNetwork pods first, then remove the HostNetwork ones.

Signed-off-by: Peter Hunt~ <[email protected]>

Author: haircommander

modules/cleaning-crio-storage.adoc

@@ -69,6 +69,15 @@ $ sudo -i
 ----
 +
 . Stop the containers and pods:
+
+.. Use the following command to stop the pods that are not in the `HostNetwork`. They must be removed first because their removal relies on the networking plugin pods, which are in the `HostNetwork`.
+[source, terminal]
++
+----
+.. for pod in $(crictl pods -q); do if [[ "$(crictl inspectp $pod | jq -r .status.linux.namespaces.options.network)" != "NODE" ]]; then crictl rmp -f $pod; fi; done
+----
+
+.. Stop all other pods:
 [source, terminal]
 +
 ----