-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent .Capabilities.APIVersions between helm install and argocd's helm template #6351
Comments
Hello, I had similar issue today and what I did to fix it was:
If it doesn't help, then it's not the same issue (but symtoms identical). |
Not following @Lirt - how does invalidating the cache result on the apiserver bundled with argo returning a newer version? |
Hmm I think my scenario was different, I apologise. In my case I installed |
got it - and agreed, seems those versions are coming from the different chart versions, and thus your suggestion for refreshing the dep cache makes sense. This issue however is related to the apiserver and the versions available there vs what argo's bundling and checking the |
Same problem here with GitLab helm chart version 5.2.1. https://gitlab.com/gitlab-org/charts/gitlab/-/blob/master/templates/_helpers.tpl#L518 |
edit: It did not help - issue's still present. |
I am still seeing this issue in the following combination:
There is no avail with:
|
I tried to add a feature to solve this kind of problem : helm/helm#10108. Yet it seems like it is not the good way around. Have you got another idea ? 🍵 🦖 |
We need some ArgoCD devs input here. @alexmt, sorry to disturb you, but could you please take a look at helm/helm#10108 (comment)? Is the proposed path acceptable from the ArgoCD perspective? |
Same issue with the following combination with the Keycloak Chart: {
"Version": "v2.1.2+7af9dfb",
"BuildDate": "2021-09-02T18:05:23Z",
"GitCommit": "7af9dfb3524c13e941ab604e36e49a617fe47d2e",
"GitTreeState": "clean",
"GoVersion": "go1.16.5",
"Compiler": "gc",
"Platform": "linux/amd64",
"KsonnetVersion": "v0.13.1",
"KustomizeVersion": "v4.2.0 2021-06-30T22:49:26Z",
"HelmVersion": "v3.6.0+g7f2df64",
"KubectlVersion": "v0.21.0",
"JsonnetVersion": "v0.17.0"
} Rendering templates locally using |
I've filled a new bug, with a summary of problems about APIVersions (and a new one). See #7291. |
If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.
Checklist:
argocd version
.Describe the bug
We're attempting to write template conditionals around resource upgrades, at the resource specific level - for example:
However, these conditionals always resolve false, because the .Capabilities.APIVersions that is exposed when ArgoCD runs helm template only includes the API-level versions, and not the Resource-level versions.
Earlier github issues, and our own testing, has shown that conditionals against API-level checks work, so the following snippet is OK (for now):
However, this isn't going to be OK forever, due to scenarios such as this one: https://gitea.com/gitea/helm-chart/issues/77
The inconsistency isn't great, but the specific problem of switching for resource API versions with fine-grained detail is really more important.
To Reproduce
Make a chart with a single small template:
Add to your ArgoCD by whatever method of your choosing, and also
helm install -n testing apiversiontest-fromhelm ./apiversiontest/
Note that the one created from plain ol' helm is much larger and contains entries for each individual resource.
Expected behavior
They don't need to be in the same order, but it would be cool to roughly the same values.
Screenshots
If applicable, add screenshots to help explain your problem.
Version
Don't have the CLI installed, but from the web UI:
v2.0.0+f5119c0
Paste the output from `argocd version` here.
Logs
The text was updated successfully, but these errors were encountered: