-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
helmCharts does not support 1+ instances of same chart, with different versions #4813
Comments
/triage accepted Kustomize caches the helm chart under a directory that just matches the chart name. It should also be storing the version in the cache directory name so that it can check if the version matches when it is updated, and also support this use case of having different chart versions. |
* Fix using same helm chart with different versions * Fix p.ValuesFile when version is set * Updated: Fix using same helm chart with different versions * Add test for issue #4813 * Use if/else for readability, add version check to absChartHome
Rather unfortunately we had to revert #4999 so I am reopening this. My bad for not catching the regression! |
Hi @natasha41575, do we have any updates on this? |
Details of why we had to revert the change are in #4999 (comment). We need to make sure that we don't modify the directory format of where the chart lives, as it breaks the workflow of users with local charts. If someone wants to pick this up, please take care to look at the previous PR and why we had to revert it. |
* Fix using same helm chart with different versions * Fix p.ValuesFile when version is set * Updated: Fix using same helm chart with different versions * Add test for issue kubernetes-sigs#4813 * Use if/else for readability, add version check to absChartHome
hi @natasha41575, I have just submitted a PR to fix #4999 as well this issue, Could you take a look at it? |
* Fix using same helm chart with different versions * Fix p.ValuesFile when version is set * Updated: Fix using same helm chart with different versions * Add test for issue kubernetes-sigs#4813 * Use if/else for readability, add version check to absChartHome
* Fix using same helm chart with different versions * Fix p.ValuesFile when version is set * Updated: Fix using same helm chart with different versions * Add test for issue kubernetes-sigs#4813 * Use if/else for readability, add version check to absChartHome
* Fix using same helm chart with different versions * Fix p.ValuesFile when version is set * Updated: Fix using same helm chart with different versions * Add test for issue kubernetes-sigs#4813 * Use if/else for readability, add version check to absChartHome
* Fix using same helm chart with different versions * Fix p.ValuesFile when version is set * Updated: Fix using same helm chart with different versions * Add test for issue kubernetes-sigs#4813 * Use if/else for readability, add version check to absChartHome
@natasha41575 , i think we can close this as per #5293 |
* Fix using same helm chart with different versions * Fix p.ValuesFile when version is set * Updated: Fix using same helm chart with different versions * Add test for issue kubernetes-sigs#4813 * Use if/else for readability, add version check to absChartHome
This issue has not been updated in over 1 year, and should be re-triaged. You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
Describe the bug
When I define multiple chart instances in
helmCharts
for same chart but with different versions, the first version defined is pulled and used for all instances.Files that can reproduce the issue
Expected output
For the supplied
kustomization.yaml
we should see two Deployment resources with different images, but we do not.Actual output
For the supplied
kustomization.yaml
we see two Deployment resources with matching images.To verify:
Versions
Kustomize version: 4.5.7
Helm version: 3.9.4
Platform
I don't believe it's relevant, but I am on Mac.
Additional context
Since kustomize has a
--helm-command
I wrote a wrapper to inspect thehelm
executions made by kustomize.Here are the executions:
Observerations:
helm pull
of the 1st version, untarred to unversioned pathhelm template
execs on the unversioned chart locationI conclude this is not a Helm issue, but a Kustomize issue.
Suggested fix: add the version to the chart directory (eg
podinfo-6.2.1
) and use the versioned dir in thehelm template
execs.Regards.
The text was updated successfully, but these errors were encountered: