This repository has been archived by the owner on Jul 15, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 279
Workaround Argo CD cluster deletion reconciliation bug #170
Comments
This was referenced Mar 25, 2021
This was referenced Mar 29, 2021
jgwest
added a commit
to jgwest/applicationset
that referenced
this issue
Jul 2, 2021
…ame for destination
jgwest
added a commit
to jgwest/applicationset
that referenced
this issue
Jul 2, 2021
…ame for destination
jgwest
added a commit
to jgwest/applicationset
that referenced
this issue
Jul 2, 2021
…ame for destination
jgwest
added a commit
to jgwest/applicationset
that referenced
this issue
Jul 2, 2021
…ame for destination
jgwest
added a commit
to jgwest/applicationset
that referenced
this issue
Jul 9, 2021
…ame for destination
jgwest
added a commit
to jgwest/applicationset
that referenced
this issue
Jul 9, 2021
…ame for destination
jgwest
added a commit
to jgwest/applicationset
that referenced
this issue
Jul 9, 2021
…ame for destination
jgwest
added a commit
to jgwest/applicationset
that referenced
this issue
Jul 9, 2021
…ame for destination
jgwest
added a commit
that referenced
this issue
Jul 13, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Argo CD bug argoproj/argo-cd#5817 causes significant issues for the Cluster generator of the ApplicationSet controller: when a cluster is deleted from Argo CD, and that cluster had Applications associated with it, Argo CD is unable to delete the Application and the application controller enters a reconciliation loop.
This is primarily an Argo CD bug, but is easily reproducible with the ApplicationSet controller (due to us supporting automated deletion of Applications on cluster deletion), hence the need to workaround it until it is fixed in v1.8 and v2.x Argo CD versions.
The text was updated successfully, but these errors were encountered: