-
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 application mananaged resources fail to delete with finalizer set to resources-finalizer.argocd.argoproj.io #20296
Comments
Can you create a minimal reproduction of the issue? It's difficult to know what went wrong without access to the manifests of the resources managed by the app an to the k8s API for the cluster where they were deployed. |
@crenshaw-dev The issue can be simulated with any resource(Deployment, CM etc). |
Can you post the Application's status field? |
|
I just tried to reproduce this with the guestbook app. I used I'd recommend checking your controller logs. |
@crenshaw-dev The finalizer was added using a Kyverno Policy. |
@sholad can you validate that your kyverno policy only ran during the resource creation. If it runs at every update, whenever argo tries to remove the finalizer because it deletes the resources, kyverno may add it back. |
Checklist:
argocd version
.Describe the bug
I created a kyverno policy to update my argocd application with the finalizer "resources-finalizer.argocd.argoproj.io". The application was created and the finalizer was present in the application's live manifest. However, when I deleted the application, the child resources managed was deleted but the app was stuck in Deletion.
To Reproduce
=====Kyverno policy====
====Application ====
Push the manifests to the gitops repo.
Wait for argocd to create the application and resources.
Comment out or remove the application from the gitops repo. To delete the app.
Expected behavior
Application stuck in Deleting state
Expected the application to be deleted, including the managed resources.
Version
v2.12.4+27d1e64
The text was updated successfully, but these errors were encountered: