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
When using ArgoCD v2.13+ with kustomize v5.3.0 or below, configured through Custom kustomize versions, an error occurs during synchronization when the --enable-helm option is used.
Problem Details
This error occurs because the specified version of kustomize in the repository is v5.2.1-helm, which does not implement the --helm-kube-version flag. This is confirmed by the help output of kustomize_5_2_1.
Root Cause Analysis
The root cause of the problem was analyzed as follows:
The parseKustomizeBuildOptions function checks build options.(source)
A specific condition is true when buildOpts is not empty, the kustomize version is v5.3.0 or above, and --enable-helm is set.(source)
There is an issue with the version obtained through the getSemverSafe -> getSemver -> Version functions.*(source)
The desired binary version is /usr/local/bin/kustomize_5_2_1, but the binary is fixed as kustomize, leading to inconsistency.(source)
To Reproduce
Steps to reproduce the issue:
1.Configure ArgoCD with kustomize v5.2.1-helm.
Attempt to sync a project using the --enable-helm option.
Observe the error message.
Expected behavior
Synchronization should proceed without errors, and the --helm-kube-version flag should be handled correctly.
Note that the condition is inverted so it should effectively be a >= 5.3.0. IMO what the OP said in his RCA seems to be what's happening.
If that's truly the bug (which is likely IMO) it means that all the kustomize version comparison in this file doesn't work when installing a custom kustomize version, although the most probable one would be this one as the other version checks seems to be >= 3.8.5 and >= 3,7,0 which are quite old.
Note that the condition is inverted so it should effectively be a >= 5.3.0. IMO what the OP said in his RCA seems to be what's happening.
If that's truly the bug (which is likely IMO) it means that all the kustomize version comparison in this file doesn't work when installing a custom kustomize version, although the most probable one would be this one as the other version checks seems to be >= 3.8.5 and >= 3,7,0 which are quite old.
Ah yes you're right. Missed the inverted condition!
Checklist:
argocd version
.Describe the bug
When using ArgoCD v2.13+ with kustomize v5.3.0 or below, configured through Custom kustomize versions, an error occurs during synchronization when the --enable-helm option is used.
Problem Details
This error occurs because the specified version of kustomize in the repository is v5.2.1-helm, which does not implement the --helm-kube-version flag. This is confirmed by the help output of kustomize_5_2_1.
Root Cause Analysis
The root cause of the problem was analyzed as follows:
The parseKustomizeBuildOptions function checks build options.(source)
A specific condition is true when buildOpts is not empty, the kustomize version is v5.3.0 or above, and --enable-helm is set.(source)
There is an issue with the version obtained through the getSemverSafe -> getSemver -> Version functions.*(source)
The desired binary version is /usr/local/bin/kustomize_5_2_1, but the binary is fixed as kustomize, leading to inconsistency.(source)
To Reproduce
Steps to reproduce the issue:
1.Configure ArgoCD with kustomize v5.2.1-helm.
Expected behavior
Synchronization should proceed without errors, and the --helm-kube-version flag should be handled correctly.
Screenshots
Version
Logs
The text was updated successfully, but these errors were encountered: