anchor.diff:    serviceNetworkCIDR: 172.30.0.0/16
   ----
   ====
  +
  +[[upgrade-playbook]]
  +== Automated Upgrade Playbook
  +ifdef::openshift-enterprise[]
  +Starting with OpenShift 3.0.2
  +endif::[]
  +ifdef::openshift-origin[]
  +Starting with Origin 1.0.6
  +endif::[]
  +if you have installed via the advanced installer and you have your inventory file
  +available you may use the upgrade playbook to automate the upgrade process. This
  +playbook will perform the following steps for you:
  +
  + * Applies latest configuration by re-running the installation playbook
  + * Upgrade and restart master services
  + * Upgrade and restart node services
  + * Applies the latest cluster policies
  + * Updates the default router if one exists
  + * Updates the default registry if one exists
  + * Updates image streams and quickstarts
  +
  +[NOTE]
  +====
  +The upgrade playbook will re-run cluster configuration steps and any settings
  +that are not stored in your inventory file will be overwritten. A backup of any
  +files changed will be made and you should carefully review the differences
  +to ensure that your environment is configured as expected.
  +====
  +
  +=== Using the upgrade playbook
  +Ensure that you have the latest ansible code checked out and run the playbook
  +utilizing the default ansible-hosts file located in _/etc/ansible/hosts_. If
  +your hosts file is located somewhere else add the `-i` flag to specify the
  +location.
  +
  +----
  +# cd ~/openshift-ansible
  +# git pull https://github.com/openshift/openshift-ansible master
  +# ansible-playbook playbooks/adhoc/upgrades/upgrade.yaml
  +----
  +
  +Verify that all nodes are marked as ready and that you're running the expected
  +versions of the docker-registry and router.
  +
  +----
  +# oc get nodes
  +NAME                      LABELS                                                           STATUS
  +master.example.com   kubernetes.io/hostname=master.example.com,region=infra,zone=default   Ready
  +node1.example.com    kubernetes.io/hostname=node1.example.com,region=primary,zone=east     Ready
  +# oc get -n default dc/router -o json | grep \"image\"
  +    "image": "openshift3/ose-haproxy-router:v3.0.2.0",
  +# oc get -n default dc/docker-registry -ojson | grep \"image\"
  +    "image": "openshift3/ose-docker-registry:v3.0.2.0",
  +----
  +
  +After upgrading you may wish to use the experimental diagnostics tool to look for common issues.
  +
  +----
  +# openshift ex diagnostics
  +...
  +[Note] Summary of diagnostics execution (version v3.0.2.0-6-g863e73a):
  +[Note] Completed with no errors or warnings seen.
  +----
  
positive.code: 
  [[upgrading-nodes]]
  
  == Upgrading Nodes
  After upgrading your masters, you can upgrade your nodes. When restarting the
  *openshift-node* service, there will be a brief disruption of outbound network
  connectivity from running pods to services while the
  
negative.code: 
  [[importing-the-latest-images]]
  
  === Importing the Latest Images
  After link:#updating-the-default-image-streams-and-templates[updating the
  default image streams], you may also want to ensure that the images within those
  streams are updated. For each image stream in the default *openshift* project,
  