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

[SW] Add custom function knative

    XMLWordPrintable

Details

    • 2022 Week 44-46 (from Oct 31), 2022 Week 47-49 (from Nov 21), 2022 Week 50-02 (from Dec 12), 2023 Week 03-05 (from Jan 16), 2023 Week 06-08 (from Feb 6), 2023 Week 09-11 (from Feb 27)

    Description

      Knative/Kubernetes resources such as KN Service, Service, Ingress, Deployment, Pods, and so on (see: https://github.com/knative/specs/blob/main/specs/eventing/overview.md#addressable) can be called by a regular HTTP POST request.

      This means that SW could support this feature out of the box, not needing an OpenAPI interface to do so.

      Image this example:

      {
  "id": "myworkflow",
  "specVersion": "0.8",
  "version": "1.0",
  "start": "State1",
  "functions": [
    {
      "name": "function1",
      "type": "custom",
      "operation": "knative:mynamespace/func1",
      "metadata": {
        "path": "/my_path"
      }
    },
    {
      "name": "func2",
      "operation": "knative:func2"
    }
  ],
  "states": [
    {
      "name": "State1",
      "type": "operation",
      "actions": [
        {
          "functionRef": {
            "refName": "function1",
            "arguments": {
              "data": "${ .data }"
            }
          }
        }
      ],
      "end": true
    }
  ]
}

      The engine would make POST requests to these endpoints with the given payload manipulated by the workflow. For example:

      1. knative:mynamespace/func1 -> the func1 Knative Service in mynamespace
      2. knative:func2 -> the func2 Knative Service in the same namespace
      3. kubernetes:serving.knative.dev/v1/mynamespace/myservice -> the explicitly kubernetes resource at mynamespace

      This will make the integration with the platform way easier and enhance the dev experience.

      This feature can leverage our custom legacy function REST already implemented in the engine.

      Attachments

        Issue Links

          clones

          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-6697 [SW] Enhance Service Discoverability

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          is blocked by

          Task - Represents a small unit of work that is not end-user facing. KOGITO-8130 Assess the use of SmallRye Stork as a 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.
          • Resolved

          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-6697 [SW] Enhance Service Discoverability

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          is depended on by

          Feature Request - Feature requests from customers and/or users KOGITO-8410 [SW] Add support for GET method to Knative custom function

          • 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

          Feature Request - Feature requests from customers and/or users KOGITO-8313 [Operator] Knative Functions discovery in the Serverless Operator

          • 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 Request - Feature requests from customers and/or users KOGITO-8430 [Operator] Add support for Kubernetes Functions

          • 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 Request - Feature requests from customers and/or users KOGITO-8448 [SW] Add support to GET method to Kubernetes custom function

          • 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

          Task - Represents a small unit of work that is not end-user facing. KOGITO-8414 [KSW-Guides] Create guide for Knative custom function

          • 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
          is incorporated by

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

          • 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

          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
          is related to

          Feature Request - Feature requests from customers and/or users KOGITO-7377 [Research Spike] - 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

              hbelmiro@redhat.com Helber Belmiro
              rhn-support-zanini Ricardo Zanini Fernandes
              Tristan Radisson Tristan Radisson
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: