From 804843bfbe9e33e34d20b8fd4535417869cd5d56 Mon Sep 17 00:00:00 2001 From: Roy Golan Date: Tue, 20 Aug 2024 20:46:49 +0300 Subject: [PATCH] Update serverlessworkflow/modules/ROOT/pages/cloud/operator/add-custom-ca-to-a-workflow-pod.adoc Co-authored-by: Ricardo Zanini <1538000+ricardozanini@users.noreply.github.com> --- .../pages/cloud/operator/add-custom-ca-to-a-workflow-pod.adoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/serverlessworkflow/modules/ROOT/pages/cloud/operator/add-custom-ca-to-a-workflow-pod.adoc b/serverlessworkflow/modules/ROOT/pages/cloud/operator/add-custom-ca-to-a-workflow-pod.adoc index f7fc08561..d94303106 100644 --- a/serverlessworkflow/modules/ROOT/pages/cloud/operator/add-custom-ca-to-a-workflow-pod.adoc +++ b/serverlessworkflow/modules/ROOT/pages/cloud/operator/add-custom-ca-to-a-workflow-pod.adoc @@ -137,8 +137,7 @@ spec: Similar to a deployment spec, a serverless workflow has a spec.podTemplate, with minor differences, but the change is almost identical. In this case, we are mounting some ingress ca-bundle because we want our workflow to reach the `.apps.my-cluster-name.my-cluster-domain` SSL endpoint. -In this example we pull the ingress CA of OpenShift's ingress deployment because this -is the CA that is used to sign certificates for routes. It can be any CA that is signing the target service certificate. +In this example, we pull the ingress CA of OpenShift's ingress deployment because this is the CA that signs the target routes' certificates. It can be any CA that is signing the target service certificate. Here's how to copy the ingress ca cert to the desired namespace: [source,shell]