Tekton Pipelines – K8s-style resources for declaring CI pipelines

https://github.com/tektoncd/pipeline

by based2 • 7 years ago

83 20 7 years ago

github.com

samtrack2019• 7 years ago

Interesting but is it another argocd?

based2• 7 years ago

https://argoproj.github.io/argo-cd/

thanatos_dem• 7 years ago

Yeah, pretty similar overall. Tho Tekton is also the underlying technology for Jenkins X. With Jenkins being such a common system in the CI/CD space, I think we'll see Tekton preferred going forward.

https://jenkins-x.io/

dlor5• 7 years ago

A closer comparison would be to Argo Workflow. Tekton and Argo Workflow provide ways to declare workflow pipelines for execution on Kubernetes. Tekton focuses on source based workflows, while Argo is more general purpose.

We've been working with the Argo team to make sure Argo CD works well with Tekton, and we now have a first-class integration in the tekton catalog, contributed by that team.

Disclosure: one of the leads and founders of the Tekton project.

product1087• 7 years ago

How much, if at all, has the investment from Google in open source projects like Tekton changed at all with the post-Diane Greene leadership?

dcosson• 7 years ago

Would you normally recommend running tekton in its own k8s cluster, or within the same cluster that runs production workloads? (Particularly if running in something like gke or eks)

jessesuen• 7 years ago

Lead and core contributor to Argoproj here.

I agree that Tekton and Argo Workflows share a closer comparison than with Argo CD (despite the "CD" acronym appearing in the name Tekton CD). Workflows is aimed to be a more general purpose workflow engine. I like to explain workflows as a fancy Kubernetes Job object, which can be used as a building block to higher level applications.

I believe the majority of workflow users are using workflows for ML, ETL, data processing pipelines. Its strength is being able to leverage your kubernetes cluster as an auto-scaling compute grid, with highly advanced scheduling capabilities (i.e. scheduling based on node attributes, pod priorities, resource requirements, etc...). That said, a fair share of users are using workflows as a lightweight CI solution, though it requires work to glue in other components to provide the complete solution (e.g. Argo Events to handle git webhooks)

empath753• 7 years ago

This handles the ci part. Argo handles the cd. I use them both together now.

dlor5• 7 years ago

I'd love to hear more about how you're using them if you don't mind sharing. I work on Tekton at Google.

RickJWagner• 7 years ago

Looks like a pretty strong string of commits. This one has some mojo.

je42• 7 years ago

is there a good resource to read up how does this differs from the normal K8S tasks ?

war1025• 7 years ago

I literally just today bought a Tekton [1] torque wrench and was wondering what business they had that required CI pipelines.

Different company.

[1] https://www.tekton.com/

powerball• 7 years ago

The focus on source based flows is the right product decision here --- wonder if it unnaturally constrains the market and effectively cede ubiquity to a more generic tool

What is the plan here?

dlor5• 7 years ago

I think most things in software trade-off between general purpose and specialized.

My 2c is that we'll see more and more things become source-based over time. We're already seeing it with infra as code, gitops, git-ml, etc.

If the scope of Tekton expands, it will be because more things become source-based. And that would be great for everyone.

Disclosure: one of the leads and founders of Tekton, at Google.

Tekton Pipelines – K8s-style resources for declaring CI pipelines

Related Stories