You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a FAQ entry about foreground cascading deletion (#1770)
Issue #, if available:
#1759
Description of changes:
Title says it.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Copy file name to clipboardExpand all lines: docs/content/docs/community/faq.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,6 +65,16 @@ cdk8s can create the Kubernetes resources and ACK uses those resources to create
65
65
66
66
## Troubleshooting
67
67
68
+
{{% hint type="success" title="Question" %}}
69
+
Why are my AWS resources sometimes not being fully deleted when trying to delete via `kubectl delete ... --cascade=foreground ...` (or via ArgoCD uninstalling my Helm chart)?
70
+
{{% /hint %}}
71
+
72
+
{{% hint type="answer" title="Answer" %}}
73
+
There is a [known issue with foreground cascading deletion](https://github.com/aws-controllers-k8s/community/issues/1759) in the ACK runtime that potentially impacts all controllers.
74
+
75
+
Until the above issue is resolved, you should use [background cascading deletion](https://kubernetes.io/docs/tasks/administer-cluster/use-cascading-deletion/#use-background-cascading-deletion) (the default behavior of `kubectl`) to delete resources.
76
+
{{% /hint %}}
77
+
68
78
{{% hint type="success" title="Question" %}}
69
79
Why am I seeing `Error: manifest does not contain minimum number of descriptors (2), descriptors found: 1` when trying to install the Helm chart?
0 commit comments