Add shadow and ab/testing graphs, decrease initial replicas

jevywong · Jan 28, 2018 · 1bf84f9 · 1bf84f9
1 parent 13b7dd3
commit 1bf84f9
Show file tree

Hide file tree

Showing 6 changed files with 13 additions and 1 deletion.
diff --git a/README.md b/README.md
@@ -114,3 +114,11 @@ Blue/Green:
 Canary:
 
 ![Kubernetes deployment canary](canary/grafana-canary.png)
+
+A/B testing:
+
+![kubernetes ab-testing deployment](ab-testing/grafana-ab-testing.png)
+
+Shadow:
+
+![kubernetes shadow deployment](shadow/grafana-shadow.png)
diff --git a/ab-testing/README.md b/ab-testing/README.md
@@ -3,6 +3,8 @@ A/B testing using Istio
 
 > Version B is released to a subset of users under specific condition.
 
+![kubernetes ab-testing deployment](grafana-ab-testing.png)
+
 A/B testing deployments consists of routing a subset of users to a new
 functionality under specific conditions. It is usually a technique for making
 business decisions based on statistics, rather than a deployment strategy.

diff --git a/ab-testing/grafana-ab-testing.png b/ab-testing/grafana-ab-testing.png
diff --git a/canary/app-v2.yaml b/canary/app-v2.yaml
@@ -5,7 +5,7 @@ metadata:
   labels:
     app: my-app
 spec:
-  replicas: 3
+  replicas: 1
   template:
     metadata:
       labels:

diff --git a/shadow/README.md b/shadow/README.md
@@ -4,6 +4,8 @@ Shadow deployment
 > Version B receives real-world traffic alongside version A and doesn’t impact
 the response.
 
+![kubernetes shadow deployment](grafana-shadow.png)
+
 A shadow deployment consists of releasing version B alongside version A, fork
 version A’s incoming requests and send them to version B as well without
 impacting production traffic. This is particularly useful to test production

diff --git a/shadow/grafana-shadow.png b/shadow/grafana-shadow.png