-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Design alternative Task Implementations inside a pipeline #215
Comments
knative/build#236 could be one possible solution |
Ref #781 |
I have following use-cases to add :)
For those, I'd be happy if Tekton provides us API to build and integrate a "custom task controller" in golang, where we have freedom to implement any logics to run the task in the controller. I think we have three ways to achieve it in general:
Add something like a CRD for Tekton TasksThis can possibly be composed of:
One possible question here is - how Tekton fetches "logs" for the specific unstructured K8s resource? For that, I believe we need at least a common interface between Tekton and the controller reconciling the K8s resources, maybe something like Add a dedicated, Tekton-defined CRD for custom tasksAssuming we can use/enhance the existing So it can basically be the same as tekton's The same question about the common interface for fetching logs applies to this as well. Enhance the existing
|
@imjasonh has been working on a design for custom tasks in tekton pipelines |
/assign @imjasonh |
@bobcatfish @imjasonh should this be considered as done as "custom tasks" is a thing now ? |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
With Custom tasks being a thing, I think this can be closed. I'll go ahead and close but if you feel it shouldn't be closed, please comment here and I'll re-open 👼🏼 |
@vdemeester: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Right now A Pipeline is a graph of Tasks, where Tasks are coupled to a Build, which run as a Pod. We'll eventually need to support alternative implementations for the Build/Task execution for cases like:
< other use cases here >
The text was updated successfully, but these errors were encountered: