helm-controller/internal
Aurel Canciu 7c75fc4d3d
Fix HelmRelease reconciliation loop
Likely after the upgrade to controller-runtime v0.15.0 a regression
surfaced for long-running reconciliations of HelmRelease resources (e.g.
for charts having pre-upgrade hooks taking a few minutes to complete).
This regression would cause the controller to immediately re-run the
upgrade after a successful upgrade, thus entering an almost-endless
loop.

Apparently, the only fix to this issue is to ensure
`.Status.LastReleaseRevision` is updated as soon as possible in the
reconiliation cycle rather than wait for the update at the end of the
cycle.

Signed-off-by: Aurel Canciu <aurelcanciu@gmail.com>
2023-06-20 14:52:50 +03:00
..
cmp diff: prettify premature diff log 2023-03-01 10:27:46 +01:00
controller Fix HelmRelease reconciliation loop 2023-06-20 14:52:50 +03:00
diff Change to `helm.toolkit.fluxcd.io/driftDetection` 2023-03-01 13:04:13 +01:00
features Allow opt-out of drift correction 2023-03-20 13:07:08 +01:00
kube kube: make persistent client opt-in configuration 2023-03-30 16:14:15 +02:00
oomwatch oomwatch: auto detect well known cgroup paths 2023-03-10 15:08:17 +01:00
runner Update Kubernetes, controller-runtime and Helm 2023-05-24 10:39:51 +02:00
util Stable sort release values by key 2023-05-11 10:17:52 +02:00