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."It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"If you're handy enough with DSL and you can present your own front-facing interface to your developers, then you can actually have a lot more granular control with Chef in operations over what developers can perform and what they can't."
"It has been very easy to tie it into our build and deploy automation for production release work, etc. All the Chef pieces more or less run themselves."
"The scalability of the product is quite nice."
"The product is useful for automating processes."
"We have had less production issues since using Chef to automate our provisioning."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"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."
"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."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"I would also like to see more analytics and reporting features. Currently, the analytics and reporting features are limited. I'll have to start building my own custom solution with Power BI or Tableau or something like that. If it came with built-in analytics and reporting features that would be great."
"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."
"The solution could improve in managing role-based access. This would be helpful."
"Since we are heading to IoT, this product should consider anything related to this."
"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 is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"Configuring Tekton requires a deep understanding of Kubernetes, which can be difficult for developers."
"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."
Chef is ranked 13th in Build Automation with 18 reviews while Tekton is ranked 3rd in Build Automation with 3 reviews. Chef is rated 8.0, while Tekton is rated 6.4. The top reviewer of Chef writes "Useful for large infrastructure, reliable, but steep learning cureve". On the other hand, the top reviewer of Tekton writes "Provides seamless integration for pipelines, allowing easy setup and execution of tasks but working with YAML files in Tekton can be challenging to modify ". Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps, Microsoft Configuration Manager and BigFix, whereas Tekton is most compared with GitLab, GitHub Actions, Harness, Travis CI 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.