Memorystore (redis) as an option (GoogleCloudPlatform#505)

* memorystore option doc

* fix sed command

* fix typo

README.md

@@ -121,6 +121,7 @@ gcloud container clusters delete onlineboutique \
 - **Istio**: [See these instructions.](docs/service-mesh.md)
 - **Anthos Service Mesh**: ASM requires Workload Identity to be enabled in your GKE cluster. [See the workload identity instructions](docs/workload-identity.md) to configure and deploy the app. Then, use the [service mesh guide](/docs/service-mesh.md).
 - **non-GKE clusters (Minikube, Kind)**: see the [Development Guide](/docs/development-guide.md)
+- **Memorystore**: [See these instructions](/docs/memorystore.md) to replace the in-cluster `redis` database with hosted Google Cloud Memorystore (redis).
 
 
 ## Architecture
@@ -174,15 +175,18 @@ If you would like to contribute features or fixes to this app, see the [Developm
 
 ## Demos featuring Online Boutique
 
-- [Google Cloud Next'18 London – Keynote](https://youtu.be/nIq2pkNcfEI?t=3071)
-  showing Stackdriver Incident Response Management
+- [Take the first step toward SRE with Cloud Operations Sandbox](https://cloud.google.com/blog/products/operations/on-the-road-to-sre-with-cloud-operations-sandbox)
+- [Deploying the Online Boutique sample application on Anthos Service Mesh](https://cloud.google.com/service-mesh/docs/onlineboutique-install-kpt)
+- [Anthos Service Mesh Workshop: Lab Guide](https://codelabs.developers.google.com/codelabs/anthos-service-mesh-workshop)
+- [KubeCon EU 2019 - Reinventing Networking: A Deep Dive into Istio's Multicluster Gateways - Steve Dake, Independent](https://youtu.be/-t2BfT59zJA?t=982)
 - Google Cloud Next'18 SF
   - [Day 1 Keynote](https://youtu.be/vJ9OaAqfxo4?t=2416) showing GKE On-Prem
-  - [Day 3 – Keynote](https://youtu.be/JQPOPV_VH5w?t=815) showing Stackdriver
+  - [Day 3 Keynote](https://youtu.be/JQPOPV_VH5w?t=815) showing Stackdriver
     APM (Tracing, Code Search, Profiler, Google Cloud Build)
   - [Introduction to Service Management with Istio](https://www.youtube.com/watch?v=wCJrdKdD6UM&feature=youtu.be&t=586)
-- [KubeCon EU 2019 - Reinventing Networking: A Deep Dive into Istio's Multicluster Gateways - Steve Dake, Independent](https://youtu.be/-t2BfT59zJA?t=982)
+- [Google Cloud Next'18 London – Keynote](https://youtu.be/nIq2pkNcfEI?t=3071)
+  showing Stackdriver Incident Response Management
 
 ---
 
-This is not an official Google project.
+This is not an official Google project.

docs/memorystore.md

@@ -0,0 +1,94 @@
+# Memorystore (redis) + OnlineBoutique
+
+This guide contains instructions for overriding the default in-cluster `redis` database for `cartservice` with Memorystore (redis).
+
+Important notes:
+- You can connect to a Memorystore (redis) instance from GKE clusters that are in the same region and use the same network as your instance.
+- You cannot connect to a Memorystore (redis) instance from a GKE cluster without VPC-native/IP aliasing enabled.
+
+![Architecture diagram with Memorystore](./img/memorystore.png)
+
+## Steps
+
+1. Create a GKE cluster with VPC-native/IP aliasing enabled.
+
+```sh
+PROJECT_ID="<your-project-id>"
+ZONE="<your-GCP-zone>"
+REGION="<your-GCP-region>"
+
+gcloud container clusters create onlineboutique \
+    --project=${PROJECT_ID} \
+    --zone=${ZONE} \
+    --machine-type=e2-standard-2 \
+    --enable-ip-alias
+```
+
+2. Enable the Memorystore (redis) service on your project.
+
+```sh
+gcloud services enable redis.googleapis.com --project=${PROJECT_ID}
+```
+
+3. Create the Memorystore (redis) instance. 
+
+```sh
+gcloud redis instances create redis-cart --size=1 --region=${REGION} --zone=${ZONE} --redis-version=redis_5_0 --project=${PROJECT_ID}
+```
+
+After a few minutes, you will see the `STATUS` as `READY` when your Memorystore instance will be successfully provisioned:
+
+```sh
+gcloud redis instances list --region ${REGION}
+```
+
+4. Update current manifests to target this Memorystore (redis) instance.
+
+```sh
+cp ./release/kubernetes-manifests.yaml ./release/updated-manifests.yaml
+REDIS_IP=$(gcloud redis instances describe redis-cart --region=${REGION} --format='get(host)')
+sed -i "s/value: \"redis-cart:6379\"/value: \"${REDIS_IP}\"/g" ./release/updated-manifests.yaml
+```
+
+In addition, in the `./release/updated-manifests.yaml` file you need also to manually remove the `Deployment` and `Service` sections of the `redis-cart` which are not needed anymore.
+
+4. Apply all the updated manifests. 
+
+```sh
+kubectl apply -f ./release/updated-manifests.yaml
+```
+
+5. **Wait for the Pods to be ready.**
+
+```
+kubectl get pods
+```
+
+After a few minutes, you should see:
+
+```
+NAME                                     READY   STATUS    RESTARTS   AGE
+adservice-76bdd69666-ckc5j               1/1     Running   0          2m58s
+cartservice-66d497c6b7-dp5jr             1/1     Running   0          2m59s
+checkoutservice-666c784bd6-4jd22         1/1     Running   0          3m1s
+currencyservice-5d5d496984-4jmd7         1/1     Running   0          2m59s
+emailservice-667457d9d6-75jcq            1/1     Running   0          3m2s
+frontend-6b8d69b9fb-wjqdg                1/1     Running   0          3m1s
+loadgenerator-665b5cd444-gwqdq           1/1     Running   0          3m
+paymentservice-68596d6dd6-bf6bv          1/1     Running   0          3m
+productcatalogservice-557d474574-888kr   1/1     Running   0          3m
+recommendationservice-69c56b74d4-7z8r5   1/1     Running   0          3m1s
+shippingservice-6ccc89f8fd-v686r         1/1     Running   0          2m58s
+```
+
+7. **Access the web frontend in a browser** using the frontend's `EXTERNAL_IP`.
+
+```
+kubectl get service frontend-external | awk '{print $4}'
+```
+
+**Note**- you may see `<pending>` while GCP provisions the load balancer. If this happens, wait a few minutes and re-run the command.
+
+## Resources
+
+- [Connecting to a Redis instance from a Google Kubernetes Engine cluster](https://cloud.google.com/memorystore/docs/redis/connect-redis-instance-gke)