-
Feature
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
-
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)
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:
- knative:mynamespace/func1 -> the func1 Knative Service in mynamespace
- 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
- incorporates
-
KOGITO-8130 Assess the use of SmallRye Stork as a Service Discovery
-
- Resolved
-
-
-
- Resolved
-
-
KOGITO-7373 [SW] Add custom function knative
-
- Resolved
-
- is related to
-
KOGITO-8496 Knative Serving Extension for Serverless Workflow specification
-
- Resolved
-
- relates to
-
-
- Closed
-
-
KOGITO-8860 Include relevant serverless workflow examples in the productized profile
-
- Resolved
-