anchor.diff:  ====
   If you do not want persistent storage, continue to
   xref:nexus-connecting-to-nexus[Connecting to Nexus]. However, your cached
  -dependencies will be lost if the pod is restarted for any reason.
  +dependencies and any configuration customization will be lost if the pod is
  +restarted for any reason.
   ====
   
  -Create a persistent volume claim (PVC) for Nexus, so that your dependencies
  -will not be lost when the pod running the server terminates. If you do not have
  -administrator access on your cluster, ask your system administrator to create a
  -Read/Write Persistent Volume for you.  Otherwise, read
  -xref:../volumes.adoc#dev-guide-volumes[Managing Volumes in {product-title}] for instructions on
  -creating a persistent volume.
  +Create a persistent volume claim (PVC) for Nexus, so that the cached
  +dependencies are not lost when the pod running the server terminates. PVCs
  +require available persistent volumes (PV) in the cluster. If there are no PVs
  +available and you do not have administrator access on your cluster, ask your
  +system administrator to create a Read/Write Persistent Volume for you.
  +Otherwise, see
  +xref:../../install_config/persistent_storage/index.adoc#install-config-persistent-storage-index[Persistent Storage in {product-title}] for
  +instructions on creating a persistent volume.
   
   Add a PVC to the Nexus deployment configuration.
   
   ----
  -$ oc volumes dc/nexus --remove --confirm
   $ oc volumes dc/nexus --add \
  -	--name 'nexus-pvc' \
  +	--name 'nexus-volume-1' \
   	--type 'pvc' \
   	--mount-path '/sonatype-work/' \
   	--claim-name 'nexus-pv' \
  -	--claim-size '1G'
  +	--claim-size '1G' \
  +	--overwrite
   ----
   
  -This removes the previous ephemeral volume for the deployment config and adds a
  +This removes the previous *emptyDir* volume for the deployment config and adds a
   claim for 1 gigabyte of persistent storage mounted at `/sonatype-work`, which
   is where our dependencies will be stored. Due to the change in configuration,
   the Nexus pod will be redeployed automatically.
  
positive.code: == Additional Resources
  * xref:../../architecture/additional_concepts/networking.adoc#architecture-additional-concepts-networking[Networking Concepts in {product-title}]
  * xref:../volumes.adoc#dev-guide-volumes[Managing Volumes in {product-title}]
  * link:https://blog.openshift.com/improving-build-time-java-builds-openshift/[Improving Build Time of Java Builds on {product-title}]
  * xref:../application_health.adoc#dev-guide-application-health[Application Health]
  * link:https://maven.apache.org/guides/getting-started/index.html[Maven "Getting Started"]
  
negative.code: oc new-app sonatype/nexus
  ----
  
  Create a route by exposing the newly created Nexus service:
  
  ----
  oc expose svc/nexus
  ----
  
  Use *oc get routes* to find the pod's new external address.
  
  ----
  oc get routes
  ----
  
  The output should resemble:
  
  ----
  NAME      HOST/PORT                              PATH      SERVICES   PORT       TERMINATION
  nexus     nexus-myproject.192.168.1.173.xip.io             nexus      8081-tcp  
  ----
  
  Confirm that Nexus is running by navigating your browser to the URL under
  *HOST/PORT*. To sign in to Nexus, the default administrator username is *admin*,
  and the password is *admin123*.
  
  Nexus comes pre-configured for the Central Repository, but you may need others
  for your application.  For many Red Hat images, it is recommended to add the
  *jboss-ga* repository at *_https://maven.repository.redhat.com/ga/_*.
  link:https://books.sonatype.com/nexus-book/reference/config-maven.html[Learn how to add repositories].
  
  [[nexus-using-probes-to-check-for-success]]
  === Using Probes to Check for Success
  
  This is a good time to set up readiness and liveness probes. These will
  