Skip to content
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

docs(install): spelling, grammar #4755

Merged
merged 2 commits into from
Jul 16, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
docs(install): spelling, grammar
Signed-off-by: Mark Shields <4237425+beejiujitsu@users.noreply.github.com>
  • Loading branch information
beejiujitsu authored Jul 9, 2024
commit c264e3b9b19a353f99be9bfbe338dd4c07897e0a
2 changes: 1 addition & 1 deletion mkdocs/docs/experiments/troubleshooting/install.md
Original file line number Diff line number Diff line change
Expand Up @@ -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,
beejiujitsu marked this conversation as resolved.
Show resolved Hide resolved
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".
Expand Down