-
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
ArgoCD v2.3.0 - ARGOCD_GIT_ASKPASS_NONCE is not set #8716
Comments
I confirmed that rolling back to 2.2.6 fixes the issue. If I then try to apply the new manifests, it breaks again. Nothing else changing between the two other than the newer manifests. This is using a Gitlab deploy token for authentication. Not sure if that affects it or not. |
Further investigations, if I apply the older version of ApplicationSet CRDs overtop of the newer ones deployed by Argo-cd things also work again. So it seems to have something to do with the newer CRD manifests at https://raw.githubusercontent.com/argoproj/applicationset/v0.4.0/manifests/install.yaml |
I can confirm your investigation is right. |
Just an update, they are trying to address the issue with a 0.4.1 release of the applicationset CRDs with this merge argoproj/applicationset#535. I assume once we apply that it should resolve the issue. Not sure if this will require an update to ArgoCD 2.3.0 though |
To my understanding starting from ArgoCD 2.3.0 applicationset controller is bundled in the installation manifests, so I would expect to have a new ArgoCD release for this fix. |
@sharon-hunters does 2.3.1 fix this? |
@tooptoop4 yep |
v2.3.1 release with fixed application set version has been published. |
Please update the documentation accordingly to reflect the fix. The command should be |
Describe the bug
I get the following error in my
ApplicationSet
even though I can confirm that the repo settings showconnectionstatus
as successful.This is in a Kubernetes EKS cluster in AWS.
Expected behavior
it should load the repository and create the applications
Screenshots
Version
ApplicationSet Output
The text was updated successfully, but these errors were encountered: