Move examples to tutorials docs

.gitbook.yaml

@@ -1 +1,12 @@
-root: ./docs/gitbook
+root: ./docs/gitbook
+
+redirects:
+  usage/progressive-delivery: tutorials/istio-progressive-delivery.md
+  usage/ab-testing: tutorials/istio-ab-testing.md
+  usage/blue-green: tutorials/kubernetes-blue-green.md
+  usage/appmesh-progressive-delivery: tutorials/appmesh-progressive-delivery.md
+  usage/linkerd-progressive-delivery: tutorials/linkerd-progressive-delivery.md
+  usage/contour-progressive-delivery: tutorials/contour-progressive-delivery.md
+  usage/gloo-progressive-delivery: tutorials/gloo-progressive-delivery.md
+  usage/nginx-progressive-delivery: tutorials/nginx-progressive-delivery.md
+  usage/crossover-progressive-delivery: tutorials/crossover-progressive-delivery.md

docs/gitbook/SUMMARY.md

@@ -3,6 +3,7 @@
 * [Introduction](README.md)
 * [How it works](how-it-works.md)
 * [FAQ](faq.md)
+* [Development guide](dev-guide.md)
 
 ## Install
 
@@ -13,20 +14,21 @@
 
 ## Usage
 
-* [Istio Canary Deployments](usage/progressive-delivery.md)
-* [Istio A/B Testing](usage/ab-testing.md)
-* [Linkerd Canary Deployments](usage/linkerd-progressive-delivery.md)
-* [App Mesh Canary Deployments](usage/appmesh-progressive-delivery.md)
-* [NGINX Canary Deployments](usage/nginx-progressive-delivery.md)
-* [Gloo Canary Deployments](usage/gloo-progressive-delivery.md)
-* [Contour Canary Deployments](usage/contour-progressive-delivery.md)
-* [Crossover Canary Deployments](usage/crossover-progressive-delivery.md)
-* [Blue/Green Deployments](usage/blue-green.md)
-* [Monitoring](usage/monitoring.md)
+* [Deployment Strategies](usage/deployment-strategies.md)
 * [Alerting](usage/alerting.md)
+* [Monitoring](usage/monitoring.md)
 
 ## Tutorials
 
+* [Istio Canary Deployments](tutorials/istio-progressive-delivery.md)
+* [Istio A/B Testing](tutorials/istio-ab-testing.md)
+* [Linkerd Canary Deployments](tutorials/linkerd-progressive-delivery.md)
+* [App Mesh Canary Deployments](tutorials/appmesh-progressive-delivery.md)
+* [NGINX Canary Deployments](tutorials/nginx-progressive-delivery.md)
+* [Gloo Canary Deployments](tutorials/gloo-progressive-delivery.md)
+* [Contour Canary Deployments](tutorials/contour-progressive-delivery.md)
+* [Blue/Green Deployments](tutorials/kubernetes-blue-green.md)
+* [Crossover Canary Deployments](tutorials/crossover-progressive-delivery.md)
 * [SMI Istio Canary Deployments](tutorials/flagger-smi-istio.md)
 * [Canaries with Helm charts and GitOps](tutorials/canary-helm-gitops.md)
 * [Zero downtime deployments](tutorials/zero-downtime-deployments.md)

docs/gitbook/usage/alerting.md

@@ -53,55 +53,3 @@ Besides Slack, you can use Alertmanager to trigger alerts when a canary deployme
       description: "Workload {{ $labels.name }} namespace {{ $labels.namespace }}"
 ```
 
-### Event Webhook
-
-Flagger can be configured to send event payloads to a specified webhook:
-
-```bash
-helm upgrade -i flagger flagger/flagger \
---set eventWebhook=https://example.com/flagger-canary-event-webhook
-```
-
-The environment variable *EVENT_WEBHOOK_URL* can be used for activating the event-webhook, too.
-This is handy for using a secret to store a sensible value that could contain api keys for example.
-
-When configured, every action that Flagger takes during a canary deployment will be sent as JSON via an HTTP POST
-request. The JSON payload has the following schema:
-
-```json
-{
-  "name": "string (canary name)",
-  "namespace": "string (canary namespace)",
-  "phase": "string (canary phase)",
-  "metadata": {
-    "eventMessage": "string (canary event message)",
-    "eventType": "string (canary event type)",
-    "timestamp": "string (unix timestamp ms)"
-  }
-}
-```
-
-Example:
-
-```json
-{
-  "name": "podinfo",
-  "namespace": "default",
-  "phase": "Progressing",
-  "metadata": {
-    "eventMessage": "New revision detected! Scaling up podinfo.default",
-    "eventType": "Normal",
-    "timestamp": "1578607635167"
-  }
-}
-```
-
-The event webhook can be overwritten at canary level with:
-
-```yaml
-  canaryAnalysis:
-    webhooks:
-      - name: "send to Slack"
-        type: event
-        url: http://event-recevier.notifications/slack
-```

docs/gitbook/usage/monitoring.md

@@ -40,6 +40,59 @@ Scaling down podinfo.test
 Promotion completed! podinfo.test
 ```
 
+### Event Webhook
+
+Flagger can be configured to send event payloads to a specified webhook:
+
+```bash
+helm upgrade -i flagger flagger/flagger \
+--set eventWebhook=https://example.com/flagger-canary-event-webhook
+```
+
+The environment variable *EVENT_WEBHOOK_URL* can be used for activating the event-webhook, too.
+This is handy for using a secret to store a sensible value that could contain api keys for example.
+
+When configured, every action that Flagger takes during a canary deployment will be sent as JSON via an HTTP POST
+request. The JSON payload has the following schema:
+
+```json
+{
+  "name": "string (canary name)",
+  "namespace": "string (canary namespace)",
+  "phase": "string (canary phase)",
+  "metadata": {
+    "eventMessage": "string (canary event message)",
+    "eventType": "string (canary event type)",
+    "timestamp": "string (unix timestamp ms)"
+  }
+}
+```
+
+Example:
+
+```json
+{
+  "name": "podinfo",
+  "namespace": "default",
+  "phase": "Progressing",
+  "metadata": {
+    "eventMessage": "New revision detected! Scaling up podinfo.default",
+    "eventType": "Normal",
+    "timestamp": "1578607635167"
+  }
+}
+```
+
+The event webhook can be overwritten at canary level with:
+
+```yaml
+  canaryAnalysis:
+    webhooks:
+      - name: "send to Slack"
+        type: event
+        url: http://event-recevier.notifications/slack
+```
+
 ### Metrics
 
 Flagger exposes Prometheus metrics that can be used to determine the canary analysis status and