Tekton Reviews

I primarily use Tekton for continuous integration purposes. When we build applications, we use Tekton for CI. For deployments, we use ArgoCD. Most of the time, we use Tekton to facilitate the CI process.

Tekton is primarily a time-saving solution. While it does take some time to set up initially, it is very efficient once running. It helps manage deployments and separates processes accordingly, which benefits both developers and me. Developers don't have to worry about the deployment or integration part as Tekton takes care of those aspects, making it easier for me to manage the pipeline.

Tekton allows you to categorize tasks according to your needs and minimizes the amount of code needed. For instance, you can separate tasks to suit your requirements. Additionally, when integrating with Terraform, Tekton makes it easy to trigger only specific parts of the infrastructure, which is beneficial for ops engineers.

For infrastructure deployment, integration is somewhat complex, especially when using Terraform with Tekton. It would be beneficial if this process were simplified.

I have been working with Tekton for about one year now.

Sometimes, when there are updates and patches, it can cause issues. For example, building a Docker image may require changing the base image due to upgrade issues. However, understanding Tekton properly helps in resolving such issues easily.

Tekton is very scalable. It's particularly effective for managing resources across multiple clusters and regions, integrating resources from different cloud providers.

Before Tekton, I used Jenkins and GitHub Actions for CI/CD pipelines. I also used Bitbucket pipelines for smaller web-related projects. These options required maintaining multiple pipeline files, unlike Tekton, which allows for streamlined categorization and management.

For infrastructure deployment, we categorize each Terraform file according to the specific components needed, such as VPCs and subnets. We maintain separate repositories for Tekton files and deploy specific components by providing the necessary paths and executing the appropriate files. Depending on whether it's a development or production environment, we maintain the appropriate pipelines.

I'd rate the solution eight 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.

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.

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.

At our company, we use Tekton for the deployment pipeline, and it's also implemented in the Kubernetes cluster. Tekton manages the CI/CD pipeline processes. 

The flexibility of Tekton is the most valuable feature. Multiple pipelines can be built using Tekton, and the solution acts as an operating system for the CI/CD operations. 

Tekton lacks sufficient documentation, which makes it quite difficult for startups to handle the product. 

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

In our organization, we have faced some issues with the stability of the solution. It's unclear to our company team that how the product handles the APIs, because resources are available for Tekton with varying API versions. The aforementioned fact creates confusion about which API version to use in Tekton which can be solved only by thorough reading of the documentation. But at our company, we haven't faced any bugs in the solution. 

It's a scalable product. There are about five Tekton users in our organization. 

Our organization's issues with the solution were solved using the documentation and the GitHub repository. 

At our company, we are planning to switch to a simpler solution than Tekton due to its lack of documentation and simplicity. 

At our company, we are able to install Tekton seamlessly without any issues. 

At our company, we used the open-source version of Tekton to manage the infrastructure. 

The main trouble with Tekton is that you need to understand the native concepts and the instructions that can be used to manage the pipeline. I would advise others to use Tekton only for complex deployment processes and also if there is a need to integrate the CI/CD software within the Kubernetes cluster for cost-effective reasons, otherwise simpler solutions like GitHub Actions can be used.

Everyone should gain sufficient knowledge and training on Tekton before using the product. Once a team has adopted Tekton, switching to another product can be difficult. 

Tekton allows integration to make the deployment process smoother. In our company, Tekton is implemented within the cluster and thus actions like AWS resource modifications, addition of images to the container registry and permission updates can be carried out to improve organizational capabilities and efficiency in deploying applications. 

A beginner with a proper understanding of Tekton documentation, implementation and knowledge of CI/CD processes will probably not face any difficulty with the product. I would overall rate Tekton a seven out of ten. It's a high-end solution and if a user has enough time and resources, then Tekton can be used to solve every issue regarding deployment processes. Organizations with small teams should rather choose an easier solution than Tekton. 

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 the solution in CI/CD pipelines for application deployment. 

The tool's most valuable aspect is its compatibility with the cloud-native environment. It can be easily installed on Kubernetes and leverages its resources to run CI/CD pipelines.

Some of the tool's cons include its minimalistic dashboard, which lacks detailed information and control compared to other tools like Jenkins or GitLab. Additionally, it's primarily used by Japanese companies.

Another drawback is its dependency on the Kubernetes cluster for deployment, which could be a limitation. One feature I would like to see included or enhanced in Tekton is the ability to reuse specific pieces of pipelines as reusable modules.

I didn't choose this tool because they already used it when I joined this company. I don't like this tool because it has many limitations. I believe many other tools are better than Tekton.

Integration with other solutions involves mainly API calls. Tekton lacks a mature dashboard, making integration more challenging than tools like GitLab or Jenkins.

I encountered some challenges, particularly with compatibility between different versions of Tekton and Kubernetes. For example, the Tekton version couldn't be installed on Kubernetes version 1.24 due to compatibility issues. Some versions of Tekton don't support certain Kubernetes features, leading to installation issues. It depends on Kubernetes, and matching Tekton versions with compatible ones is essential.

The tool has increased our operational costs due to the need for repetitive tasks and code duplication. Unlike other tools like GitLab or Jenkins, it often requires duplicating resources across clusters or regions. This duplication elevates maintenance costs, as any code changes must be applied in multiple locations.

I have been working with the product for ten months. 

The solution is stable, and I haven't encountered any performance issues. 

I find Tekton to be scalable. It leverages Kubernetes as its underlying system, allowing for scalability. For instance, if you need to run numerous concurrent jobs, Tekton can accommodate this requirement. My company has 70-100 users. 

We have deployed Tekton across multiple locations, departments, and cross-tenants. It has been used for about three or four years and is utilized by various teams to deploy applications in different clusters and locations.

Since the tool is open-source, we resolve issues ourselves. 

The installation process is straightforward, which stands out as one of Tekton's notable advantages. Deploying a YAML file onto your Kubernetes cluster is all it takes, and the installation on Kubernetes is quick. I believe it's achievable in less than a minute. In contrast, other tools like GitHub or Jenkins often require significant setup time.

There is minimal ongoing maintenance required. However, upgrading to the latest version can sometimes be challenging due to compatibility issues between Tekton and Kubernetes. Upgrading Tekton may also necessitate upgrading the Kubernetes cluster, which can incur additional maintenance costs.

The tool increases our operational costs because it requires repetitive tasks. Other tools like GitLab or Jenkins can reduce costs, as they eliminate much of this repetition. Currently, we often need to duplicate resources. For example, if we want to install based on manifests in a new cluster, we must copy all the base modules to another cluster and keep them in the repository. This duplication can increase the maintainability costs, as any changes to the code must be made in multiple places.

The tool is open-source and free to use. 

I wouldn't recommend the product to others. I recommend GitLab for anyone looking to work on mature CI/CD pipelines. I rate the overall product a four 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.