Summary
This user story describes a use case where user needs to have a singleton Job Service instance in the same namespace a Data Index on Kubernetes with Postgresql database.
User is able to configure callbackstatetimeouts with persistence or with no persistence and their configuration allows registering process events on Data Index Sevice and create timers in Job Service.
Postgresql instance from data index should be reused in Job Service.
We should consider allowing user o deploy the DB first ( not as part of DI deployment )

Procedures
These are the steps this JIRA implements:

• Prerequisite
• Use Case 3 - Single Workflow with singleton Data Index Service and Job Service
• Use Case 3 ( with persistence ) - Single Workflow with singleton Data Index Service and Job Service where DB tables are created by user

Goal
As a serverless logic user
I want to have singleton Data Index service with Postresql and Job Service with Postresql persistence that is configured to register job status events in the Data Index service.
I want to be able to configure the workflow to register process events in Data Index.
I want to be able to configure the workflow to create timers on the Jobs Service.
I want to be able to deploy a workflow with operator that requires timers.

Acceptance criteria
User is able to perform the use case.
No blocker or critical issues are open.