Tekton is a cloud-native CI/CD tool preferred for its integration with Kubernetes. It offers customizable pipelines and efficient management of tasks, appealing to those handling complex deployments. Its open-source design and ease of use support its widespread adoption.


| Product | Mindshare (%) |
|---|---|
| Tekton | 5.8% |
| GitLab | 7.7% |
| Jenkins | 7.7% |
| Other | 78.8% |
| Title | Rating | Mindshare | Recommending | |
|---|---|---|---|---|
| GitLab | 4.2 | 7.7% | 97% | 91 interviewsAdd to research |
| VMware Tanzu Platform | 4.0 | 2.3% | 100% | 23 interviewsAdd to research |
| Company Size | Count |
|---|---|
| Small Business | 11 |
| Midsize Enterprise | 4 |
| Large Enterprise | 20 |
| Company Size | Count |
|---|---|
| Small Business | 145 |
| Midsize Enterprise | 65 |
| Large Enterprise | 367 |
Designed for Kubernetes, Tekton provides a robust environment for continuous integration and deployment. It supports cloud-native design, allowing seamless automation of building, testing, and deployment processes. Users benefit from customizable solutions with reusable tasks and parallel execution capabilities, optimizing CI/CD processes via a user-friendly dashboard. Despite its challenges with storage and logging, Tekton remains an adaptable tool that integrates well with other applications, like Argo CD. However, its deployment accessibility, scalability in complex environments, and documentation need enhancement to improve user onboarding and security management.
What features make Tekton stand out?Industries often employ Tekton within Kubernetes and OpenShift for its automation capabilities in CI/CD pipelines. Its use extends to automating build, test, and deployment processes in microservices management. Tekton's integration with tools like Argo CD facilitates superior deployment, making it the preferred choice for efficient orchestration in cloud-native environments over competitors such as Jenkins.
| Author info | Rating | Review Summary |
|---|---|---|
| Software engineer at a manufacturing company with 10,001+ employees | 4.5 | I've used Tekton for build and deployment pipelines for over a year; it's stable, customizable, and integrates well with Kubernetes, but pipeline scalability is still unclear and depends heavily on resource availability. |
| Senior Software Engineer at a transportation company with 10,001+ employees | 4.0 | While working at Deloitte, I found Tekton ideal due to its cloud-native and customizable features, which easily integrated with Red Hat OpenShift. Despite initial limited community support, Tekton offers better scalability and efficiency compared to Jenkins, especially on AWS. |
| Software Engineer at IBM Software Labs | 4.0 | We use Tekton as a CI/CD pipeline in an OpenShift cluster, which efficiently manages tasks like build and deploy, reducing our costs significantly compared to Jenkins. However, improvements in CRD management and security integration are needed. |
| Senior SRE at a tech vendor with 10,001+ employees | 4.5 | I've been using Tekton for almost three years due to its Kubernetes-native functionality, particularly for IBM Cloud Kubernetes tasks. I value its declarative style, better control over pipelines, and lightweight nature compared to Jenkins. |
| DevOps Developer at Ibm India Software Lab Private Limited | 3.0 | I use Tekton for our CI pipeline due to its compatibility with containerized applications and seamless installation. While it's resource-efficient and integrates well with Kubernetes, it lacks integration capabilities and security management compared to Jenkins and Travis. |
| Tech lead at Ford Motor Company | 4.5 | I use Tekton to create and manage CI/CD pipelines for various environments. Its step-by-step management and 'promote' feature are valuable. However, version update management and synchronization with tools like OTEL and Datadog need improvement for ease. |
| Self Employed at Deguene Cloud Adoption Consulting | 4.5 | I primarily use Tekton for CI/CD in cloud-native environments due to its Kubernetes-ready design. It's beneficial for container integration and automation with its custom task feature, though it may not suit bare-metal setups. Previously, I used Jenkins and Concourse. |
| DevOps Lead at IBM | 4.5 | We transitioned from Jenkins to Tekton, enhancing our CI/CD processes with efficient automation and shared tools that save time and resources. However, Tekton could improve by integrating event-driven pipelines for automatic response to security triggers, improving workflow efficiency. |