syncPolicy.DisableHelmChartCache=true

[lknite]

Summary

It is common in development environments and with bleeding edge releases, for a helm chart to be updated quickly without changing the version number. Although philosophically it may be that this scenario should never occur, and folks need to use pipelines and version numbers every time, regardless ... it happens.

If you are lucky enough to pull a helm chart which was quickly updated in this way, via arogocd you may be out of luck until they release a new helm chart... possibly several days later with issues in the meantime, as argocd will not recognize a new helm chart without a new release version.

Motivation

Running into this today again, this time it was a bitnami helm chart which I submitted a pull request for, I pulled the helm chart and my fix was missing. After some communication the helm chart was updated (with the same version number) and it worked, till I redeployed. Afterwards there is a caching issue. Click 'hard refresh' hasn't helped.

Running into this issue also in my development environment where hard refresh works but afterwards when something restarts its trying to load a different version than the latest and greatest (which it should because I'm using 0.0.x), maybe its cause I'm using an oci helm chart store? Regardless, wish I could just clear out the helm chart cache somehow.

Proposal

      syncPolicy:
        syncOptions:
        - DisableHelmChartCache=true

Requirements

• Support OCI based helm chart stores 'helm show chart ...' in addition to the more established index-based style

Additional

Alternatively, a webhook enhancement which could respond to helm chart updates could also work around this issue in many situations, but that seems like a whole different discussion, so I posted it in the discussion section: #18001