-
Epic
-
Resolution: Done
-
Major
-
1.42.0.Final
-
Support Data Index Deployment on Kubernetes
-
False
-
None
-
False
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
---
-
---
-
-
Currently, the only way to use Data Index on Kubernetes is the SonataFlow in dev mode. It's an embedded version not suitable for production usage.
Ideally, the operator should be able to:
1. Deploy one Data Index per Namespace. It could be attached to a SonataFlowPlatform instance
2. Configure Data Index to use the preferred messaging method: either Kafka or Knative
3. Configure Data Index Postgres connectivity
4. Configure the SonataFlow instances within the namespace to use the deployed Data Index.
This EPIC's scope is:
1. Assess a manual Data Index deployment and configuration to serve as a basis to automate the deployment and management by the operator.
2. Implement the actual Data Index management by the operator (one instance per namespace).
- blocks
-
KOGITO-9930 [Operator] Cluster-Scoped Supporting Services in SonataFlow Operator
- Resolved
- is cloned by
-
KOGITO-9742 [Operator] Support Jobs Service Deployment on Kubernetes
- Resolved
-
KOGITO-9931 [Operator] Support configuring workflows against central services
- Closed
- is depended on by
-
KOGITO-9915 [Operator] Auto-configure persistence on workflows based on SonataFlowPlatform
- Closed
-
FLPATH-598 Provide a method to deploy the backend services
- Closed
-
KOGITO-9813 [Operator] Push SonataFlow flow definition and deployment information to Data Index
- Closed
- is related to
-
KOGITO-9658 Provide metadata to identify to which SWF construct a given process definition node is associated to
- Resolved
-
SRVLOGIC-272 Persistency and schema initialization handling
- ON_DEV
- relates to
-
KOGITO-8784 Review SonataFlow Operator Prod Profile
- Resolved