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

Knative Serving Extension for Serverless Workflow specification

    XMLWordPrintable

Details

    • Knative Serving Extension for Serverless Workflow specification
    • False
    • None
    • False
    • In Progress
    • 100
    • 100% 100%
    • ---
    • ---

    Description

      Engage with IBM to wrap up the Knative extension for SW spec and adjust Kogito implementation to support it.

      Draft extension: https://hackmd.io/caIcNikDSASCxTX51QJ53w

      The extension was set aside for the time being. So for now, we will enable Service Discovery for Knative Serving functions and calls using the default specification description for functions.

      Users can define functions as (see SRVLOGIC-7):

      knative:mynamespace/myservice

      By default, the workflow will POST to this Knative Endpoint. A user can optionally call this function using CloudEvents too. See https://sonataflow.org/serverlessworkflow/latest/integrations/custom-functions-knative.html

      Attachments

        Issue Links

          is incorporated by

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. SRVLOGIC-137 Knative Serving Extension for Serverless Workflow specification

          • 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.
          • ON_QA
          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. SRVLOGIC-249 SonataFlow Operator integration with Knative Eventing

          • 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.
          • In Progress

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. KOGITO-8492 Implement Serverless Workflow custom function for Kubernetes

          • 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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. KOGITO-8493 Implement Serverless Workflow custom function for OpenShift

          • 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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. KOGITO-8494 Improvements to Service Discovery Property Expansion

          • 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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. KOGITO-8500 Use SmallRye Stork in Service Discovery

          • 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.
          • Closed

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. SRVLOGIC-7 [core] Simplified serverless knative function invocation

          • 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.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-7863 [SW] Support alias for common resource names in the Service Discovery URI

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              hbelmiro@redhat.com Helber Belmiro
              hbelmiro@redhat.com Helber Belmiro
              Dominik Hanak Dominik Hanak
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: