Merge pull request #57 from stefanprodan/release-0.6.0

Release v0.6.0

CHANGELOG.md

@@ -2,6 +2,25 @@
 
 All notable changes to this project are documented in this file.
 
+## 0.6.0 (2019-02-25)
+
+Allows for [HTTPMatchRequests](https://istio.io/docs/reference/config/istio.networking.v1alpha3/#HTTPMatchRequest) 
+and [HTTPRewrite](https://istio.io/docs/reference/config/istio.networking.v1alpha3/#HTTPRewrite) 
+to be customized in the service spec of the canary custom resource.
+
+#### Features
+
+- Add HTTP match conditions and URI rewrite to the canary service spec [#55](https://github.com/stefanprodan/flagger/pull/55)
+- Update virtual service when the canary service spec changes 
+    [#54](https://github.com/stefanprodan/flagger/pull/54)
+    [#51](https://github.com/stefanprodan/flagger/pull/51)
+
+#### Improvements 
+
+- Run e2e testing on [Kubernetes Kind](https://github.com/kubernetes-sigs/kind) for canary promotion 
+    [#53](https://github.com/stefanprodan/flagger/pull/53)
+
+
 ## 0.5.1 (2019-02-14)
 
 Allows skipping the analysis phase to ship changes directly to production

README.md

@@ -26,6 +26,7 @@ Flagger documentation can be found at [docs.flagger.app](https://docs.flagger.ap
     * [Flagger install on GKE](https://docs.flagger.app/install/flagger-install-on-google-cloud)
 * How it works
     * [Canary custom resource](https://docs.flagger.app/how-it-works#canary-custom-resource)
+    * [Virtual Service](https://docs.flagger.app/how-it-works#virtual-service)
     * [Canary deployment stages](https://docs.flagger.app/how-it-works#canary-deployment)
     * [Canary analysis](https://docs.flagger.app/how-it-works#canary-analysis)
     * [HTTP metrics](https://docs.flagger.app/how-it-works#http-metrics)
@@ -105,7 +106,7 @@ spec:
     rewrite:
       uri: /
   # for emergency cases when you want to ship changes
-  # in production without analysing the canary
+  # in production without analysing the canary (default false)
   skipAnalysis: false
   canaryAnalysis:
     # schedule interval (default 60s)
@@ -144,8 +145,8 @@ For more details on how the canary analysis and promotion works please [read the
 ### Roadmap
 
 * Extend the validation mechanism to support other metrics than HTTP success rate and latency
+* Add A/B testing capabilities using fixed routing based on HTTP headers and cookies match conditions
 * Add support for comparing the canary metrics to the primary ones and do the validation based on the derivation between the two
-* Extend the canary analysis and promotion to other types than Kubernetes deployments such as Flux Helm releases or OpenFaaS functions
 
 ### Contributing
 

artifacts/flagger/deployment.yaml

@@ -22,7 +22,7 @@ spec:
       serviceAccountName: flagger
       containers:
       - name: flagger
-        image: quay.io/stefanprodan/flagger:0.5.1
+        image: quay.io/stefanprodan/flagger:0.6.0
         imagePullPolicy: IfNotPresent
         ports:
         - name: http

charts/flagger/Chart.yaml

@@ -1,7 +1,7 @@
 apiVersion: v1
 name: flagger
-version: 0.5.1
-appVersion: 0.5.1
+version: 0.6.0
+appVersion: 0.6.0
 kubeVersion: ">=1.11.0-0"
 engine: gotpl
 description: Flagger is a Kubernetes operator that automates the promotion of canary deployments using Istio routing for traffic shifting and Prometheus metrics for canary analysis.

charts/flagger/values.yaml

@@ -2,7 +2,7 @@
 
 image:
   repository: quay.io/stefanprodan/flagger
-  tag: 0.5.1
+  tag: 0.6.0
   pullPolicy: IfNotPresent
 
 metricsServer: "http://prometheus.istio-system.svc.cluster.local:9090"

pkg/version/version.go

@@ -1,4 +1,4 @@
 package version
 
-var VERSION = "0.5.1"
+var VERSION = "0.6.0"
 var REVISION = "unknown"