Skip to content

Commit

Permalink
Merge pull request #1596 from fluxcd/release-1.36.0
Browse files Browse the repository at this point in the history
Release 1.36.0
  • Loading branch information
stefanprodan authored Feb 7, 2024
2 parents c0a00e6 + cf6e241 commit 3f06a0b
Show file tree
Hide file tree
Showing 11 changed files with 48 additions and 22 deletions.
29 changes: 28 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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)
Expand Down
2 changes: 1 addition & 1 deletion artifacts/flagger/deployment.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions charts/flagger/Chart.yaml
Original file line number Diff line number Diff line change
@@ -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
Expand Down
2 changes: 1 addition & 1 deletion charts/flagger/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@

image:
repository: ghcr.io/fluxcd/flagger
tag: 1.35.0
tag: 1.36.0
pullPolicy: IfNotPresent
pullSecret:

Expand Down
4 changes: 2 additions & 2 deletions charts/loadtester/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
apiVersion: v1
name: loadtester
version: 0.30.0
appVersion: 0.30.0
version: 0.31.0
appVersion: 0.31.0
kubeVersion: ">=1.19.0-0"
engine: gotpl
description: Flagger's load testing services based on rakyll/hey and bojand/ghz that generates traffic during canary analysis when configured as a webhook.
Expand Down
2 changes: 1 addition & 1 deletion charts/loadtester/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ replicaCount: 1

image:
repository: ghcr.io/fluxcd/flagger-loadtester
tag: 0.30.0
tag: 0.31.0
pullPolicy: IfNotPresent
pullSecret:

Expand Down
5 changes: 3 additions & 2 deletions cmd/loadtester/main.go
Original file line number Diff line number Diff line change
Expand Up @@ -22,13 +22,14 @@ import (
"regexp"
"time"

"go.uber.org/zap"

"github.com/fluxcd/flagger/pkg/loadtester"
"github.com/fluxcd/flagger/pkg/logger"
"github.com/fluxcd/flagger/pkg/signals"
"go.uber.org/zap"
)

var VERSION = "0.30.0"
var VERSION = "0.31.0"
var (
logLevel string
port string
Expand Down
16 changes: 7 additions & 9 deletions docs/gitbook/tutorials/istio-progressive-delivery.md
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Expand Down
2 changes: 1 addition & 1 deletion kustomize/base/flagger/kustomization.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -9,4 +9,4 @@ resources:
images:
- name: ghcr.io/fluxcd/flagger
newName: ghcr.io/fluxcd/flagger
newTag: 1.35.0
newTag: 1.36.0
2 changes: 1 addition & 1 deletion kustomize/tester/deployment.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ spec:
spec:
containers:
- name: loadtester
image: ghcr.io/fluxcd/flagger-loadtester:0.30.0
image: ghcr.io/fluxcd/flagger-loadtester:0.31.0
imagePullPolicy: IfNotPresent
ports:
- name: http
Expand Down
2 changes: 1 addition & 1 deletion pkg/version/version.go
Original file line number Diff line number Diff line change
Expand Up @@ -16,5 +16,5 @@ limitations under the License.

package version

var VERSION = "1.35.0"
var VERSION = "1.36.0"
var REVISION = "unknown"

0 comments on commit 3f06a0b

Please sign in to comment.