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 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 valuable feature is automation."
"Deployment has become quick and orchestration is now easy."
"The most valuable feature is the language that it uses: Ruby."
"We have had less production issues since using Chef to automate our provisioning."
"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"The product is useful for automating processes."
"One thing that we've been able to do is a tiered permission model, allowing developers and their managers to perform their own operations in lower environments. This means a manager can go in and make changes to a whole environment, whereas a developer with less access may only be able to change individual components or be able to upgrade the version for software that they have control over."
"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 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."
"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."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"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."
"If they can improve their software to support Docker containers, it would be for the best."
"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."
"In the future, Chef could develop a docker container or docker images."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"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 might be occasional issues with storage or cluster-level logging, which can affect production."
"Configuring Tekton requires a deep understanding of Kubernetes, which can be difficult for developers."
"It tends to occupy a significant amount of disk space on the node, which could potentially pose challenges."
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.