Merge pull request #813 from fluxcd/release-1.6.3

Release v1.6.3

CHANGELOG.md

@@ -2,6 +2,27 @@
 
 All notable changes to this project are documented in this file.
 
+## 1.6.3
+
+**Release date:** 2021-02-15
+
+This release comes with support for Kubernetes pod topology spread constraints.
+
+Flagger has a new [logo](https://github.com/fluxcd/flagger/pull/812),
+many thanks to [Bianca](https://github.com/bia) for designed it.
+
+#### Improvements
+
+- Rewrite the primary Pod Topology Spread Constraints based on label selector
+  [#806](https://github.com/fluxcd/flagger/pull/806)
+
+#### Fixes
+
+- Suffix only the podAntiAffinity values that match the deployment name
+  [#805](https://github.com/fluxcd/flagger/pull/805)
+- Check if mandatory secrets/configmaps exist
+  [#799](https://github.com/fluxcd/flagger/pull/799)
+
 ## 1.6.2
 
 **Release date:** 2021-01-28

artifacts/flagger/deployment.yaml

@@ -22,7 +22,7 @@ spec:
       serviceAccountName: flagger
       containers:
       - name: flagger
-        image: ghcr.io/fluxcd/flagger:1.6.2
+        image: ghcr.io/fluxcd/flagger:1.6.3
         imagePullPolicy: IfNotPresent
         ports:
         - name: http

charts/flagger/Chart.yaml

@@ -1,7 +1,7 @@
 apiVersion: v1
 name: flagger
-version: 1.6.2
-appVersion: 1.6.2
+version: 1.6.3
+appVersion: 1.6.3
 kubeVersion: ">=1.16.0-0"
 engine: gotpl
 description: Flagger is a progressive delivery operator for Kubernetes

charts/flagger/values.yaml

@@ -2,7 +2,7 @@
 
 image:
   repository: ghcr.io/fluxcd/flagger
-  tag: 1.6.2
+  tag: 1.6.3
   pullPolicy: IfNotPresent
   pullSecret:
 

docs/gitbook/SUMMARY.md

@@ -8,6 +8,7 @@
 * [Flagger Install on Kubernetes](install/flagger-install-on-kubernetes.md)
 * [Flagger Install on GKE Istio](install/flagger-install-on-google-cloud.md)
 * [Flagger Install on EKS App Mesh](install/flagger-install-on-eks-appmesh.md)
+* [Flagger Install on Alibaba ServiceMesh](install/flagger-install-on-alibaba-servicemesh.md)
 
 ## Usage
 
@@ -32,7 +33,6 @@
 * [Blue/Green Deployments](tutorials/kubernetes-blue-green.md)
 * [Canary analysis with Prometheus Operator](tutorials/prometheus-operator.md)
 * [Zero downtime deployments](tutorials/zero-downtime-deployments.md)
-* [Rollout Weights](tutorials/rollout-weights.md)
 
 ## Dev
 

docs/gitbook/faq.md

@@ -224,14 +224,20 @@ If you use a different convention you can specify your label with the `-selector
 
 #### Is pod affinity and anti affinity supported?
 
-Flagger will rewrite the first value in each match expression, defined in the target deployment's pod anti-affinity and topology spread constraints, satisfying the following two requirements when creating, or updating, the primary deployment:
+Flagger will rewrite the first value in each match expression,
+defined in the target deployment's pod anti-affinity and topology spread constraints,
+satisfying the following two requirements when creating, or updating, the primary deployment:
 
-* The key in the match expression must be one of the labels specified by the parameter selector-labels. The default labels are `app`,`name`,`app.kubernetes.io/name`.
+* The key in the match expression must be one of the labels specified by the parameter selector-labels.
+  The default labels are `app`,`name`,`app.kubernetes.io/name`.
 * The value must match the name of the target deployment.
 
-The rewrite done by Flagger in these cases is to suffix the value with "-primary". This rewrite can be used to spread the pods created by the canary and primary deployments across different availability zones.
+The rewrite done by Flagger in these cases is to suffix the value with `-primary`.
+This rewrite can be used to spread the pods created by the canary
+and primary deployments across different availability zones.
 
 Example target deployment:
+
 ```yaml
 apiVersion: apps/v1
 kind: Deployment
@@ -261,6 +267,7 @@ spec:
 ```
 
 Example of generated primary deployment:
+
 ```yaml
 apiVersion: apps/v1
 kind: Deployment
@@ -292,6 +299,7 @@ spec:
 It is also possible to use a different label than the `app`, `name` or `app.kubernetes.io/name`.
 
 Anti affinity example(using a different label):
+
 ```yaml
 apiVersion: apps/v1
 kind: Deployment

kustomize/base/flagger/kustomization.yaml

@@ -9,4 +9,4 @@ resources:
 images:
   - name: ghcr.io/fluxcd/flagger
     newName: ghcr.io/fluxcd/flagger
-    newTag: 1.6.2
+    newTag: 1.6.3

pkg/version/version.go

@@ -16,5 +16,5 @@ limitations under the License.
 
 package version
 
-var VERSION = "1.6.2"
+var VERSION = "1.6.3"
 var REVISION = "unknown"