docs(installing_deis): remove in-place upgrade documentation

Author: carmstrong

docs/installing_deis/upgrading-deis.rst

@@ -166,82 +166,5 @@ Once you've finished migrating over to the new cluster, just update your wildcar
 point at your new load balancer. The application names are all the same, so no CNAME
 modification needs to occur.
 
-In-place upgrade
-----------------
-
-This upgrade method involves shutting down the existing cluster, upgrading Deis components, and then
-restarting them. It has the benefit of preserving existing data, but has the caveat that it results
-in cluster downtime.
-
-Stop components
-^^^^^^^^^^^^^^^
-The Makefile has the ability to stop all Deis copmonents. Once this occurs, all apps will
-be unresponsive.
-
-.. code-block:: console
-
-    dev $ make stop
-
-You can ``make status`` to ensure that all services are stopped.
-
-Export data containers
-^^^^^^^^^^^^^^^^^^^^^^
-Four Deis components, builder, database, logger, and registry, run separate containers to store
-their stateful data. We export these as tarballs before upgrading the containers.
-
-.. code-block:: console
-
-    dev $ fleetctl ssh deis-builder.service
-    core $ sudo docker export deis-builder-data > /home/core/deis-builder-data-backup.tar
-    dev $ fleetctl ssh deis-database.service
-    core $ sudo docker export deis-database-data > /home/core/deis-database-data-backup.tar
-    dev $ fleetctl ssh deis-logger.service
-    core $ sudo docker export deis-logger-data > /home/core/deis-logger-data-backup.tar
-    dev $ fleetctl ssh deis-registry.service
-    core $ sudo docker export deis-registry-data > /home/core/deis-registry-data-backup.tar
-
-Upgrade Deis client and fleetctl
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The latest Deis client should be installed. You can either use pip or download a pre-compiled binary.
-See the release notes or the release's README for a link to the latest client.
-
-Also, new Deis releases frequently require upgrades to the fleetctl client. Again, see the
-release notes for the new release to see if an upgrade is necessary.
-
-Upgrade components
-^^^^^^^^^^^^^^^^^^
-Now we instruct all servers to download the release's Docker containers. This will take some time...
-
-.. code-block:: console
-
-    dev $ make pull
-
-Import data containers
-^^^^^^^^^^^^^^^^^^^^^^
-We need to reimport the saved data containers we exported earlier.
-
-.. code-block:: console
-
-    dev $ fleetctl ssh deis-builder.service
-    core $ cat /home/core/deis-builder-data-backup.tar | sudo docker import - deis-builder-data
-    dev $ fleetctl ssh deis-database.service
-    core $ cat /home/core/deis-database-data-backup.tar | sudo docker import - deis-database-data
-    dev $ fleetctl ssh deis-logger.service
-    core $ cat /home/core/deis-logger-data-backup.tar | sudo docker import - deis-logger-data
-    dev $ fleetctl ssh deis-registry.service
-    core $ cat /home/core/deis-registry-data-backup.tar | sudo docker import - deis-registry-data
-
-Start the cluster
-^^^^^^^^^^^^^^^^^
-Again, the Makefile takes care of this logic for us:
-
-.. code-block:: console
-
-    dev $ make run
-
-Test
-^^^^
-Ensure all applications function as expected.
-
 .. _`#710`: https://github.com/deis/deis/issues/710
 .. _`#467`: https://github.com/deis/deis/issues/467