Tekton Reviews

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.

The platform's most valuable feature is its wireless capability, which makes installation easy and sets up the flow.

The product's UI could be improved, as there are occasional latency issues. The triggering part, especially the CRD installation needs enhancement.

I have been using Tekton for one and a half years. 

The platform could be more scalable. 

The technical community support could be better.

Neutral

The initial setup process is easy. 

The product is free of cost.

We used Tekton to integrate it with different DevOps tools. We used various SaaS tools like Fortify and Jenkins and security tools such as JMeter and Google Lighthouse. 

I rate it a seven out of ten. 

We use Tekton for CI/CD automation, continuous integration, continuous deployment, and general-purpose automation.

The platform's most valuable features are the cloud-native approach and atomicity. Unlike other monolithic solutions, it is early in adopting a cloud-native platform for CI/CD, which enhances scalability. Additionally, its ability to operate at a granular level allows us to create small automation jobs and combine them into larger tasks, making it very useful.

One project involved automating our deployment processes across multiple environments. By leveraging the solution, we reduced deployment times significantly and increased reliability, allowing for more frequent releases and improved overall productivity.

The product's scalability can be challenging when multiple users access it simultaneously. We have seen some resource crunches, typical for any product supporting a large user base. 

One of the main challenges has been managing complex pipeline dependencies. As the scale of our projects, ensuring that all dependencies are correctly defined and executed in the right order can become cumbersome.

Integration is an area where it lags compared to other CI/CD tools like Jenkins, which has a rich plugin ecosystem. It lacks sufficient vendor support for plugins, requiring users to write their integration scripts, which is less convenient.

Enhancements in documentation and user onboarding would be beneficial. Clearer guides and tutorials could help reduce new users' learning curves and facilitate smoother integration with existing workflows.

The support team is knowledgeable and responsive when resolving issues, though improvements in onboarding and documentation could further enhance the overall experience.

Neutral

The initial setup was somewhat complex, requiring a thorough understanding of Tekton's structure. Once configured, it provided a flexible and scalable solution for our CI/CD needs.

We implemented the product with the help of our in-house team. 

We evaluated other CI/CD tools before choosing Tekton. Tekton's flexibility and cloud-native approach were key factors in switching.

The platform's custom tasks feature allows organizations to create standardized team tasks. It enables enterprises to build a flexible framework atop Tekton, making it easier to define workflows with standard inputs and outputs.

It does not differentiate between continuous integration and deployment, offering a unified framework. It provides tooling to run code that builds or deploys applications, allowing for flexible task configurations and parallel processing.

We manage version control through Git repositories, where we store our Tekton pipeline definitions. It allows us to track changes and revert to previous versions, maintaining a robust versioning system for our CI/CD processes.

It has the potential to be a long-term solution due to its scalability and flexibility. However, continuous improvements in user experience and community support will be key factors in its sustained adoption within our organization.

Security is managed through role-based access controls (RBAC) and secret management features. We ensure that sensitive information, such as API keys, is stored securely and that only authorized users can access critical pipeline functions.

Overall, I rate it a six out of ten.

We have our automation pipeline in Tekton. We create pipelines, basically pipelines, to run automated customer scenarios through our automation, Bash scripts, and Golang. To execute these tests routinely, we have implemented those pipelines in Tekton.

Tekton's integration capabilities enhance our development workflows. The product we are testing is also based on Kubernetes and containers, as is Tekton. At the end of the day, we use similar files and languages. 

So, it integrates pretty well. We use it through OpenShift pipelines on the OpenShift platform. The updates are automated, so we don't have to worry about them too much.

I like that you can parallelize tasks. If two tests are not conflicting, you can run them in parallel. This saves time. You can also test pipelines locally if they are not working. 

Additionally, I like the branching and visualization tools for the pipeline. I can easily share an image with someone, and they can understand the pipeline's structure.

Compared to traditional tools like Jenkins, Tekton lacks a lot of features. It's not efficient in managing conflicts between multiple pipelines. If I execute a test and someone else executes a test, we face lots of conflicts and overwriting of each other's work. That's one area for improvement.

Also, the reliability of Tekton is sometimes an issue. I think it's more of a Kubernetes-related issue than a Tekton issue. There are more outages than we expect. 

We have a strict requirement of running tests four to five times a day, and sometimes it's not able to provision the pipeline on time, so we lose test runs.

I have been using it for two years. 

We have had stability issues, but on my side, it was more dependent on Kubernetes, the platform we used. But it depends on the deployment model. 

I would rate the stability a seven out of ten. 

No issues with scalability. I can estimate that around 20 teams, with an average of four people per team, use it, so around 80 people use it. 

The customer service and support have been excellent. We have an internal deployment of Tekton, so the support team is also internal.

Positive

It's easy, but it depends on which distribution you use. The Google one, I haven't tried. Because it is easy on RedHat one. 

Challenges:

There are too many files to change if you have to make any minor source code changes. It becomes difficult to review (if someone has changed something) and assess the impact of those changes on other tasks or pipelines. There's too much friction in terms of making small changes.

Tekton is an open-source tool, and we use it directly. Red Hat has its own distribution of Tekton.

We have our own internal deployment, so we don't pay anything.

Overall, I would rate the solution a seven out of ten because there are lots of areas for improvement.

I would recommend it to someone who is well-versed in Kubernetes and can debug internal issues, not to any newcomers. I would suggest they explore traditional legacy tools first.

I use it for the CI/CD pipeline. The client wanted to create a pipeline for this workflow to be deployed in his kubernetes cluster whenever he made changes. We had three different pipelines for three stages: one for dev, one for production, and the other for QA. The client was unfamiliar with this process, so he wanted us to create three different environments to eliminate manual processes.

With the help of Tekton Hub, we accessed example tasks that were very useful for everyone involved. From that hub, we took a sample task and created our own. It was straightforward to set up. We built the software image, and once that was done, we implemented the deployment process in the same pipeline, where the Helm Chart gets updated with the image name using the check command.

We also integrated the branch nodes through the request process, making it easy to trigger deployments cleanly. Compared to other tools like Argo CD and Argo Workflows, we found them very helpful, as they require different UIs and workflows.

The most valuable features are trigger functionality and the dashboard because they easily highlight our errors. Tekton allows us to see both CI/CD in one place. Unlike other products, Tekton makes managing the entire CI/CD process much easier than separating it into different parts. 

Tekton could use better documentation. We struggled due to the lack of clear documentation for triggers. Everything else was documented very well, but that section needs improvement.

I have been using Tekton for one year.

Tekton is very stable. They release a beta version approximately every two months, but they maintain the stable version until they are confident that the beta version is ready for use.

Scaling up and down is straightforward. The cleanup process in the pipeline section is also very easy. We can quickly delete any tasks.

We never had a chance to contact the support team.

Tekton is open source, so we never encountered any pricing issues. We were able to use it free of cost from end to end.

I was part of the DevOps team, and once our developers completed their code, it was easy for us to trigger workflows. When they wanted to deploy to different environments, like from development to QA and then to production, Tekton made it very user-friendly. Developers often lack knowledge of operations, so they don’t always know how to trigger processes. With Tekton, we managed to achieve this seamlessly without requiring developer intervention.

Tekton is easy to use for someone familiar with the CI/CD process and who has experience with manual authorization and deployment in Kubernetes. There may be a learning curve for beginners, but anyone with basic knowledge of Docker and Kubernetes will find it easy.

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