Loading...

XML

Word

Printable

Type: Feature Request
Resolution: Done
Priority: Major
Fix Version/s: 1.44.0.Final
Affects Version/s: 1.30.0.Final
Component/s: Operator, Serverless Workflow Engine
Labels:
- ksw-tp2

Blocked:
False
Blocked Reason:
None
Ready:
False
[QE] How to address?:
---
[QE] Why QE missed?:
---
Epic Link:
Knative Serving Extension for Serverless Workflow specification
Intelligence Requested:
Market:

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

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.

depends on

KOGITO-8013 [SW] Enhance Service Discoverability: Improve example to use the discovery

Resolved

KOGITO-7373 [SW] Add custom function knative

Resolved

is related to

KOGITO-8770 [SPIKE] [SW] Reassess the Kubernetes/Knative discovery and internal catalog to keep them independent

Resolved

KOGITO-7755 Manage Functions included in a Workflow with Operator

Closed

KOGITO-8766 [SW] Adjust the Knative Function definition to use the same interface as defined by the extension

Resolved

SRVLOGIC-7 [core] Simplified serverless knative function invocation

Closed

relates to

KOGITO-8297 Improve the build and deploy user experience for a Workflow using the Serverless Operator

Resolved

(1 is related to, 1 relates to)

Assignee:: Filippe Spolti

Reporter:: Helber Belmiro

QA Contact:: Tristan Radisson

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2022/12/02 12:27 PM

Updated:: 2023/09/18 7:36 PM

Resolved:: 2023/09/18 7:36 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates