Uploaded image for project: 'Serverless logic'
  1. Serverless logic
  2. SRVLOGIC-7

[core] Simplified serverless knative function invocation

    XMLWordPrintable

Details

    • Feature
    • Resolution: Done
    • Major
    • 1.28.0
    • None
    • serverless-workflow
    • None
    • False
    • None
    • False
    • 0
    • 0% 0%
    • 2022 Week 41-43 (from Oct 10), 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)

    Description

      Motivation

      Knative/Kubernetes resources such as KN Service, Service, Ingress, Deployment, Pods, and more 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.

      Goal

      Simplify invocation of serverless knative functions from serverless workflows

      Scenarios

      As a developer, I want to define endpoints of serverless functions in serverless workflow operations dynamically based on their service name in the namespace, see the examples below:

      1. knative:mynamespace/func1 -> the func1 Knative Service in mynamespace
      2. knative:func2 -> the func2 Knative Service in the same namespace

      As a developer, I don’t want to add OpenAPI to a serverless function in order to be able to call it from a workflow.

      Expected outcomes

      Function operation can use new formats knative: and kubernetes: for defining endpoints dynamically.

      Serverless functions doesn’t require OpenAPI and will be called directly via HTTP requests

      Attachments

        Issue Links

          incorporates

          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

          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

          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-7373 [SW] Add custom function knative

          • 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 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-8496 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.
          • Resolved
          relates to

          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

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-8860 Include relevant serverless workflow examples in the productized profile

          • 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
              ibek1@redhat.com Ivo Bek
              Marian Macik Marian Macik
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: