Bump CRD version to v1alpha3

- new field canaryAnalysis.interval

docs/gitbook/how-it-works.md

@@ -9,7 +9,7 @@
 For a deployment named _podinfo_, a canary promotion can be defined using Flagger's custom resource:
 
 ```yaml
-apiVersion: flagger.app/v1alpha2
+apiVersion: flagger.app/v1alpha3
 kind: Canary
 metadata:
   name: podinfo
@@ -38,6 +38,8 @@ spec:
     hosts:
     - podinfo.example.com
   canaryAnalysis:
+    # schedule interval (default 60s)
+    interval: 1m
     # max number of failed metric checks before rollback
     threshold: 10
     # max traffic percentage routed to canary
@@ -128,12 +130,13 @@ You can change the canary analysis _max weight_ and the _step weight_ percentage
 ### Canary Analysis
 
 The canary analysis runs periodically until it reaches the maximum traffic weight or the failed checks threshold. 
-By default the analysis interval is set to one minute and can be configured with the `controlLoopInterval` command flag.
 
 Spec:
 
 ```yaml
   canaryAnalysis:
+    # schedule interval (default 60s)
+    interval: 1m
     # max number of failed metric checks before rollback
     threshold: 10
     # max traffic percentage routed to canary
@@ -148,13 +151,13 @@ The above analysis, if it succeeds, will run for 25 minutes while validating the
 You can determine the minimum time that it takes to validate and promote a canary deployment using this formula:
 
 ```
-controlLoopInterval * (maxWeight / stepWeight)
+interval * (maxWeight / stepWeight)
 ```
 
 And the time it takes for a canary to be rollback:
 
 ```
-controlLoopInterval * threshold 
+interval * threshold 
 ```
 
 ### HTTP Metrics

docs/gitbook/install/install-flagger.md

@@ -23,8 +23,7 @@ Deploy Flagger in the _**istio-system**_ namespace:
 ```bash
 helm upgrade -i flagger flagger/flagger \
 --namespace=istio-system \
---set metricsServer=http://prometheus.istio-system:9090 \
---set controlLoopInterval=1m
+--set metricsServer=http://prometheus.istio-system:9090
 ```
 
 Enable **Slack** notifications:

docs/gitbook/usage/progressive-delivery.md

@@ -20,7 +20,7 @@ kubectl apply -f ${REPO}/artifacts/canaries/hpa.yaml
 Create a canary custom resource \(replace example.com with your own domain\):
 
 ```yaml
-apiVersion: v1alpha2
+apiVersion: flagger.app/v1alpha3
 kind: Canary
 metadata:
   name: podinfo
@@ -49,6 +49,8 @@ spec:
     hosts:
     - app.example.com
   canaryAnalysis:
+    # schedule interval (default 60s)
+    interval: 1m
     # max number of failed metric checks before rollback
     threshold: 5
     # max traffic percentage routed to canary