|
2 | 2 |
|
3 | 3 | All notable changes to this project are documented in this file.
|
4 | 4 |
|
| 5 | +## 1.31.0 |
| 6 | + |
| 7 | +**Release date:** 2023-05-10 |
| 8 | + |
| 9 | +⚠️ __Breaking Changes__ |
| 10 | + |
| 11 | +This release adds support for Linkerd 2.12 and later. Due to changes in Linkerd |
| 12 | +the default namespace for Flagger's installation had to be changed from |
| 13 | +`linkerd` to `flagger-system` and the `flagger` Deployment is now injected with |
| 14 | +the Linkerd proxy. Furthermore, installing Flagger for Linkerd will result in |
| 15 | +the creation of an `AuthorizationPolicy` that allows access to the Prometheus |
| 16 | +instance in the `linkerd-viz` namespace. To upgrade your Flagger installation, |
| 17 | +please see the below migration guide. |
| 18 | + |
| 19 | +If you use Kustomize, then follow these steps: |
| 20 | +* `kubectl delete -n linkerd deploy/flagger` |
| 21 | +* `kubectl delete -n linkerd serviceaccount flagger` |
| 22 | +* If you're on Linkerd >= 2.12, you'll need to install the SMI extension to enable |
| 23 | + support for `TrafficSplit`s: |
| 24 | + ```bash |
| 25 | + curl -sL https://linkerd.github.io/linkerd-smi/install | sh |
| 26 | + linkerd smi install | kubectl apply -f - |
| 27 | + ``` |
| 28 | +* `kubectl apply -k github.com/fluxcd/flagger//kustomize/linkerd` |
| 29 | + |
| 30 | + Note: If you're on Linkerd < 2.12, this will report an error about missing CRDs. |
| 31 | + It is safe to ignore this error. |
| 32 | + |
| 33 | +If you use Helm and are on Linkerd < 2.12, then you can use `helm upgrade` to do |
| 34 | +a regular upgrade. |
| 35 | + |
| 36 | +If you use Helm and are on Linkerd >= 2.12, then follow these steps: |
| 37 | +* `helm uninstall flagger -n linkerd` |
| 38 | +* Install the Linkerd SMI extension: |
| 39 | + ```bash |
| 40 | + helm repo add l5d-smi https://linkerd.github.io/linkerd-smi |
| 41 | + helm install linkerd-smi l5d-smi/linkerd-smi -n linkerd-smi --create-namespace |
| 42 | + ``` |
| 43 | +* Install Flagger in the `flagger-system` namespace |
| 44 | + and create an `AuthorizationPolicy`: |
| 45 | + ```bash |
| 46 | + helm repo update flagger |
| 47 | + helm install flagger flagger/flagger \ |
| 48 | + --namespace flagger-system \ |
| 49 | + --set meshProvider=linkerd \ |
| 50 | + --set metricsServer=http://prometheus.linkerd-viz:9090 \ |
| 51 | + --set linkerdAuthPolicy.create=true |
| 52 | + ``` |
| 53 | + |
| 54 | +Furthermore, a bug which led the `confirm-rollout` webhook to be executed at |
| 55 | +every step of the Canary instead of only being executed before the canary |
| 56 | +Deployment is scaled up, has been fixed. |
| 57 | + |
| 58 | +#### Improvements |
| 59 | + |
| 60 | +- Add support for Linkerd 2.13 |
| 61 | + [#1417](https://github.com/fluxcd/flagger/pull/1417) |
| 62 | + |
| 63 | +#### Fixes |
| 64 | + |
| 65 | +- Fix the loadtester install with flux documentation |
| 66 | + [#1384](https://github.com/fluxcd/flagger/pull/1384) |
| 67 | +- Run `confirm-rollout` checks only before scaling up deployment |
| 68 | + [#1414](https://github.com/fluxcd/flagger/pull/1414) |
| 69 | +- e2e: Remove OSM tests |
| 70 | + [#1423](https://github.com/fluxcd/flagger/pull/1423) |
| 71 | + |
5 | 72 | ## 1.30.0
|
6 | 73 |
|
7 | 74 | **Release date:** 2023-04-12
|
|
0 commit comments