You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this task, we will create a new guide helping users to integrate workflows, Data Index, and Jobs Services applications with Knative Eventing.
These services already support communication via HTTP CloudEvents. Users can create SinkBindings and Triggers to make these services communicate via events.
@fjtirado this explanation is good, but, don't consider a full operator managed deployment, where, the WF, DI and JS deployments, configurations, etc, are fully operator managed.
So the user will have to do manual configurations but not in classic quarkus project, instead, in the operator CRDs, etc
In this task, we will create a new guide helping users to integrate workflows, Data Index, and Jobs Services applications with Knative Eventing.
These services already support communication via HTTP CloudEvents. Users can create SinkBindings and Triggers to make these services communicate via events.
In this guide, we will instruct users to create these objects and make the architecture available in the cluster. A viable example can be seen here: https://github.com/flows-examples/techpreview2/tree/main/platforms/data_index_and_jobservice_as_platform_service_postgresql_persistence_knative_eventing_manual
In future versions, the operator will manage these objects automatically.
The text was updated successfully, but these errors were encountered: