We performed a comparison between Chef and Tekton based on real PeerSpot user reviews.
Find out in this report how the two Build Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"The product is useful for automating processes."
"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 most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"Chef recipes are easy to write and move across different servers and environments."
"The scalability of the product is quite nice."
"Automation is everything. Having so many servers in production, many of our processes won't work nor scale. So, we look for tools to help us automate the process, and Chef is one of them."
"Its seamless integration with Kubernetes, being built on top of it and utilizing Custom Resource Definitions, ensures a smooth experience within Kubernetes environments exclusively."
"Tekton is an orchestrator. It provides seamless integration for our pipelines. It offers robust support for executing tasks within the pipeline, allowing us to set up and run pipelines quickly."
"Tekton is serverless and runs on OpenShift, and we leverage Tekton to take full advantage of the Kubernetes features such as running and scaling the solution in PaaS."
"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."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"Support and pricing for Chef could be improved."
"If they can improve their software to support Docker containers, it would be for the best."
"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."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"They could provide more features, so the recipes could be developed in a simpler and faster way. There is still a lot of room for improvement, providing better functionalities when creating recipes."
"There might be occasional issues with storage or cluster-level logging, which can affect production."
"It tends to occupy a significant amount of disk space on the node, which could potentially pose challenges."
"Configuring Tekton requires a deep understanding of Kubernetes, which can be difficult for developers."
Chef is ranked 15th in Build Automation with 18 reviews while Tekton is ranked 4th in Build Automation with 4 reviews. Chef is rated 8.0, while Tekton is rated 7.0. The top reviewer of Chef writes "Easy configuration management, optimization abilities, and complete infrastructure and application automation". On the other hand, the top reviewer of Tekton writes "A pipeline tool to create CI integrations for applications with ease of use". Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps, BigFix and SaltStack, whereas Tekton is most compared with GitLab, GitHub Actions, Travis CI, Harness and Jenkins. See our Chef vs. Tekton report.
See our list of best Build Automation vendors.
We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
