anchor.diff:  you may be required to perform certain steps and key points during the standard
   upgrade process described earlier in this topic.
   
  +ifdef::openshift-enterprise[]
  +[NOTE]
  +====
  +This section will also be updated as asynchronous errata are released for
  +OpenShift Enterprise 3.1 with any additional instructions that are required.
  +====
  +
  +See the link:../release_notes/ose_3_1_release_notes.html[OpenShift Enterprise 3.1
  +Release Notes] to review the latest release notes.
  +
  +[[openshift-enterprise-3-1-0]]
  +==== OpenShift Enterprise 3.1.0
  +
  +After finishing the link:#manual-upgrades[standard manual upgrade steps],
  +perform the following additional steps specific to OpenShift Enterprise 3.1.0 to
  +fully complete the upgrade.
  +
  +*Removing Support for the v1beta3 API*
  +
  +Update the *_/etc/origin/master/master-config.yml_* file on each master and
  +remove *v1beta3* from the `*apiLevels*` and `*kubernetesMasterConfig.apiLevels`*
  +parameters.
  +
  +*Create Symlinks for New Directories*
  +
  +Some directories were renamed from *openshift* to *origin*, so create the
  +following symlinks:
  +
  +----
  +# ln -s /var/lib/openshift /var/lib/origin
  +# ln -s /etc/openshift /etc/origin
  +----
  +
  +*Create and Add Master Proxy Client Certificates*
  +
  +Create *_/etc/origin/master/master.proxy-client.{crt,key}_* certificates:
  +
  +====
  +----
  +# cd /etc/origin/master/
  +# oadm ca create-master-certs --cert-dir=/etc/origin/master/ \
  +            --master=https://<internal-master-fqdn>:8443 \
  +            --public-master=https://<external-master-fqdn>:8443 \
  +            --hostnames=<external-master-fqdn>,<internal-master-fqdn>,localhost,127.0.0.1,172.17.42.1,kubernetes.default.local \
  +            --overwrite=false
  +----
  +====
  +
  +Add the master proxy client certificates to the
  +*_/etc/origin/master/master-config.yml_* file on each master:
  +
  +====
  +----
  +  - kubernetesMasterConfig.proxyClientInfo.certFile: master.proxy-client.crt
  +  - kubernetesMasterConfig.proxyClientInfo.keyFile: master.proxy-client.key
  +----
  +====
  +endif::[]
  +
   ifdef::openshift-origin[]
   For OpenShift Origin, see the
  -link:https://github.com/openshift/origin/releases[Releases page] on GitHub  to
  +link:https://github.com/openshift/origin/releases[Releases page] on GitHub to
   review the latest release notes.
  -endif::[]
  -ifdef::openshift-enterprise[]
  -See the link:../whats_new/ose_3_0_release_notes.html[OpenShift Enterprise 3.0
  -Release Notes] to review the latest release notes.
  -endif::[]
  -
  -ifdef::openshift-enterprise[]
  -[[openshift-enterprise-3-0-1-0]]
  -
  -=== OpenShift Enterprise 3.0.1.0
  -
  -The following steps are required for the
  -link:../whats_new/ose_3_0_release_notes.html#ose-3-0-1-0[OpenShift Enterprise
  -3.0.1.0 release].
  -endif::[]
  -ifdef::openshift-origin[]
  +
   [[openshift-origin-1-0-4]]
  -
  -=== OpenShift Origin 1.0.4
  +==== OpenShift Origin 1.0.4
   
   The following steps are required for the
   https://github.com/openshift/origin/releases/tag/v1.0.4[OpenShift Origin 1.0.4
   release].
  -endif::[]
   
   *Creating a Service Account for the Router*
   
  
positive.code: 
  [[manual-upgrades]]
  == Upgrading Manually
  As an alternative to using the link:#upgrade-playbook[automated upgrade
  playbook], you can manually upgrade your OpenShift cluster. To manually upgrade
  without disruption, it is important to upgrade each component as documented in
  this topic. Before you begin your upgrade, familiarize yourself with the entire
  procedure. link:#additional-instructions-per-release[Specific releases] may
  require additional steps to be performed at key points during the standard
  upgrade process.
  
  [[upgrading-masters]]
  
  === Upgrading Masters
  ifdef::openshift-origin[]
  Upgrade your masters first. On each master host, upgrade the *origin-master*
  
negative.code: endif::[]
  
  [[updating-policy-definitions]]
  === Updating Policy Definitions
  
  After a cluster upgrade, the recommended
  link:../architecture/additional_concepts/authorization.html#roles[default
  cluster roles] may have been updated. To check if an update is recommended for
  