Incorporated review suggestions

Author: hmanwani-rh

modules/admin/proc-mount-directories-pvcs.adoc

@@ -0,0 +1,64 @@
+[id="proc-mount-directories-pvcs_{context}"]
+= Mounting directories from pre-created PVCs
+
+Starting from `v1alpha3`, you can mount directories from pre-created PersistentVolumeClaims (PVCs) using the `spec.application.extraFiles.pvcs` field.
+
+.Prerequisites
+* You have understanding of the mounting logic:
+** If `spec.application.extraFiles.pvcs[].mountPath` is defined, the PVC is mounted to the specified path.
+** If `spec.application.extraFiles.pvcs[].mountPath` is not defined, the PVC is mounted under the path specified in `spec.application.extraFiles.mountPath/`.
+** If neither `mountPath` is defined, the PVC defaults to `/opt/app-root/src` or you can use {product-very-short} container working directory (if defined).
+
+.Procedure
+. Define the PVCs using the following YAML example:
++
+--
+.Example YAML file to define PVCs
+[source,yaml]
+----
+apiVersion: v1  
+kind: PersistentVolumeClaim  
+metadata:  
+  name: myclaim1  
+spec:  
+  accessModes:  
+    - ReadWriteOnce  
+  resources:  
+    requests:  
+      storage: 2Gi  
+---  
+apiVersion: v1  
+kind: PersistentVolumeClaim  
+metadata:  
+  name: myclaim2  
+spec:  
+  accessModes:  
+    - ReadWriteOnce  
+  resources:  
+    requests:  
+      storage: 2Gi 
+----
+--
+
+. Use the following configuration to specify how the PVCs are mounted in the container:
++
+--
+.Example configuration for mounting PVCs in a container
+[source,yaml]
+----
+spec:  
+  application:  
+    extraFiles:  
+      mountPath: /my/path  
+      pvcs:  
+        - name: myclaim1  
+        - name: myclaim2  
+          mountPath: /vol/my/claim
+----
+--
+
+.Verification
+Based on the configuration, the following directories are mounted in the container:
+
+* `/my/path/myclaim1`
+* `/vol/my/claim`

modules/admin/proc-rhdh-deployment-config.adoc

@@ -97,58 +97,6 @@ spec:
                 persistentVolumeClaim:
                   claimName: dynamic-plugins-root
 ----
-
-Starting from v1alpha3 (Operator version 0.4.0), you can mount directories from pre-created PVCs using the `spec.application.extraFiles.pvcs` field. PVCs are mounted as directories to the container's path, based on the following logic:
-
-* If `spec.application.extraFiles.pvcs[].mountPath` is defined, the PVC is mounted to the specified path.
-* If `spec.application.extraFiles.pvcs[].mountPath` is not defined, the PVC is mounted under `spec.application.extraFiles.mountPath/`.
-* If neither is defined, the PVC defaults to `/opt/app-root/src`.
-
-.Example PVC objects in the namespace
-[source,yaml]
-----
-apiVersion: v1
-kind: PersistentVolumeClaim
-metadata:
-  name: myclaim1
-spec:
-  accessModes:
-    - ReadWriteOnce
-  resources:
-    requests:
-      storage: 2Gi
----
-apiVersion: v1
-kind: PersistentVolumeClaim
-metadata:
-  name: myclaim2
-spec:
-  accessModes:
-    - ReadWriteOnce
-  resources:
-    requests:
-      storage: 2Gi
-----
-
-The PVCs in the previous example can be mounted to the container as follows:
-
-.Example PVCs mounted to the container
-[source,yaml]
-----
-spec:
-  application:
-    extraFiles:
-      mountPath: /my/path
-      pods:
-        - name: myclaim1
-        - name: myclaim2
-          mountPath: /vol/my/claim
-----
-
-As a result, the following directories are mounted in the container:
-
-* `/my/path/myclaim1`
-* `/vol/my/claim`
 --
 
 `cpu` request::

titles/admin-rhdh/title-admin.adoc

@@ -40,4 +40,5 @@ include::assemblies/assembly-admin-templates.adoc[leveloffset=+1]
 include::assemblies/assembly-techdocs-plugin.adoc[leveloffset=+1]
 
 // RHDH Operator deployment
-include::modules//admin/proc-rhdh-deployment-config.adoc[leveloffset=+1]
+include::modules/admin/proc-rhdh-deployment-config.adoc[leveloffset=+1]
+include::modules/admin/proc-mount-directories-pvcs.adoc[leveloffset=+2]