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
Each flux -n NAMESPACE reconcile helmrelease APP_NAME generates a helm install that increases helm REVISION (it also triggers hooks, of course).
No changes are being made between reconciles neither to the chart or the values.
I am passing the values in the HelmRelease through the values: with no reference to ConfigMaps or Secrets. Just plain text values.
The chart source is an internal ChartMuseum repository.
Also I have compared helm upgrade --install ... outputs and it doesn't have any random generated field or anything and there are no differences between outputs when the same values are provided.
✘ mihai@devBox helm -n ns-core-2 ls --filter ms-tap
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
ms-tap ns-core-2 16 2021-07-09 09:00:36.324702754 +0000 UTC deployed laravel-0.5.6
mihai@devBox flux -n ns-core-2 reconcile helmrelease ms-tap
► annotating HelmRelease ms-tap in ns-core-2 namespace
✔ HelmRelease annotated
◎ waiting for HelmRelease reconciliation
✔ HelmRelease reconciliation completed
✔ applied revision 0.5.6
mihai@devBox helm -n ns-core-2 ls --filter ms-tap
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
ms-tap ns-core-2 18 2021-07-09 09:02:54.144744795 +0000 UTC deployed laravel-0.5.6
As you can see after the reconcile the revision is bumped by 2, from 16 to 18 (not always by 2... possibly it synced with the interval reconcile loop) and hooks were triggered.
Please let me know if I'm missing something, and what data do you need from me (if any).
Disclaimer: I will be on vacation for the next 2 weeks so I'll probably be slow to respond, sorry.
Thanks and congrats for the great tools you're building!
The text was updated successfully, but these errors were encountered:
Thanks for submitting the issue and providing some more details to Stefan.
Based on additional information I have gathered from/with Stefan, it seems that the generation of the HelmRelease for some reason is bumped every time, which makes the controller assume a short route to upgrade because there is an assumption this should only happen for spec changes.
After we discovered this, we had a couple of options left, but were able to trace it down to your internal usage of flux reconcile which due to making use of Update instead of Patch to change the annotation values, seems to accidentally bump the generation.
We will be working on a patch for fluxcd/flux2 to solve this there.
Describe the bug
Each
flux -n NAMESPACE reconcile helmrelease APP_NAME
generates a helm install that increases helm REVISION (it also triggers hooks, of course).No changes are being made between reconciles neither to the chart or the values.
I am passing the values in the
HelmRelease
through thevalues:
with no reference to ConfigMaps or Secrets. Just plain text values.The chart source is an internal ChartMuseum repository.
Also I have compared
helm upgrade --install ...
outputs and it doesn't have any random generated field or anything and there are no differences between outputs when the same values are provided.I am running on versions:
How I reproduce
As you can see after the reconcile the revision is bumped by 2, from 16 to 18 (not always by 2... possibly it synced with the interval reconcile loop) and hooks were triggered.
Please let me know if I'm missing something, and what data do you need from me (if any).
Disclaimer: I will be on vacation for the next 2 weeks so I'll probably be slow to respond, sorry.
Thanks and congrats for the great tools you're building!
The text was updated successfully, but these errors were encountered: