kurator
kurator copied to clipboard
[FR] The realization of pipeline.
This page lists the requirements for The realization of pipeline.
for more details, see #476
Requirements:
-
[x] Pipeline API: #478
-
[ ] Render template:
-
- [x] RBAC #494
-
- [ ] PredefinedTask: Simply renders the task with default parameter values, which means parameters are pre-configured. #541
-
- [ ] CustomTask: A one-step process to render all essential information; no parameter configuration required.
-
- [ ] Pipeline: Both PredefinedTask and CustomTask can be directly utilized in Pipelines without the need for passing parameters.
-
- [ ] Trigger
- [ ] PredefinedTask:
-
- [ ] Git clone:
-
- [ ] Lint
-
- [ ] UT
-
- [ ] Build image
-
- [ ] Upload image
- and so on
-
[ ] Reconciler for Render Tekton Resource:
-
[ ] Kurator pipeline cli:
-
- [ ] Get pipeline excution log and status
-
- [ ] Install Tekton, optional
- [ ] Docs:
-
- [ ] How to create github secret
-
- [ ] How to create OCI registry secret
-
- [ ] How to config a gateway service to route trigger
-
- [ ] How to use PredefinedTask
-
- [ ] How to use CustomTask
-
- [ ] How to manage your supply chain security
/assign
PredefinedTask Rendering:
PredefinedTask directly render default parameter values for existed task, eliminating the need for user configuration. This method is efficient for standard tasks, reducing setup complexity and expediting the process. It is based on class Tekton catalog task
CustomTask Rendering:
CustomTask rendering automates the entire task setup, requiring no parameter input from the user. It's designed for complex tasks, providing a ready-to-use configuration with all necessary details included. It is means that, user need provide enough info about the task excution.
Pipeline Integration:
Both PredefinedTask and CustomTask are engineered for direct integration into Pipelines, no more need any parameter passing.