|
2 | 2 |
|
3 | 3 | All notable changes to this project are documented in this file. |
4 | 4 |
|
| 5 | +## 0.0.9 (2020-09-22) |
| 6 | + |
| 7 | +This prerelease adds support for `DependsOn` references to other namespaces |
| 8 | +than the `HelmRelease` resource resides in, container images for ARMv7 and |
| 9 | +ARMv8 published to `ghcr.io/fluxcd/helm-controller-arm64`, a Helm upgrade |
| 10 | +from `3.3.1` to `3.3.3`, and a refactor of the `Status` object. |
| 11 | + |
| 12 | +The latter introduces the following breaking changes to the `Status` object: |
| 13 | + |
| 14 | +* The `Installed`, `Upgraded`, `RolledBack`, and `Uninstalled` conditions |
| 15 | + have been removed, since they did not represent current state, but rather |
| 16 | + actions taken, which are already recorded by events. |
| 17 | +* The `ObservedStateReconciled` field has been removed, since it solved the |
| 18 | + problem of remembering past release successes, but not past release |
| 19 | + failures, after other subsequent failures such as dependency failures, |
| 20 | + Kubernetes API failures, etc. |
| 21 | +* The `Tested` condition has been renamed to `TestSuccess`, for forward |
| 22 | + compatibility with interval based Helm tests. |
| 23 | + |
| 24 | +While introducing the following new `Status` conditions: |
| 25 | + |
| 26 | +* `Remediated` which records whether the release is currently in a |
| 27 | + remediated state. It is used to prevent release retries after remediation |
| 28 | + failures. We were previously not doing this for rollback failures. |
| 29 | +* `Released` which records whether the current state has been successfully |
| 30 | + released. This is used to remember the last release attempt status, |
| 31 | + regardless of any subsequent other failures such as dependency failures, |
| 32 | + Kubernetes API failures, etc. |
| 33 | + |
5 | 34 | ## 0.0.8 (2020-09-11) |
6 | 35 |
|
7 | 36 | This prerelease adds support for defining a `ValuesFile` in the |
|
0 commit comments