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.

Sign up for GitHub

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: Fix User Docs with outdated commands #1787

Merged
merged 2 commits into from
Aug 22, 2024
+2 −2
Merged

docs: Fix User Docs with outdated commands #1787

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
68cbfe1
Fix User Docs with outdated commands
jeremyharisch Aug 21, 2024
356a1a1
Merge branch 'main' into fixDocs
jeremyharisch Aug 21, 2024
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
4 changes: 2 additions & 2 deletions docs/user-tutorials/02-10-manage-module-with-custom-resource-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ By default, the CustomResourcePolicy of the enabled module is `CreateAndDelete`.
For example, to enable the Keda module with the default policy for the `default-kyma` Kyma CR, run:

```bash
kyma alpha add module keda -n kyma-system -k default-kyma
kyma alpha enable module keda -n kyma-system -k default-kyma
```

This will result in the `default-kyma` Kyma CR spec like this:
Expand All @@ -35,7 +35,7 @@ spec:

Lifecycle Manager will create a corresponding Keda CR in your target cluster and propagate all the values from the ModuleTemplate `spec.data.spec` to the `spec.resource` of the related Manifest CR. This way, you can configure and manage your Keda resources using Lifecycle Manager.

To skip this enablement process, you can set the `customResourcePolicy` flag to `Ignore` when you enable the module. This will result in no Keda CR created in your target cluster. It will also prevent Lifecycle Manager from adding any `spec.resource` to the related Manifest CR.
To skip this enablement process, you can set the `--policy` flag to `Ignore` when you enable the module. This will result in no Keda CR created in your target cluster. It will also prevent Lifecycle Manager from adding any `spec.resource` to the related Manifest CR.

> [!WARNING]
> Setting up the flag to `Ignore` also means that Lifecycle Manager does not monitor or manage any Keda CR's readiness status. Therefore, you should exercise caution and discretion when using the `Ignore` policy for your module CR.
Loading