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

[Operator] Knative Functions discovery in the Serverless Operator

    XMLWordPrintable

Details

    Description

      The operator must be able to discover the Knative Function address and bind that address to the function definition as defined in the extension (https://hackmd.io/caIcNikDSASCxTX51QJ53w). Additionally, the runtime/builder image must not have any discovery add-on in their classpath since it's the operator's responsibility to add the discoveries to the functions catalog during the reconciliation cycle.

      We will detach the Kogito SW Runtime discovery from the internal cache/catalog.

      Attachments

        Issue Links

          depends on

          Task - Represents a small unit of work that is not end-user facing. KOGITO-8013 [SW] Enhance Service Discoverability: Improve example to use the 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-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

          Task - Represents a small unit of work that is not end-user facing. KOGITO-8770 [SPIKE] [SW] Reassess the Kubernetes/Knative discovery and internal catalog to keep them independent

          • 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-7755 Manage Functions included in a Workflow with 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

          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-8766 [SW] Adjust the Knative Function definition to use the same interface as defined by the extension

          • 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
          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-8297 Improve the build and deploy user experience for a Workflow using 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.
          • Resolved

          Activity

            People

              rhn-support-fspolti Filippe Spolti
              hbelmiro@redhat.com Helber Belmiro
              Tristan Radisson Tristan Radisson
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: