Skip to content

Commit d587f9d

Browse files
jmagakGitHub Actions
andauthored
Apply peer suggestions (#1379)
Co-authored-by: GitHub Actions <[email protected]>
1 parent 6e0009a commit d587f9d

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
@@ -24,7 +24,7 @@ helm install `<release_name>` openshift-helm-charts/redhat-developer-hub-orchest
2424
+
2525
[IMPORTANT]
2626
====
27-
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.
27+
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.
2828
====
2929

3030
. 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
@@ -7,7 +7,7 @@ Use manual installation when you want full control of the setup process and comp
77

88
.Procedure
99

10-
. 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.
10+
. Install the OpenShift Serverless components manually by following the instructions in the {rhoserverless-link}[{rhoserverless-brand-name}] documentation.
1111

1212
. 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].
1313

0 commit comments

Comments
 (0)