From 7776d658205c8ff3e87795684e64e5eceffbcb73 Mon Sep 17 00:00:00 2001 From: Jordi Gil Date: Wed, 6 Mar 2024 15:21:10 -0500 Subject: [PATCH] Fix adoc errors Signed-off-by: Jordi Gil --- .../ROOT/pages/cloud/operator/enabling-jobs-service.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/serverlessworkflow/modules/ROOT/pages/cloud/operator/enabling-jobs-service.adoc b/serverlessworkflow/modules/ROOT/pages/cloud/operator/enabling-jobs-service.adoc index 1b8dafdcd..bb8da60f3 100644 --- a/serverlessworkflow/modules/ROOT/pages/cloud/operator/enabling-jobs-service.adoc +++ b/serverlessworkflow/modules/ROOT/pages/cloud/operator/enabling-jobs-service.adoc @@ -18,7 +18,7 @@ This integration eliminates the need for including these properties within the S To enable the deployment of a Jobs Service instance, the `SonataFlowPlatform` CRD exposes a set of fields that allow the user to configure the running instance. -==== Ephemeral persistence +=== Ephemeral persistence The basic runtime is to deploy the Jobs Service with an ephemeral backend running in the same container as the Jobs Service runtime. @@ -44,7 +44,7 @@ sonataflow-platform-jobs-service-cdf85d969-sbwkj 1/1 Running 0 Keep in mind that this setup is not recommended for production environments, especially because the data does not persist when the pod restarts. -==== Using an existing PostgreSQL service +=== Using an existing PostgreSQL service For robust environments it is recommened to use an dedicated database service and configure Jobs Service to make use of it. Currently, the Jobs Service only supports PostgreSQL database. @@ -54,7 +54,7 @@ deployed in the same namespace. By default, the persistence specification defined in the `SonataFlow` workflow's CR takes priority over the one in the `SonataFlowPlatform` persistence specification. -===== Using the persistence field defined in the `SonataFlowPlatform` CR +==== Using the persistence field defined in the `SonataFlowPlatform` CR Using the persistence configuration in the `SonataFlowPlatform` CR located in the same namespace requires to have the `SonataFlow` CR persistence field configured to have an empty `{}` value, signaling the Operator to derive the persistence from the active `SonataFlowPlatform`, when available. If no persistence is defined the operator will fallback to the ephemeral persistence previously described. @@ -139,7 +139,7 @@ Annotations: Type: Opaque Data -==== +\\\\==== PGDATA: 28 bytes POSTGRES_DATABASE: 10 bytes POSTGRES_PASSWORD: 10 bytes