This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/incubator-kie-kogito-docs.git
The following commit(s) were added to refs/heads/gh-pages by this push:
new 52bb88261 deploy: 84940cb4d418f7037c05faeb0941fc9efa55d209
52bb88261 is described below
commit 52bb882616e3b6f84b5ffcf49a9343035fcc964d
Author: ricardozanini <[email protected]>
AuthorDate: Mon Mar 11 14:18:15 2024 +0000
deploy: 84940cb4d418f7037c05faeb0941fc9efa55d209
---
.../main/cloud/operator/supporting-services.html | 43 +++++++++++++++++++++-
1 file changed, 42 insertions(+), 1 deletion(-)
diff --git a/serverlessworkflow/main/cloud/operator/supporting-services.html
b/serverlessworkflow/main/cloud/operator/supporting-services.html
index ce44804c9..a7ab594a2 100644
--- a/serverlessworkflow/main/cloud/operator/supporting-services.html
+++ b/serverlessworkflow/main/cloud/operator/supporting-services.html
@@ -5,7 +5,7 @@
<meta name="viewport" content="width=device-width,initial-scale=1">
<title>Supporting Services :: SonataFlow Guides</title>
<meta name="description" content="Deploy Supporting Services with
SonataFlow Operator">
- <meta name="keywords" content="kogito, sonataflow, workflow, serverless,
operator, kubernetes, openshift, containers, data, index, job, service">
+ <meta name="keywords" content="kogito, sonataflow, workflow, serverless,
operator, kubernetes, openshift, containers, data, index, job, service,
cluster, wide, scoped, cluster-wide, cluster-scoped">
<meta name="generator" content="Antora 3.1.4">
<link rel="stylesheet" href="../../../../_/css/site.css">
<link rel="icon" href="../../../../_/img/favicon.ico" type="image/x-icon">
@@ -798,6 +798,44 @@ spec:
</div>
</div>
<div class="sect1">
+<h2 id="cluster-wide-services"><a class="anchor"
href="#cluster-wide-services"></a>Cluster-Wide Supporting Services</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The <code>SonataFlowClusterPlatform</code> CR is optionally used to specify
a cluster-wide set of supporting services for workflow consumption. This is
done by referencing an existing, namespaced <code>SonataFlowPlatform</code>
resource.</p>
+</div>
+<div class="paragraph">
+<p>Following is a basic configuration. It will allow workflows cluster-wide to
leverage whatever supporting services are configured in the chosen "central"
namespace.</p>
+</div>
+<div class="listingblock">
+<div class="title">Example of a basic SonataFlowClusterPlatform CR</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs"
data-lang="yaml">apiVersion: sonataflow.org/v1alpha08
+kind: SonataFlowClusterPlatform
+metadata:
+ name: cluster-platform
+spec:
+ platformRef:
+ name: sonataflow-platform
+ namespace: <central namespace></code></pre>
+</div>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+<div class="paragraph">
+<p>These cluster-wide services can be overridden in any namespace, by
configuring that namespace’s
<code>SonataFlowPlatform.spec.services</code>.</p>
+</div>
+</td>
+</tr>
+</table>
+</div>
+</div>
+</div>
+<div class="sect1">
<h2 id="_additional_resources"><a class="anchor"
href="#_additional_resources"></a>Additional resources</h2>
<div class="sectionbody">
<div class="ulist">
@@ -806,6 +844,9 @@ spec:
<p><a href="../../data-index/data-index-service.html" class="xref page">Data
Index standalone service</a></p>
</li>
<li>
+<p><a href="enabling-jobs-service.html" class="xref page">Managing Jobs
Service with the Operator</a></p>
+</li>
+<li>
<p><a href="known-issues.html" class="xref page">SonataFlow Operator Known
Issues, Limitations and Roadmap</a></p>
</li>
</ul>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
