Merge pull request #103 from arschles/move-gcs

doc(object-storage): move the GCS section to a more global area

Author: arschles

src/installing-workflow/configuring-object-storage.md

@@ -13,10 +13,16 @@ These components are flexible and can work out of the box with almost any system
 
 Note: object storage configuration has not been standardized across all components in our beta release. As such, configuration instructions differ for each component. We plan to remediate this problem in our next release. Please see our [deis/deis#4966](https://github.com/deis/deis/issues/4966) for our progress on that work.
 
-# Minio
+## Minio
 
 Additionally, Deis ships with a [Minio](http://minio.io) [component](https://github.com/deis/minio). This component runs as a Kubernetes service, and the components listed above are configured to automatically look for that service and use it as object storage if it's available.
 
+## Google Cloud Storage
+
+[Google Cloud Storage](https://cloud.google.com/storage/) (GCS) can interoperate with the S3 API using a feature called [interoperability](https://cloud.google.com/storage/docs/interoperability). If you choose to use GCS for object storage, you'll have to turn on this interoperability mode. In order to do so, please follow the steps in the [GCS migration documentation](https://cloud.google.com/storage/docs/migrating?hl=en_US#migration-simple).
+
+We recommend storing these and all other credentials as Kubernetes secrets. See the below sections for details on configuring each component for details.
+
 # Configuring the Deis Components
 
 Every Deis component that relies on object storage relies on the following two inputs for configuration:
@@ -64,14 +70,6 @@ Note - to base64 encode your credentials, you can use the `base64` tool on most
 echo $MY_ACCESS_KEY | base64
 ```
 
-### A Note on Google Cloud Storage
-
-Google Cloud Storage (GCS) can interoperate with the S3 API using a feature called [interoperability](https://cloud.google.com/storage/docs/interoperability). If you choose to use GCS for object storage, you'll have to turn on this interoperability mode. In order to do so, please follow the steps at https://cloud.google.com/storage/docs/migrating?hl=en_US#migration-simple.
-
-When you're done, please set the `DEIS_OUTSIDE_STORAGE` environment variable to `storage.googleapis.com`, and ensure the keys that you created (as part of the previous paragraph) are in the correct locations on the filesystem.
-
-Reminder: We recommend storing these and all other credentials as Kubernetes secrets. See the "Configuring Deis Components" section above for more details and examples.
-
 ## [deis/slugbuilder](https://github.com/deis/slugbuilder)
 
 ### Environment Variables
@@ -209,7 +207,7 @@ Connection details to minio are configured via `DEIS_MINIO_SERVICE_HOST` and `DE
 
 If the `DATABASE_STORAGE` backend is configured as "s3", the database will receive its credentials from `/var/run/secrets/deis/objectstore/creds/`. This is generated automatically (as part of the `helm generate` command) based on the configuration options given in the https://github.com/deis/charts/blob/master/workflow-dev/tpl/objectstorage.toml file.
 
-### Google Cloud Storage (S3 Compatibility Mode)
+### Google Cloud Storage (Interoperability Mode)
 
 If the `DATABASE_STORAGE` backend is configured as "gcs", the database will receive its credentials from `/var/run/secrets/deis/database/creds/`. This is generated based on the configuration options given in the https://github.com/deis/charts/blob/master/workflow-dev/manifests/deis-minio-secret-user.yaml file. The access key and secret key must be `base64` encoded.