Tekton Reviews

I am using Tekton for continuous integration in our project.

The feature that I like most about Tekton is that it is built for Kubernetes, so we can utilize our resources effectively.

Tekton should have more accessibility for some rare use cases so that we can have more references when applying some techniques to our pipeline.

I have been using Tekton since February.

If we set it up correctly and know exactly what we have done, it is very stable because it runs on top of Kubernetes.

I can't give an opinion right now because I haven't applied the scale to our deployment. It's only in our staging environment.

I haven't contacted support yet since most of my errors are addressed in their GitHub repository.

Positive

I had some experience using Tekton when my company migrated the CI panel from another platform.

The initial setup is rather easy because the tutorial is easy to follow.

Tekton is free to use. It's open source.

I would recommend Tekton to my coworkers if they use Kubernetes most at work. However, if my colleagues don't use Kubernetes, I wouldn't recommend Tekton to them because it is very difficult to understand Tekton if you aren't familiar with Kubernetes.

I'd rate the solution eight out of ten.

The CI solution of the team I worked for was based on Tekton. Since Tekton is a Kubernetes native framework, we can easily configure it within a Kubernetes cluster, which has many benefits.

I would say the customization ability that Tekton provides is good. As an example, if we look at the pipeline structure of Tekton, a Tekton Pipeline was built with Tekton Tasks. We can specify a Tekton Task within the pipeline YAML. Otherwise, we can specify the task in a separate YAML and add it as a reference within the pipeline so that we can use the Tekton Task as a reusable component in other pipelines as well. Another thing is that we can execute a Tekton Task based on conditions such as "when" expressions. Furthermore, Tekton provides Tekton Triggers. We use Tekton Triggers to dynamically execute a pipeline based on an event, which is also a very useful feature for us. These customization features of Tekton made it more valuable and flexible to use for us.

The product's documentation is an area of concern, making it an area where improvements are required.

Apart from the documentation, there is one more thing that I believe needs to improve in Tekton. In the Tekton pipeline structure, there is an optional feature called finally section, where we can add all the core Tekton Tasks, which have to be executed even in a pipeline failure scenario. But the issue is that we cannot give a sequence for the tasks in the finally section, so all the tasks are running simultaneously. I believe if we had a feature to help users add a sequence for the tasks in the finally section, then it would make our lives easier.

The scalability could improve a lot in the future.

I have been using Tekton for a year. I am a user of the tool.

Sometimes, we face some version compatibility issues, but when we upgrade the version, it gets rectified. Stability-wise, I rate the solution an eight out of ten.

I know that there are more than 20 people using Tekton within our company. As the CI solution in our company is based on Tekton, many people, including new joiners, also have to learn Tekton. Scalability-wise, I rate the solution a seven out of ten.

When our company faced challenges with the tool, we had to do our own trials and errors to find a solution. Sometimes, we had to go through some GitHub issues related to the challenges we faced, but most of the time, we couldn't find an exact solution by looking at the GitHub issues. So we had to try to resolve the issues we faced in Tekton with the knowledge we had. We did not contact Tekton's support team.

Tekton's integration capabilities have helped our company's development workflow. Tekton is a Kubernetes native framework, so most of the command lines that we use in Kubernetes could also be used within Tekton framework. Basically, configuring Tekton Pipelines within our Kubernetes cluster was very easy compared to using other solutions. Overall, the development workflow was easy when using Tekton.

As a beginner who is trying to use Tekton, it will take some effort to learn it because the documentation in Tekton has to improve a lot. There are no tutorials to learn about Tekton because I personally learned it from my seniors and my experience and even when we faced challenges in the development, we couldn't find a solution on the internet. We had to do our own trial and error to find a solution, which was one of the main challenges while using Tekton.

I recommend the tool to others as using Tekton makes our lives easier. As far as I know, many companies don't know about Tekton. If they knew that there is something called Tekton, they would definitely adjust to it. 

I rate the tool a nine out of ten.

Our primary use case is for cloud integration and cloud deployment. Tekton is a cloud-native tool that we utilize in Kubernetes and OpenShift. It helps us with code integrations and code deployment. We use it for automating various processes and integrating it with our DevOps environment.

Tekton has improved our performance by allowing us to define metrics and resource limits, enhancing the performance of our whole pipeline. The ability to customize tasks and use custom containers has also allowed us to tailor our workflows to our needs.

The customization is valuable. We can make a lot of customizations, and data sharing between tasks using workspaces is very convenient. Moreover, the flexibility and ease of use in creating and attaching new tasks make it very user-friendly. The Tekton UI and user interactions are very good.

Tekton could improve by adding better documentation. The documentation needs improvement to clarify supported features and required integrations. Additionally, while it is currently a cloud-native solution limited to Kubernetes, an option to run it locally on our own systems would be very useful. Security integrations and third-party integrations also need enhancement.

We have been using the Tekton solution for nearly two years.

Tekton is stable and performs well. However, it would benefit from adding new features quickly to stay relevant and helpful.

Tekton is highly scalable due to its cloud-native nature.

We have not escalated any queries to Tekton itself. Since Tekton comes as an integral part of Red Hat, we rely on existing documentation and haven't had any issues requiring direct technical support.

Neutral

In the past, we used Jenkins for CI/CD. Each tool has its own use case and pros and cons, but Tekton's cloud-native capabilities and ease of deployment and maintenance make it a better fit for our needs.

The initial setup of Tekton is very straightforward. We install it as an operator in our cluster, making maintenance tasks like auto-upgrades and updates easier.

There is no specific cost related to resource optimization provided by Tekton. We need to manage the resource limits and requests ourselves to prevent resource exhaustion, especially when running on cloud platforms like AWS, Azure, or GCP.

I recommend Tekton to anyone closely interacting with Kubernetes. It is particularly useful for larger teams with complex application deployment requirements. However, for smaller teams or simpler use cases, it may not be necessary.

I'd rate the solution six out of ten.

I use Tekton for DevOps work, where developed applications will be deployed into a cloud Kubernetes or any Kubernetes platform. This process includes all the Docker builds and deployment into the cluster and the notification after deployment or any triggers.

Tekton has been used for a project where the client wanted their application to be deployed in a Kubernetes cluster, and Tekton is the tool that enables this deployment process.

I like the setup of the dashboard. We can see all the tasks, the pipelines, and all the triggers in one place. That's the main use case that I like. Also, the Tekton Hub was very useful with a huge community. It was very useful for sourcing tasks and pipelines.

Tekton is a good product with all the features I need. There isn't anything that needs improvement.

I have been using Tekton for about one year.

The stability of Tekton depends on correct implementation. If implemented correctly, it's a very good product. I haven't faced any stability issues myself.

Most of the time, the community is really helpful. I didn't need to contact support because the Tekton Hub and its community provided adequate support.

Positive

We used Flux before. However, we do not really use it now. Now, we use ArgoCD to deploy applications across multiple systems.

The initial setup is straightforward. However, users need to follow the documented steps and version requirements.

Some colleagues in my office had prior experience with Tekton, so I had to help with its implementation.

We have documentation for Tekton content creation for the CNCF course that can be forwarded to help others start using Tekton. I'd rate the solution ten out of ten.

We use Tekton to build and deploy business apps, which include analytics programming in their strategy. Our DeepLab setup involves routers that trigger Tekton within our clusters to build and deploy their strategy as needed.

Tekton is also used in Flutter, eliminating the need for GitLab CI for our setup. While GitLab Runners can handle build and deployment tasks, Tekton offers strong integration with EKS and Kubernetes clusters. 

Tekton is useful for us, especially since we use it for all other deployments and in the cloud. In terms of build and deployment capabilities, it can function similarly to GitLab.

The Helm Chart for Tekton doesn't come with all the manifests needed for installation; you must apply them manually. I use ArgoCD to upgrade and manage Tekton, but manual updates to the Helm charts are still required.

I have been using Tekton for one year.

We have analytics that utilize a negative tone. Around 50 people use this in the cloud. When they need to deploy or release a strategy, they tag it and create a new Tekton task. Tekton then handles building and integrating its strategy within our clusters.

It is open source, like DeepLab Community Edition.

Tekton is easy to use, but updating from older versions can be challenging due to method changes with each release. I've spent a lot of time upgrading it. Once you start using Tekton, you can manage it with just a few files and apply them easily. 

The best documentation for Tekton is their CRD for the operator.

Overall, I rate the solution a six out of ten.

Generally, we are using Tekton for deployments instead of Jenkins. We create pipelines in Tekton for a number of services, each with different logs and requirements, especially in our DevOps practices. I have been using this Tekton pipeline for nearly six months.

The main benefits we have seen from using Tekton include saving time compared to Jenkins. The user interface is easier to use, and there are no plugins required for installation, unlike Jenkins. Time savings and ease of use are significant advantages.

Tekton has a user interface that facilitates time savings, making it more user-friendly than Jenkins. It is easier to handle and eliminates the need for plugin installations.

The user interface of Tekton could be improved. Sometimes, it takes more time during production deployments than expected.

I have been using the solution for nearly six months.

Tekton is stable, easy to use, and currently provides good stability.

Tekton is scalable, and most of our team members are using the Tekton pipeline.

As of now, I haven't asked for technical support. I would approach technical support if I encounter any problems.

Positive

Before Tekton, we used Jenkins. Tekton is better than Jenkins in terms of user interface and ease of integration without the need for plugins.

The initial setup took about one week, and there were some doubts on how to operate and execute deployments. But after learning about the tools, the setup was smooth, and everything was configured properly.

Four teams were involved in the deployment process: the ECS team, tenant ops team, DevOps team, and development team.

There are efficiency gains due to time savings in pipeline setup compared to Jenkins. This is a major point of efficiency for Tekton.

I would recommend Tekton to other users who are considering its implementation. It's better compared to Jenkins.

I'd rate the solution eight out of ten.

I use Tekton generally for CI purposes and automation APIs.

We have created a Helm template for Tekton, and we're currently working on scripts. This allows us to create pipelines on the fly, which has significantly streamlined our workflow.

I have full control over it, actually, in my team. Another thing is that Tekton is based on Kubernetes. In Kubernetes, we have the concept of cron jobs which run on a time-to-time basis. In Tekton, we have the concept called task or task runs. We can expose an API and use the trigger and trigger-binding concept, allowing us to trigger tasks whenever needed. This mechanism is very nice.

RBAC is really needed for Tekton. Also, if you have too many PVCs and don't clean them up, it may stop working due to the limited number of PVCs you can create in a cluster.

I have been using it for the past two years.

Tekton is a stable product. One issue we might run into is when there are too many PVCs that haven't been cleaned up. We have mitigated this by creating a CronJob that runs every midnight to clear those tasks.

Tekton is scalable if well-planned. However, it is not a plug-and-play solution for now. You need to write the tasks according to your business case, which might differ from team to team or service to service.

While setting up, I was initially active on their Slack channel where I was able to get help. They were responsive.

Neutral

We were using Jenkins before Tekton.

The initial setup was daunting and took me four months to set it up and get the flow. There is a steep learning curve, especially with concepts like event listeners, event triggers, and trigger binding.

Tekton was initially very daunting, and it took me a long time to get the flow. However, once you get it, it’s awesome.

I'd rate the solution six out of ten.

I mostly use it for application deployments, it's a CI/CD tool. We use it for Kubernetes application deployment.

Through the API pipelines, through Tekton, it's very easy. We just have some configuration files, and it will handle the deployments smoother and faster compared to CI/CD 2.0. 

It's like Kubernetes nature. We don't require a lot of things for different environments. We can also customize and do the deployment.

People must have the knowledge. Once they have the knowledge, it's quite simple to use if the application is friendly.

It is quite good compared to the other applications. It is very faster than the other applications. It is a very good application.

There might be some compatibility issues and the need for customization during deployment, especially when deploying to different environments.

I've been using it from the last one and a half years.

The stability issues can be there. It is the core level who are doing some developers, they will do. The core level changes will be due to some core level changes; only they will affect it. 

If there is some customization, we can do it through Tekton also, we can do it. It won't be an issue.

I would rate the stability an eight out of ten. 

It's highly scalable, and it's highly available for applications, which are containerized applications. It will be highly available to speed up the application through Tekton.

I would rate the scalability an eight out of ten. 

The scalability means that in the case of the usage of that application, there will be some ins and outs, like some porting issues. There will be there. But, it is like from the deployment phase, they are using it, whether Cloud Run or on-premises, they are doing the deployment. Maybe it will differ, the things. So we need to check the compatibility. It will be available. It is compatible, but we need to customize it from that side. So the customization we need to do, that... that is that's why I have given it only eight. That's my reason.

We can do the deployments. It's based on whether they are deploying cloud or on-premises-related applications or something. It depends upon their code and their deployment style.

Initially, everyone will face challenges, but once they get to know about it, it would be very easy. It's just easy to understand. It's a Kubernetes-native application, so users must have some knowledge in Kubernetes, and users have some CI/CD knowledge. If they are using those, they can use Tekton.

Overall, I would rate it a nine out of ten. Once you are used to it, it is a very user-friendly application. 

Tekton is a great application that simplifies deployments, and customers are happy once their application is up and running, whether through a website or another method. So, it's highly available. If there are any issues, we can now easily deploy continuous updates, and it won't disrupt the application.