Skip to content

Commit 98e2bca

Browse files
openshift-cherrypick-robotGitHub Actions
andauthored
Apply peer suggestions (#1380)
Co-authored-by: GitHub Actions <[email protected]>
1 parent d9cdd91 commit 98e2bca

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

modules/orchestrator/proc-install-rhdh-with-orchestrator-helm-cli.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ helm install `<release_name>` openshift-helm-charts/redhat-developer-hub-orchest
2323
+
2424
[IMPORTANT]
2525
====
26-
You must be an administrator to install the `redhat-developer-hub-orchestrator-infra` Helm chart because it deploys additional cluster-scoped OpenShift Serverless and OpenShift Serverless Logic Operators. As an administrator, you need to manually approve the install plans for OpenShift Serverless and Serverless Logic Operators.
26+
You must be an administrator to install the `redhat-developer-hub-orchestrator-infra` Helm chart because it deploys additional cluster-scoped OpenShift Serverless and OpenShift Serverless Logic Operators. As an administrator, you must manually approve the install plans for OpenShift Serverless and Serverless Logic Operators.
2727
====
2828

2929
. Install the Backstage chart with the orchestrator enabled as shown in the following example:

modules/orchestrator/proc-manual-install-components-orchestrator-plugin.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Use manual installation when you want full control of the setup process and comp
66

77
.Procedure
88

9-
. Install the OpenShift Serverless components. If you wish to manually install the OpenShift Serverless components, follow the instructions in the {rhoserverless-link}[{rhoserverless-brand-name}] documentation.
9+
. Install the OpenShift Serverless components manually by following the instructions in the {rhoserverless-link}[{rhoserverless-brand-name}] documentation.
1010

1111
. You must also configure workflow persistence to prevent workflow context from being lost when the Pod restarts. You can do this configuration at the namespace level using the `SonataFlowPlatform` or `SonataFlow` custom resources (CR). For detailed instructions on configuring persistence using the `SonataFlowPlatform` or `SonataFlow` custom resources, see {rhoserverless-link}/html-single/serverless_logic/index#serverless-logic-managing-persistence[Managing workflow persistence].
1212

0 commit comments

Comments
 (0)