Try our new research platform with insights from 80,000+ expert users

Chef vs Tekton comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Chef
Ranking in Build Automation
17th
Average Rating
8.0
Reviews Sentiment
7.9
Number of Reviews
19
Ranking in other categories
Release Automation (6th), Configuration Management (17th)
Tekton
Ranking in Build Automation
2nd
Average Rating
7.6
Number of Reviews
36
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of December 2024, in the Build Automation category, the mindshare of Chef is 0.4%, down from 0.7% compared to the previous year. The mindshare of Tekton is 12.0%, up from 9.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Arun S . - PeerSpot reviewer
Useful for large infrastructure, reliable, but steep learning cureve
Chef can be scaled as needed. The Chef server itself can scale but it depends on the available resources. You can upgrade specific resources to meet the demand. Similarly, with clients, you can add as many clients as you need. Again, this depends on the server resources. If the server has enough resources, it can handle the number of servers required to manage the infrastructure. Chef can be scaled to meet the needs of the infrastructure being managed. The solution is good to manage multiple large infrastructures. We can have 10 to 10,000 users using this solution and it manages them well.
AjayKrishna - PeerSpot reviewer
If you're dealing with many applications and need a reliable, scalable, and efficient system, I'd recommend this solution
Tekton's most important feature is its cloud-native nature. Unlike Jenkins, which may not scale as efficiently, Tekton's CI pipeline can automatically scale up to handle increased workload demands without needing manual adjustments. Another important aspect is the level of customization offered by Tekton. Each task in the CI pipeline can be customized independently, allowing developers to write code in various languages like shell scripting, Java, or Python and incorporate them into the pipeline as needed. This level of abstraction and customization greatly benefits developers in creating efficient CI pipelines. Also, it can be challenging to understand the logs and troubleshoot issues without clear guidance. It's not always easy to reach technical support and get immediate answers. In my opinion, improvement in this area would be beneficial.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The scalability of the product is quite nice."
"Deployment has become quick and orchestration is now easy."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"This solution has improved my organization in the way that deployment has become very quick and orchestration is easy. If we have thousands of servers we can easily deploy in a small amount of time. We can deploy the applications or any kind of announcements in much less time."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"The most valuable feature is the language that it uses: Ruby."
"I wanted to monitor a hybrid cloud environment, one using AWS and Azure. If I have to provision/orchestrate between multiple cloud platforms, I can use Chef as a one-stop solution, to broker between those cloud platforms and orchestrate around them, rather than going directly into each of the cloud-vendors' consoles."
"Tekton provides a feature where you can schedule the job."
"I find it beneficial to show data from Tekton to another GitHub or Bitbucket pipeline."
"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."
"I like the branching and visualization tools for the pipeline."
"We just have some configuration files, and it will handle the deployments smoother and faster compared to CI/CD 2.0."
"The installation process is seamless, requiring fewer resources compared to Jenkins."
"The most valuable features of Tekton include the reusability of tasks, the clean UI interface, and the binding of services and secrets."
"You can isolate most Tekton assets in the Kubernetes namespace for your feature branch. This allows you to freely change Tekton assets and objects to adapt to your feature branch and requirements."
 

Cons

"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"I would rate this solution a nine because our use case and whatever we need is there. Ten out of ten is perfect. We have to go to IOD and stuff so they should consider things like this to make it a ten."
"Since we are heading to IoT, this product should consider anything related to this."
"There appears to be no effort to fix the command line utility functionality, which is definitely broken, provides a false positive for a result when you perform the operation, and doesn't work."
"I would like them to add database specific items, configuration items, and migration tools. Not necessarily on the builder side or the actual setup of the system, but more of a migration package for your different database sets, such as MongoDB, your extenders, etc. I want to see how that would function with a transition out to AWS for Aurora services and any of the RDBMS packages."
"Support and pricing for Chef could be improved."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"Tekton lacks sufficient documentation"
"Improvements could include introducing a UI-based pipeline development feature, such as drag and drop, which would help individuals with limited technical knowledge start building pipelines."
"The tool should improve in terms of output flexibility. It runs on a specific Kubernetes machine, and the persistent memory storage is on a single partition. Improving this aspect could make analyzing logs and toolchain outputs from external tools easier."
"The product's documentation is an area of concern, making it an area where improvements are required."
"It would be beneficial to find case studies or more information on complex implementations."
"The product's version update management process needs improvement."
"Tekton lacks integration capabilities compared to other CI/CD tools like Jenkins and Travis."
"Tekton is a good product with all the features I need. There isn't anything that needs improvement."
 

Pricing and Cost Advice

"Purchasing the solution from AWS Marketplace was a good experience. AWS's pricing is pretty in line with the product's regular pricing. Though instance-wise, AWS is not the cheapest in the market."
"Pricing for Chef is high."
"Chef is priced based on the number of nodes."
"I wasn't involved in the purchasing, but I am pretty sure that we are happy with the current pricing and licensing since it never comes up."
"The price per node is a little weird. It doesn't scale along with your organization. If you're truly utilizing Chef to its fullest, then the number of nodes which are being utilized in any particular day might scale or change based on your Auto Scaling groups. How do you keep track of that or audit it? Then, how do you appropriately license it? It's difficult."
"The price is always a problem. It is high. There is room for improvement. I do like purchasing on the AWS Marketplace, but I would like the ability to negotiate and have some flexibility in the pricing on it."
"We are able to save in development time, deployment time, and it makes it easier to manage the environments."
"We are using the free, open source version of the software, which we are happy with at this time."
"The product is free of cost."
"Tekton is an open-source tool."
"The tool is open-source and free to use."
"The solution is open-source."
"It is entirely open source and free of charge."
"The product is free and open-source."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
817,354 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
23%
Computer Software Company
15%
Manufacturing Company
6%
Retailer
6%
Financial Services Firm
23%
Manufacturing Company
15%
Computer Software Company
13%
Government
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Chef?
Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code.
What needs improvement with Chef?
Chef does not support the containerized things of Chef products. In the future, Chef could develop a docker container or docker images.
How does Tekton compare with Jenkins?
When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requirements and use cases in mind. Tekton deployment is complex and it is not very e...
What do you like most about Tekton?
Its seamless integration with Kubernetes, being built on top of it and utilizing Custom Resource Definitions, ensures a smooth experience within Kubernetes environments exclusively.
What needs improvement with Tekton?
Regarding areas for improvement in Tekton, I have not encountered significant issues. It works well for our use case. However, incorporating AI could be a potential enhancement in the future.
 

Comparisons

 

Learn More

 

Overview

 

Sample Customers

Facebook, Standard Bank, GE Capital, Nordstrom, Optum, Barclays, IGN, General Motors, Scholastic, Riot Games, NCR, Gap
The Home Depot, PayPal, Target, HSBC, McKesson, Oncology Venture
Find out what your peers are saying about Chef vs. Tekton and other solutions. Updated: December 2024.
817,354 professionals have used our research since 2012.