Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-7433

Create a working design for the Kogito Serverless Workflow CRD

    XMLWordPrintable

Details

    •  Serverless Workflow CRD Design
    • False
    • None
    • False
    • Documentation (Ref Guide, User Guide, etc.)
    • To Do
    • 100
    • 100% 100%
    • ---
    • ---

    Description

      The goal of this epic is to produce a working design for the Kogito Serverless Workflow CRD as described here: https://docs.google.com/document/d/1JIoFwNf4TE4gSsbRv6Bl-tyf4s5XKkowNfkffOX-X6A/edit#heading=h.h5qkxnjpiw17

      A proof of concept is shared in this repository: https://github.com/davidesalerno/kogito-serverless-operator

      Attachments

        Issue Links

          is depended on by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SRVLOGIC-48 [deliverable][use case] Workflow API on OpenShift (CRD) (community only)

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. KOGITO-7498 Kogito Serverless Workflow Builder Image

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. KOGITO-8048 Stabilize the code of the PoC of the Kogito Serverless Workflow CRD

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              dsalerno@redhat.com Davide Salerno
              dsalerno@redhat.com Davide Salerno
              Tristan Radisson Tristan Radisson
              Tristan Radisson Tristan Radisson
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: