Release v1.7.0

Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
This commit is contained in:
Stefan Prodan 2021-03-23 11:00:35 +02:00
parent ffef8ba4d9
commit 775dc91ede
No known key found for this signature in database
GPG Key ID: 3299AEB0E4085BAF
8 changed files with 46 additions and 12 deletions

View File

@ -2,6 +2,33 @@
All notable changes to this project are documented in this file.
## 1.7.0
**Release date:** 2021-03-23
This release comes with support for manually approving
the traffic weight increase.
#### Features
- Add webhook for manually approving traffic weight increase
[#849](https://github.com/fluxcd/flagger/pull/849)
- Add WaitingPromotion phase to canary status
[#859](https://github.com/fluxcd/flagger/pull/859)
#### Improvements
- linkerd: update prometheus URL based on the latest 2.10 changes
[#845](https://github.com/fluxcd/flagger/pull/845)
- docs: update resources to disable mTLS in Istio
[#843](https://github.com/fluxcd/flagger/pull/843)
- docs: updating slack alerting docs to point to legacy slack webhooks
[#833](https://github.com/fluxcd/flagger/pull/833)
- chart: Add pull secret for Prometheus deployment
[#842](https://github.com/fluxcd/flagger/pull/842)
- Update Kubernetes packages to v1.20.4
[#857](https://github.com/fluxcd/flagger/pull/857)
## 1.6.4
**Release date:** 2021-02-26

View File

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

View File

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

View File

@ -41,13 +41,13 @@ $ helm upgrade -i flagger flagger/flagger \
--set metricsServer=http://prometheus:9090
```
To install Flagger for **Linkerd**:
To install Flagger for **Linkerd** (requires Linkerd Viz extension):
```console
$ helm upgrade -i flagger flagger/flagger \
--namespace=linkerd \
--set meshProvider=linkerd \
--set metricsServer=http://linkerd-prometheus:9090
--set metricsServer=http://prometheus.linkerd-viz:9090
```
To install Flagger for **AWS App Mesh**:

View File

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

View File

@ -6,7 +6,14 @@ This guide shows you how to use Linkerd and Flagger to automate canary deploymen
## Prerequisites
Flagger requires a Kubernetes cluster **v1.16** or newer and Linkerd **2.4** or newer.
Flagger requires a Kubernetes cluster **v1.16** or newer and Linkerd **2.10** or newer.
Install Linkerd the Promethues (part of Linkerd Viz):
```bash
linkerd install | kubectl apply -f -
linkerd viz install | kubectl apply -f -
```
Install Flagger in the linkerd namespace:
@ -14,11 +21,11 @@ Install Flagger in the linkerd namespace:
kubectl apply -k github.com/fluxcd/flagger//kustomize/linkerd
```
Note that you'll need kubectl 1.14 or newer to run the above command.
## Bootstrap
Flagger takes a Kubernetes deployment and optionally a horizontal pod autoscaler \(HPA\), then creates a series of objects \(Kubernetes deployments, ClusterIP services and SMI traffic split\). These objects expose the application inside the mesh and drive the canary analysis and promotion.
Flagger takes a Kubernetes deployment and optionally a horizontal pod autoscaler (HPA),
then creates a series of objects (Kubernetes deployments, ClusterIP services and SMI traffic split).
These objects expose the application inside the mesh and drive the canary analysis and promotion.
Create a test namespace and enable Linkerd proxy injection:

View File

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

View File

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