Merge pull request #1172 from fluxcd/release-1.20.0

Release v1.20.0
This commit is contained in:
Stefan Prodan
2022-04-15 13:24:01 +03:00
committed by GitHub
13 changed files with 51 additions and 22 deletions
+28
View File
@@ -2,6 +2,34 @@
All notable changes to this project are documented in this file.
## 1.20.0
**Release date:** 2022-04-15
This release comes with improvements to the AppMesh, Contour and Istio integrations.
#### Improvements
- AppMesh: Add annotation to enable Envoy access logs
[#1156](https://github.com/fluxcd/flagger/pull/1156)
- Contour: Update the httproxy API and enable RetryOn
[#1164](https://github.com/fluxcd/flagger/pull/1164)
- Istio: Add destination port when port discovery and delegation are true
[#1145](https://github.com/fluxcd/flagger/pull/1145)
- Metrics: Add canary analysis result as Prometheus metrics
[#1148](https://github.com/fluxcd/flagger/pull/1148)
#### Fixes
- Fix canary rollback behaviour
[#1171](https://github.com/fluxcd/flagger/pull/1171)
- Shorten the metric analysis cycle after confirm promotion gate is open
[#1139](https://github.com/fluxcd/flagger/pull/1139)
- Fix unit of time in the Istio Grafana dashboard
[#1162](https://github.com/fluxcd/flagger/pull/1162)
- Fix the service toggle condition in the podinfo helm chart
[#1146](https://github.com/fluxcd/flagger/pull/1146)
## 1.19.0
**Release date:** 2022-03-14
-1
View File
@@ -237,7 +237,6 @@ For all [Gateway API](https://gateway-api.sigs.k8s.io/) implementations like [Co
#### Integrations
* Add support for ingress controllers like HAProxy and ALB
* Add support for metrics providers like InfluxDB, Stackdriver, SignalFX
### Contributing
+1 -1
View File
@@ -22,7 +22,7 @@ spec:
serviceAccountName: flagger
containers:
- name: flagger
image: ghcr.io/fluxcd/flagger:1.19.0
image: ghcr.io/fluxcd/flagger:1.20.0
imagePullPolicy: IfNotPresent
ports:
- name: http
+2 -2
View File
@@ -1,7 +1,7 @@
apiVersion: v1
name: flagger
version: 1.19.0
appVersion: 1.19.0
version: 1.20.0
appVersion: 1.20.0
kubeVersion: ">=1.16.0-0"
engine: gotpl
description: Flagger is a progressive delivery operator for Kubernetes
+2 -2
View File
@@ -2,7 +2,7 @@
image:
repository: ghcr.io/fluxcd/flagger
tag: 1.19.0
tag: 1.20.0
pullPolicy: IfNotPresent
pullSecret:
@@ -138,7 +138,7 @@ tolerations: []
prometheus:
# to be used with ingress controllers
install: false
image: docker.io/prom/prometheus:v2.33.5
image: docker.io/prom/prometheus:v2.34.0
pullSecret:
retention: 2h
# when enabled, it will add a security context for the prometheus pod
+1 -1
View File
@@ -1,6 +1,6 @@
apiVersion: v1
name: grafana
version: 1.6.0
version: 1.7.0
appVersion: 7.2.0
description: Grafana dashboards for monitoring Flagger canary deployments
icon: https://raw.githubusercontent.com/fluxcd/flagger/main/docs/logo/flagger-icon.png
+2 -2
View File
@@ -1,6 +1,6 @@
apiVersion: v1
version: 6.0.1
appVersion: 6.0.0
version: 6.1.3
appVersion: 6.1.3
name: podinfo
engine: gotpl
description: Flagger canary deployment demo application
+1 -1
View File
@@ -1,7 +1,7 @@
# Default values for podinfo.
image:
repository: ghcr.io/stefanprodan/podinfo
tag: 6.0.0
tag: 6.1.3
pullPolicy: IfNotPresent
podAnnotations: {}
+3 -3
View File
@@ -10,10 +10,10 @@ version in production by gradually shifting traffic to the new version while mea
and running conformance tests.
Flagger implements several deployment strategies (Canary releases, A/B testing, Blue/Green mirroring)
using a service mesh (App Mesh, Istio, Linkerd, Open Service Mesh)
using a service mesh (App Mesh, Istio, Linkerd, Kuma, Open Service Mesh)
or an ingress controller (Contour, Gloo, NGINX, Skipper, Traefik) for traffic routing.
For release analysis, Flagger can query Prometheus, Datadog, New Relic, CloudWatch or Graphite
and for alerting it uses Slack, MS Teams, Discord and Rocket.
For release analysis, Flagger can query Prometheus, InfluxDB, Datadog, New Relic, CloudWatch, Stackdriver
or Graphite and for alerting it uses Slack, MS Teams, Discord and Rocket.
![Flagger overview diagram](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-overview.png)
+8 -6
View File
@@ -478,7 +478,7 @@ spec:
name: graphite-basic-auth
```
## Google CLoud Monitoring (Stackdriver)
## Google Cloud Monitoring (Stackdriver)
Enable Workload Identity on your cluster, create a service account key that has read access to the
Cloud Monitoring API and then create an IAM policy binding between the GCP service account and the Flagger
@@ -528,18 +528,20 @@ spec:
The reference for the query language can be found [here](https://cloud.google.com/monitoring/mql/reference)
## Influxdb
## InfluxDB
The influxdb provider uses the [flux](https://docs.influxdata.com/influxdb/v2.0/query-data/get-started/) scripting language.
The InfluxDB provider uses the [flux](https://docs.influxdata.com/influxdb/v2.0/query-data/get-started/) query language.
Create a secret that contains your authentication token that can be gotthen from the InfluxDB UI.
Create a secret that contains your authentication token that can be found in the InfluxDB UI.
```
kubectl create secret generic gcloud-sa --from-literal=token=<token>
kubectl create secret generic influx-token --from-literal=token=<token>
```
Then reference the secret in the metric template.qq
Then reference the secret in the metric template.
Note: The particular MQL query used here works if [Istio is installed on GKE](https://cloud.google.com/istio/docs/istio-on-gke/installing).
```yaml
apiVersion: flagger.app/v1beta1
kind: MetricTemplate
+1 -1
View File
@@ -9,4 +9,4 @@ resources:
images:
- name: ghcr.io/fluxcd/flagger
newName: ghcr.io/fluxcd/flagger
newTag: 1.19.0
newTag: 1.20.0
+1 -1
View File
@@ -19,7 +19,7 @@ spec:
serviceAccountName: flagger-prometheus
containers:
- name: prometheus
image: prom/prometheus:v2.33.5
image: prom/prometheus:v2.34.0
imagePullPolicy: IfNotPresent
args:
- '--storage.tsdb.retention=2h'
+1 -1
View File
@@ -16,5 +16,5 @@ limitations under the License.
package version
var VERSION = "1.19.0"
var VERSION = "1.20.0"
var REVISION = "unknown"