Release v1.36.0

Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>

CHANGELOG.md

@@ -2,6 +2,33 @@
 
 All notable changes to this project are documented in this file.
 
+## 1.36.0
+
+**Release date:** 2024-02-07
+
+This release comes with support for canary releases with traffic shifting using
+Istio TCP routing. For more information on how to enable TCP routing please
+see the [Istio tutorial](hhttps://docs.flagger.app//tutorials/istio-progressive-delivery#canary-deployments-for-tcp-services).
+
+Both Flagger and the load tester Go dependencies have been updated to fix various CVEs.
+Flagger is now built with Go 1.21 and the container base image has been updated to Alpine 3.19.
+
+#### Improvements
+- Istio Canary TCP service support
+  [#1564](https://github.com/fluxcd/flagger/pull/1564)
+- Update Go dependencies
+  [#1595](https://github.com/fluxcd/flagger/pull/1595)
+- Build with Go 1.21 and Alpine 3.19
+  [#1594](https://github.com/fluxcd/flagger/pull/1594)
+
+#### Fixes
+- return an error for missing metric templates
+  [#1582](https://github.com/fluxcd/flagger/pull/1582)
+- istio: make retry attempts a mandatory field
+  [#1571](https://github.com/fluxcd/flagger/pull/1571)
+- fix(pdb): use the full capabilities comparison for PDBs
+  [#1511](https://github.com/fluxcd/flagger/pull/1511)
+
 ## 1.35.0
 
 **Release date:** 2023-11-30
@@ -18,7 +45,7 @@ Lastly, two bugs related to deleting a Canary object with
 `.spec.revertOnDeletion: true` have been fixed.
 
 #### Improvements
-- Support istio Destination Dule WarmupDurationSecs
+- Support Istio DestinationRule WarmupDurationSecs
   [#1540](https://github.com/fluxcd/flagger/pull/1540)
 - feat: Webhook retries
   [#1541](https://github.com/fluxcd/flagger/pull/1541)

artifacts/flagger/deployment.yaml

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

charts/flagger/Chart.yaml

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

charts/flagger/values.yaml

@@ -5,7 +5,7 @@
 
 image:
   repository: ghcr.io/fluxcd/flagger
-  tag: 1.35.0
+  tag: 1.36.0
   pullPolicy: IfNotPresent
   pullSecret:
 

docs/gitbook/tutorials/istio-progressive-delivery.md

@@ -508,15 +508,13 @@ spec:
 ```yaml
 apiVersion: flagger.app/v1beta1
 kind: Canary
-...
-...
-service:
-  port: 7070
-  appProtocol: TCP # <== set the appProtocol here
-  targetPort: 7070
-  portName: "tcp-service-port"
-...
-...
+# omitted for brevity
+spec:
+  service:
+    port: 7070
+    appProtocol: TCP # <== set the appProtocol here
+    targetPort: 7070
+    portName: "tcp-service-port"
 ```
 
 If the `appProtocol` equals `TCP` then Flagger will treat this as a Canary deployment for a `TCP` service. When it creates the `VirtualService` document it will add a `TCP` section to route requests between the `primary` and `canary` services. See Istio documentation for more information on this [spec](https://istio.io/latest/docs/reference/config/networking/virtual-service/#TCPRoute).

kustomize/base/flagger/kustomization.yaml

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

pkg/version/version.go

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