Merge pull request #70110 from stevsmit/OCPBUGS-9446

Updates bare metal configuration docs

Author: stevsmit

modules/installation-registry-storage-block-recreate-rollout-bare-metal.adoc

@@ -8,7 +8,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="installation-registry-storage-block-recreate-rollout-bare-metal_{context}"]
-= Configuring block registry storage
+= Configuring block registry storage for bare metal
 
 To allow the image registry to use block storage types during upgrades as a cluster administrator, you can use the `Recreate` rollout strategy.
 
@@ -21,13 +21,55 @@ If you choose to use a block storage volume with the image registry, you must us
 
 .Procedure
 
-. To set the image registry storage as a block storage type, patch the registry so that it uses the `Recreate` rollout strategy and runs with only one (`1`) replica:
+. Enter the following command to set the image registry storage as a block storage type, patch the registry so that it uses the `Recreate` rollout strategy, and runs with only one (`1`) replica:
 +
 [source,terminal]
 ----
 $ oc patch config.imageregistry.operator.openshift.io/cluster --type=merge -p '{"spec":{"rolloutStrategy":"Recreate","replicas":1}}'
 ----
-+
+
 . Provision the PV for the block storage device, and create a PVC for that volume. The requested block volume uses the ReadWriteOnce (RWO) access mode.
+.. Create a `pvc.yaml` file with the following contents to define a VMware vSphere `PersistentVolumeClaim` object:
++
+[source,yaml]
+----
+kind: PersistentVolumeClaim
+apiVersion: v1
+metadata:
+  name: image-registry-storage <1>
+  namespace: openshift-image-registry <2>
+spec:
+  accessModes:
+  - ReadWriteOnce <3>
+  resources:
+    requests:
+      storage: 100Gi <4>
+----
+<1> A unique name that represents the `PersistentVolumeClaim` object.
+<2> The namespace for the `PersistentVolumeClaim` object, which is `openshift-image-registry`.
+<3> The access mode of the persistent volume claim. With `ReadWriteOnce`, the volume can be mounted with read and write permissions by a single node.
+<4> The size of the persistent volume claim.
+
+.. Enter the following command to create the `PersistentVolumeClaim` object from the file:
++
+[source,terminal]
+----
+$ oc create -f pvc.yaml -n openshift-image-registry
+----
+
++
+. Enter the following command to edit the registry configuration so that it references the correct PVC:
 +
-. Edit the registry configuration so that it references the correct PVC.
+[source,terminal]
+----
+$ oc edit config.imageregistry.operator.openshift.io -o yaml
+----
++
+.Example output
+[source,yaml]
+----
+storage:
+  pvc:
+    claim: <1>
+----
+<1> By creating a custom PVC, you can leave the `claim` field blank for the default automatic creation of an `image-registry-storage` PVC.

modules/installation-registry-storage-block-recreate-rollout-nutanix.adoc

@@ -21,7 +21,7 @@ If you choose to use a block storage volume with the image registry, you must us
 
 .Procedure
 
-. To set the image registry storage as a block storage type, patch the registry so that it uses the `Recreate` rollout strategy and runs with only one (`1`) replica:
+. Enter the following command to set the image registry storage as a block storage type, patch the registry so that it uses the `Recreate` rollout strategy, and runs with only one (`1`) replica:
 +
 [source,terminal]
 ----
@@ -51,14 +51,14 @@ spec:
 <3> The access mode of the persistent volume claim. With `ReadWriteOnce`, the volume can be mounted with read and write permissions by a single node.
 <4> The size of the persistent volume claim.
 
-.. Create the `PersistentVolumeClaim` object from the file:
+.. Enter the following command to create the `PersistentVolumeClaim` object from the file:
 +
 [source,terminal]
 ----
 $ oc create -f pvc.yaml -n openshift-image-registry
 ----
 
-. Edit the registry configuration so that it references the correct PVC:
+. Enter the following command to edit the registry configuration so that it references the correct PVC:
 +
 [source,terminal]
 ----

modules/installation-registry-storage-block-recreate-rollout.adoc

@@ -24,7 +24,7 @@ have more than one replica.
 
 .Procedure
 
-. To set the image registry storage as a block storage type, patch the registry so that it uses the `Recreate` rollout strategy and runs with only `1` replica:
+. Enter the following command to set the image registry storage as a block storage type, patch the registry so that it uses the `Recreate` rollout strategy, and runs with only `1` replica:
 +
 [source,terminal]
 ----
@@ -53,15 +53,15 @@ spec:
 <3> The access mode of the persistent volume claim. With `ReadWriteOnce`, the volume can be mounted with read and write permissions by a single node.
 <4> The size of the persistent volume claim.
 
-.. Create the `PersistentVolumeClaim` object from the file:
+.. Enter the following command to create the `PersistentVolumeClaim` object from the file:
 +
 [source,terminal]
 ----
 $ oc create -f pvc.yaml -n openshift-image-registry
 ----
 
 +
-. Edit the registry configuration so that it references the correct PVC:
+. Enter the following command to edit the registry configuration so that it references the correct PVC:
 +
 [source,terminal]
 ----

modules/persistent-storage-vsphere-dynamic-provisioning-cli.adoc

@@ -33,7 +33,7 @@ spec:
 <2> The access mode of the persistent volume claim. With `ReadWriteOnce`, the volume can be mounted with read and write permissions by a single node.
 <3> The size of the persistent volume claim.
 
-. Create the `PersistentVolumeClaim` object from the file:
+. Enter the following command to create the `PersistentVolumeClaim` object from the file:
 +
 [source,terminal]
 ----