-
Epic
-
Resolution: Done
-
Critical
-
None
-
Include Serverless Function Samples in our Sample Catalog
-
False
-
None
-
False
-
Green
-
To Do
-
OCPSTRAT-621 - Include Serverless Function Samples in Sample Catalog
-
0
-
OCPSTRAT-621Include Serverless Function Samples in Sample Catalog
-
0% To Do, 0% In Progress, 100% Done
-
Feature
-
M
-
Not Supported
Problem:
As a developer of serverless functions, we don't provide any samples.
Goal:
Provide Serverless Function samples in the sample catalog. These would be utilizing the Builder Image capabilities.
Why is it important?
Use cases:
- <case>
Acceptance criteria:
- <criteria>
Dependencies (External/Internal):
- Serverless team would need to provide sample repo for serverless function
- Samples operator would need to be update
Design Artifacts:
Exploration:
Note:
- Need to define the API and confirm with other stakeholders - need to support a serverless func image stream "tag"
- Serverless team will need to provide updates to the existing Image Streams, as well as maintain the sample repositories which are referenced in the Image Streams.
- Need to understand the relationship between ImageStream and Image Stream Tag
- Should serverless function samples in the catalog have "builder image" tag? or should it be "serverless function"