You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've recently upgraded Flux from v0.35.0 to v0.41.2 and now observe that when a HelmRelease fails to reconcile due to timed out waiting for the condition we no longer see the log actions which indicate which wait action has timed out.
Last Helm logs:
creating 4 resource(s)
beginning wait for 4 resources with timeout of 5m0s
Deployment is not ready: thanos/thanos. 0 out of 1 expected pods are ready
However, the same Last Helm logs event in v0.41.2 now looks like this:
Last Helm logs:
resetting values to the chart's original version
performing update for thanos
creating upgraded release for thanos
waiting for release thanos resources (created: 0 updated: 23 deleted: 5)
warning: Upgrade "thanos" failed: timed out waiting for the condition
From a cursory review of the recent helm-controller and helm changes, I can't see anything that should have this impact, but something has changed it seems.
The previous output was extremely helpful and made troubleshooting a breeze, with the new output especially on the more complex releases, it is quite a pain to figure out what exactly has failed.
The text was updated successfully, but these errors were encountered:
Hey folks 👋🏼
We've recently upgraded Flux from v0.35.0 to v0.41.2 and now observe that when a HelmRelease fails to reconcile due to
timed out waiting for the condition
we no longer see the log actions which indicate which wait action has timed out.Component versions:
The
Last Helm logs
event we see in v0.35.0:which is also consistent with thetroubleshooting docs.
However, the same
Last Helm logs
event in v0.41.2 now looks like this:From a cursory review of the recent
helm-controller
andhelm
changes, I can't see anything that should have this impact, but something has changed it seems.The previous output was extremely helpful and made troubleshooting a breeze, with the new output especially on the more complex releases, it is quite a pain to figure out what exactly has failed.
The text was updated successfully, but these errors were encountered: