From cdfb2b05bc89f21151064b5f074389120a276dbd Mon Sep 17 00:00:00 2001 From: Dominik Hanak Date: Wed, 22 May 2024 10:21:05 +0200 Subject: [PATCH] 596 - Review configure-knative-eventing-resources --- .../configuring-knative-eventing-resources.adoc | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-knative-eventing-resources.adoc b/serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-knative-eventing-resources.adoc index 8a9f362c9..8ce4fa6bd 100644 --- a/serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-knative-eventing-resources.adoc +++ b/serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-knative-eventing-resources.adoc @@ -6,11 +6,17 @@ This document describes how you can configure the workflows to let operator create the Knative eventing resources on Kubernetes. -{operator_name} can analyze the event definitions from the `spec.flow` and create `SinkBinding`/`Trigger` based on the type of the event. Then the workflow service can utilize them for event communications. The same purpose of this feature in quarkus extension can be found xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc#ref-example-sw-event-definition-knative[here]. +{operator_name} can analyze the event definitions from the `spec.flow` and create `SinkBinding`/`Trigger` based on the type of the event. Then the workflow service can utilize them for event communications. + +[NOTE] +==== + Alternativelly, you can follow our xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc#ref-example-sw-event-definition-knative[advanced guide] that uses Java and Quarkus to introduce this feature. +==== == Prerequisite -1. Knative is installed on the cluster and Knative Eventing is initiated with a `KnativeEventing` CR. -2. A broker named `default` is created. Currently, all Triggers created by the {operator_name} will read events from `default` +1. The {operator_name} installed. See xref:cloud/operator/install-serverless-operator.adoc[] guide. +2. Knative is installed on the cluster and Knative Eventing is initiated with a `KnativeEventing` CR. +3. A broker named `default` is created. Currently, all Triggers created by the {operator_name} will read events from `default` == Configuring the workflow @@ -52,7 +58,7 @@ Knative resources are not watched by the operator, indicating they will not unde == Additional resources * https://knative.dev/docs/eventing/[Knative Eventing official site] -* xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc[quarkus extension for Knative eventing] +* xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc[Quarkus extension for Knative eventing] * xref:job-services/core-concepts.adoc#knative-eventing-supporting-resources[Knative eventing for Job service] * xref:data-index/data-index-core-concepts.adoc#_knative_eventing[Knative eventing for data index]