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
{{ message }}
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
We were changing the URL of the git repository of a HelmRelease.
Unfortunately, the Helm Operator didn't pick that up and didn't trigger a sync.
Deleting the pod of helm-operator, thus restarting it, helped. We would expect that it automatically picks up the new url without a restart.
We also tried deleting the HelmRelease resource. Flux was re-creating the HelmRelease resource but still the old repository URL was used by helm-operator. Is this a known issue?
The text was updated successfully, but these errors were encountered:
The problem is that chart clones being stored against the releaseName. In case a previous chart clone is found the operator will never look at the git source in the HelmRelease again as it already has a clone for the said release name.
We were changing the URL of the git repository of a
HelmRelease
.Unfortunately, the Helm Operator didn't pick that up and didn't trigger a sync.
Deleting the pod of
helm-operator
, thus restarting it, helped. We would expect that it automatically picks up the new url without a restart.We also tried deleting the
HelmRelease
resource. Flux was re-creating theHelmRelease
resource but still the old repository URL was used byhelm-operator
. Is this a known issue?The text was updated successfully, but these errors were encountered: