ArgoCD Application creation fails when referenced repository/path does not exists #209
Labels
bug
Something isn't working
Comments
|
Last 100 log lines from the argocd provider to show the hammering w/o back-off or re-queing |
|
I confirmed that the API can disable the validation of cluster/repo. The API can be told to not validate the repo/cluster as shown below. CLI parameter: Checking the provider for equivalent option: argocd app create test-argocd-cli --insecure=true --validate=true --repo https://xxxxxx/v3-configuration-dev/isv-configuration/nk-bedc-dev/nk-bedc-dev.git --project nk-bedc-us-east-1-argocd-prj-dev --path bad-path --dest-namespace test --dest-server https://kubernetes.default.svc
FATA[0004] rpc error: code = InvalidArgument desc = application spec for test-argocd-cli is invalid: InvalidSpecError: Unable to generate manifests in bad-path: rpc error: code = Unknown desc = bad-path: app path does not exist
argocd app create test-argocd-cli --insecure=true --validate=false --repo https://xxxxxx/v3-configuration-dev/isv-configuration/nk-bedc-dev/nk-bedc-dev.git --project nk-bedc-us-east-1-argocd-prj-dev --path bad-path --dest-namespace test --dest-server https://kubernetes.default.svc
application 'test-argocd-cli' createdI am pretty sure the is different than |
|
From the API spec: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
When creating an ArgoCD app from the command like (kubectl apply) with a repository with a folder that does not exist yet, the application will be accepted and then go in
Unknownstatus. But it is accepted.When trying to create the same application from Crossplane, the Application is never accepted by the ArgoCD instance and the managed resource returns this error:
Also, the
argocd-servershows that the API is being called repeatedly by crossplane w/o back-off. This could lead to overwhelming theargocd-serverHow can we reproduce it?
Managed Resource in Crossplane:
YAML applied using kubectl apply
Proof that kubectl apply accepts the application
What environment did it happen in?
Crossplane version: 1.16
Crossplane Provider argocd version: v0.9.0
kubectl version) 1.29Cross-posted against ArgoCD argoproj/argo-cd#20580
The text was updated successfully, but these errors were encountered: