-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
argocd cannot resolve kustomize manifest. #3814
Comments
Hello @jetersen , I think this is due to this bug in Kustomize 3.5.5: kubernetes-sigs/kustomize#2538 . Try changing git URL as following: Thanks, |
See argoproj/argo-cd#3814 Kustomize issue: kubernetes-sigs/kustomize#2538 go-getter issue: hashicorp/go-getter#257
See argoproj/argo-cd#3814 Kustomize issue: kubernetes-sigs/kustomize#2538 go-getter issue: hashicorp/go-getter#257
Yes it fixes it @alexmt though as I understand it would break again once go-getter fixes the issue which is not ideal 😭 |
This works around the issue discussed in argoproj/argo-cd#3814 due to changes in kustomize and go-getting. Essentially, with the "//" technique of downloading a single directory, other directories outside that tree could be resolved.
This works around the issue discussed in argoproj/argo-cd#3814 due to changes in kustomize and go-getter. Essentially, with the `//` technique of downloading a single directory, other directories outside that tree couldn't be resolved.
@jetersen actually, Kustomize follows a similar pattern to go-getter but does not use go-getter itself (this confused me as well, as a small optimization in Kustomize's version lead to me having issues not reproducible with go-getter). |
the new suggested format of url should reported in the documentation: https://argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup/#manage-argo-cd-using-argo-cd |
This for me was an issue with the command Manually switching the paths to forward slashes fixed the issue for me. |
What's the reason behind the docs not reporting the new url? Nobody opening a PR or is there a special reason why it has to stay double slashed and without https? |
@SnoozeFreddo The standard kustomize URL format for remote directories contains both https and double slashes:
The legacy URL format does not:
The ArgoCD docs example is missing the
|
anyone else running into a variant of this when you refer the |
Describe the bug
We use argo-cd to deploy argo-cd using kustomize, though since v1.5.6 we are seeing the error below. So downgraded to v1.5.5 where it works.
Tried to upgrade to v1.5.7 was working fine for a day or so but than the argo-cd application hit the error again.
To Reproduce
Setup a argo-cd application using kustomize
Expected behavior
Kustomize should be able to resolve the manifest.
Screenshots
Version
Logs
Repo server log:
Application controller log:
The text was updated successfully, but these errors were encountered: