anchor.diff:  place your services in this repository as well. You must configure this repository as the external Maven repository. You cannot configure a separate mirror repository in an immutable environment.
   endif::[]
   ifeval::["{context}"!="openshift-immutable"]
  -. Prepare a Maven release repository to which you can write. The repository must allow read access without authentication. Your OpenShift environment must have access to this repository. You can deploy a Nexus repository manager in the OpenShift environment. For instructions about setting up Nexus on OpenShift, see https://access.redhat.com/documentation/en-us/openshift_container_platform/3.11/html/developer_guide/tutorials#nexus-setting-up-nexus[Setting up Nexus]. Use this repository as a separate mirror repository.
  +. Configure a Maven release repository to which you have write access. The repository must allow read access without authentication and your OpenShift environment must have network access to this repository.
  ++
  +You can deploy a Nexus repository manager in the OpenShift environment. For instructions about setting up Nexus on OpenShift, see https://access.redhat.com/documentation/en-us/openshift_container_platform/3.11/html/developer_guide/tutorials#nexus-setting-up-nexus[Setting up Nexus] in the {OPENSHIFT} 3.11 documentation. 
  +ifeval::["{context}"=="openshift-operator"]
  +The documented procedure is applicable to {OPENSHIFT} version 4.
  +endif::[]
  +Use this repository as a separate mirror repository.
   +
   Alternatively, if you use a custom external repository (for example, Nexus) for your services, you can use the same repository as a mirror repository.
   endif::[]
  
positive.code: {OPENSHIFT} environment
  endif::offline_onprem[]
  does not have outgoing access to the public Internet, you must prepare a Maven repository with a mirror of all the necessary artifacts and make this repository available to your environment.
  
  [NOTE]
  ====
  
negative.code: :offline_onprem:
  endif::[]
  
  ifeval::["{context}"=="openshift-operator"]
  = Preparing for deployment in a restricted network
  You can deploy {PRODUCT} in a restricted network that is not connected to the public Internet. For instructions about operator deployment in a restricted network, see https://access.redhat.com/documentation/en-us/openshift_container_platform/4.3/html/operators/olm-restricted-networks[Using Operator Lifecycle Manager on restricted networks] in {OPENSHIFT} documentation.
  
  [IMPORTANT]
  ====
  In {PRODUCT} {PRODUCT_VERSION}, deployment on restricted networks is for Technology Preview only. For more information on Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Scope].
  ====
  
  In order to use a deployment that does not have outgoing access to the public Internet, you must prepare a Maven repository with a mirror of all the necessary artifacts and make this repository available to your environment.
  endif::[]
  
  ifeval::["{context}"!="openshift-operator"]
  = Preparing a Maven mirror repository for offline use
  
  If your
  