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
The history page doesn't show the correct values for params (such as image.tag) after sync using the same Helm Chart version from a helm repo. All entries in the page display the same chart params. Consequently, the rollback function doesn't seems to work. I don't know if it has a relation to #2848.
As I could understand, Argo doesn't keep the 'n' different versions of the same Chart, right? Only if I update the Chart version number... Is it possible to have multiples charts cached for the same application under the same Chart Version?
A list of the steps required to reproduce the issue. Best of all, give us the URL to a repository that exhibits this issue.
Update a parameter in values.yaml in a Helm Chart (image.tag, i.e.) without updating the Chart Version.
Package and Push the Helm Chart to a Chart Repo (Harbor, in my case), overwriting the existing one with the same version (0.1.0, i.e.)
Select an app which is pointing to that Helm Chart repo and "hard refresh" so Argo downloads the new chart (.tgz).
Manually sync the app (the diff shows that there is a new image.tag)
Verify that all the entries in history page display the same old version of the chart. (All history params is updated to the last version of the applied chart after the cache expires)
6 (optional). If I decide to rollback to any version, it applies the same chart that is already deployed (and ignore the values shown on history).
A clear and concise description of what you expected to happen.
That the history page shows all changes and that Argo could keep track of Charts changes, even with the same Chart version.
If applicable, add screenshots to help explain your problem.
Based on https://argoproj.github.io/argo-cd/user-guide/parameters/ if I override image tag helm parameter only and raising chart version is an overkill, how do I go about rollbacking? I think this is a valid use case for those who do not want to go fully GitOps and pollute commit history with version bumps.
Checklist:
argocd version
.The history page doesn't show the correct values for params (such as image.tag) after sync using the same Helm Chart version from a helm repo. All entries in the page display the same chart params. Consequently, the rollback function doesn't seems to work. I don't know if it has a relation to #2848.
As I could understand, Argo doesn't keep the 'n' different versions of the same Chart, right? Only if I update the Chart version number... Is it possible to have multiples charts cached for the same application under the same Chart Version?
A list of the steps required to reproduce the issue. Best of all, give us the URL to a repository that exhibits this issue.
6 (optional). If I decide to rollback to any version, it applies the same chart that is already deployed (and ignore the values shown on history).
A clear and concise description of what you expected to happen.
That the history page shows all changes and that Argo could keep track of Charts changes, even with the same Chart version.
If applicable, add screenshots to help explain your problem.
Paste the output from
argocd version
here.argocd: v1.4.2+48cced9
BuildDate: 2020-01-24T01:04:04Z
GitCommit: 48cced9
GitTreeState: clean
GoVersion: go1.12.6
Compiler: gc
Platform: linux/amd64
argocd-server: v1.4.2+48cced9
BuildDate: 2020-01-24T01:07:03Z
GitCommit: 48cced9
GitTreeState: clean
GoVersion: go1.12.6
Compiler: gc
Platform: linux/amd64
Ksonnet Version: v0.13.1
Kustomize Version: Version: {Version:kustomize/v3.2.1 GitCommit:d89b448c745937f0cf1936162f26a5aac688f840 BuildDate:2019-09-27T00:10:52Z GoOs:linux GoArch:amd64}
Helm Version: v2.15.2
Kubectl Version: v1.14.0
Logs
The text was updated successfully, but these errors were encountered: