diff --git a/modules/developer_guide/pages/openshift.adoc b/modules/developer_guide/pages/openshift.adoc
index 7351583..c3ec6f0 100644
--- a/modules/developer_guide/pages/openshift.adoc
+++ b/modules/developer_guide/pages/openshift.adoc
@@ -82,20 +82,40 @@ configurations that won't work.
 You will likely need (at a minimum) the following objects:
 
 * A
-https://docs.openshift.com/container-platform/4.14/cicd/builds/understanding-buildconfigs.html[BuildConfig]
+https://docs.openshift.com/container-platform/4.15/cicd/builds/understanding-buildconfigs.html[BuildConfig]
 - This defines how your container is built.
 * An
-https://docs.openshift.com/container-platform/4.14/openshift_images/image-streams-manage.html[ImageStream]
+https://docs.openshift.com/container-platform/4.15/openshift_images/image-streams-manage.html[ImageStream]
 - This references a "stream" of container images and lets you trigger
 deployments or image builds based on changes in a stream.
 * A
-https://docs.openshift.com/container-platform/4.14/applications/deployments/what-deployments-are.html[Deployment]
+https://docs.openshift.com/container-platform/4.15/applications/deployments/what-deployments-are.html[Deployment]
 - This defines how your container is deployed (how many replicas, what
 ports are available, etc)
 - Note: DeploymentConfigs are deprecated, do not use them!
 * A
-https://docs.openshift.com/container-platform/4.14/applications/connecting_applications_to_services/getting-started-with-service-binding.html[Service]
+https://docs.openshift.com/container-platform/4.15/applications/connecting_applications_to_services/getting-started-with-service-binding.html[Service]
 - An internal load balancer that routes traffic to your pods.
 * A
-https://docs.openshift.com/container-platform/4.14/networking/routes/route-configuration.html[Route]
+https://docs.openshift.com/container-platform/4.15/networking/routes/route-configuration.html[Route]
 - This exposes a Service as a host name.
+* Storage https://docs.openshift.com/container-platform/4.15/storage/index.html[Storage]
+- On the Fedora Infra clusters in both staging and production, an automated storage provisioning system is in place. To access simply create a PVC:
+
+----
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: PVCNAME-UPDATE
+spec:
+  volumeName: PVCNAME-VOL-UPDATE
+  accessModes:
+  - ReadWriteOnce
+  resources:
+    requests:
+      storage: 10Gi
+  storageClassName: 'ocs-storagecluster-cephfs'
+  volumeMode: Filesystem
+----
+
+