From c264e3b9b19a353f99be9bfbe338dd4c07897e0a Mon Sep 17 00:00:00 2001 From: Mark Shields <4237425+beejiujitsu@users.noreply.github.com> Date: Tue, 9 Jul 2024 13:52:33 -0400 Subject: [PATCH 1/2] docs(install): spelling, grammar Signed-off-by: Mark Shields <4237425+beejiujitsu@users.noreply.github.com> --- mkdocs/docs/experiments/troubleshooting/install.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mkdocs/docs/experiments/troubleshooting/install.md b/mkdocs/docs/experiments/troubleshooting/install.md index 9934a1c751a..fff6b992628 100644 --- a/mkdocs/docs/experiments/troubleshooting/install.md +++ b/mkdocs/docs/experiments/troubleshooting/install.md @@ -29,7 +29,7 @@ If not created, install it from [here](https://github.com/litmuschaos/chaos-oper Under typical operating conditions, the ChaosOperator makes use of finalizers to ensure that the ChaosEngine is deleted only after chaos resources (chaos-runner, experiment pod, any other helper pods) are removed. -When uninstalling Litmus via the operator manifest (which contains the namespace, operator, crd specifictions in a single YAML) +When uninstalling Litmus via the operator manifest, which contains the namespace, operator, crd specifications in a single YAML, without deleting the existing chaosengine resources first, the ChaosOperator deployment may get deleted before the CRD removal is attempted. Since the stale chaosengines have the finalizer present on them, their deletion (triggered by the CRD delete) and by consequence, the deletion of the chaosengine CRD itself is "stuck". From c31031a49be183d1e42c38f7f5bced811323529b Mon Sep 17 00:00:00 2001 From: Mark Shields <4237425+beejiujitsu@users.noreply.github.com> Date: Tue, 9 Jul 2024 13:54:34 -0400 Subject: [PATCH 2/2] Update mkdocs/docs/experiments/troubleshooting/install.md Signed-off-by: Mark Shields <4237425+beejiujitsu@users.noreply.github.com> --- mkdocs/docs/experiments/troubleshooting/install.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mkdocs/docs/experiments/troubleshooting/install.md b/mkdocs/docs/experiments/troubleshooting/install.md index fff6b992628..6db84f73319 100644 --- a/mkdocs/docs/experiments/troubleshooting/install.md +++ b/mkdocs/docs/experiments/troubleshooting/install.md @@ -29,7 +29,7 @@ If not created, install it from [here](https://github.com/litmuschaos/chaos-oper Under typical operating conditions, the ChaosOperator makes use of finalizers to ensure that the ChaosEngine is deleted only after chaos resources (chaos-runner, experiment pod, any other helper pods) are removed. -When uninstalling Litmus via the operator manifest, which contains the namespace, operator, crd specifications in a single YAML, +When uninstalling Litmus via the operator manifest, which contains the namespace, operator, and crd specifications in a single YAML, without deleting the existing chaosengine resources first, the ChaosOperator deployment may get deleted before the CRD removal is attempted. Since the stale chaosengines have the finalizer present on them, their deletion (triggered by the CRD delete) and by consequence, the deletion of the chaosengine CRD itself is "stuck".