Kubernetes vs. Progress Chef

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Kubernetes
Score 8.9 out of 10
N/A
Kubernetes is an open-source container cluster manager.N/A
Progress Chef
Score 8.1 out of 10
N/A
Chef IT infrastructure automation suites were developed by Chef Software in Seattle and acquired by Progress Software in September 2020. The Chef Enterprise Automation Stack is an integrated suite of automation technologies presented as a solution for delivering change quickly, repeatedly, and securely over every application's lifecycle. The Chef Effortless Infrastructure Suit is an integrated suite of automation technologies to codify infrastructure, security, and compliance, as well as…N/A
Pricing
KubernetesProgress Chef
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
KubernetesProgress Chef
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Best Alternatives
KubernetesProgress Chef
Small Businesses
Docker
Docker
Score 9.1 out of 10
HashiCorp Terraform
HashiCorp Terraform
Score 8.8 out of 10
Medium-sized Companies
Docker
Docker
Score 9.1 out of 10
HashiCorp Terraform
HashiCorp Terraform
Score 8.8 out of 10
Enterprises
Docker
Docker
Score 9.1 out of 10
SUSE Manager
SUSE Manager
Score 9.1 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
KubernetesProgress Chef
Likelihood to Recommend
8.8
(15 ratings)
8.1
(18 ratings)
Usability
-
(0 ratings)
7.3
(1 ratings)
Performance
-
(0 ratings)
9.4
(10 ratings)
Support Rating
-
(0 ratings)
7.2
(5 ratings)
Contract Terms and Pricing Model
-
(0 ratings)
6.4
(1 ratings)
Ease of integration
-
(0 ratings)
9.7
(6 ratings)
Professional Services
-
(0 ratings)
9.1
(1 ratings)
User Testimonials
KubernetesProgress Chef
Likelihood to Recommend
Kubernetes
K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.
Read full review
Progress Software Corporation
Chef is a fantastic tool for automating software deployments that aren't able to be containerized. It's more developer-oriented than its other competitors and thus allows you to do more with it. The Chef Infra Server software is rock-solid and has been extremely stable in our experience. I would definitely recommend its use if you're looking for an automation framework. And it also offers InSpec which is a very good tool for testing your infrastructure to ensure it deployed as intended.
Read full review
Pros
Kubernetes
  • Complex cluster management can be done with simple commands with strong authentication and authorization schemes
  • Exhaustive documentation and open community smoothens the learning process
  • As a user a few concepts like pod, deployment and service are sufficient to go a long way
Read full review
Progress Software Corporation
  • Chef is great at deploying code to both small and large groups of servers.
  • We use chef to standup new servers as well as deploy updated code to existing servers and it does this very well.
  • Being able to make a change and have it push manually or automatically to any subset of servers has changed the landscape of how our IT teams operate.
Read full review
Cons
Kubernetes
  • Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
  • The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
  • Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.
Read full review
Progress Software Corporation
  • Chef could do a better job with integration with other DevOps tools. Our company relies on Jenkins and Ansible, which took some development and convincing for plug-ins to be created/available.
  • It would be nice if kitchen didn't only have a vagrant/virtual-box prerequisite. Our company one day stop allowing virtual-box to run without special privileges, and that caused a lot of issues for people trying to do kitchen tests.
  • Chef could use more practice materials for the advanced certification badges. There was not a lot of guidance in what to study or examples of certain topics.
Read full review
Usability
Kubernetes
No answers on this topic
Progress Software Corporation
The suite of tools is very powerful. The ability to create custom modules allows for unlimited potential for managing all aspects of a system. However, there is pretty significant learning curve with the toolset. It currently takes approx 3-4 months for new engineers to feel comfortable with our implementation
Read full review
Performance
Kubernetes
No answers on this topic
Progress Software Corporation
It loads quick enough for basically all our systems. Because we have this for local dev environments, speed isn't really a big issue here. Yes, depending on the system, sometimes it does take a relatively long time, but it's not an issue for me. One thing that is annoying is that if I want to make a small change to a cookbook and re-run the Chef client, I can't just make the change in the cache and run it. I have to do the whole process of updating the server.
Read full review
Support Rating
Kubernetes
No answers on this topic
Progress Software Corporation
Support for Chef is easily available for fee or through the open source community as most the issues you will face will have been addressed through the Chef developer community forums. The documentation for Chef is moderate to great and easily readable.
Read full review
Alternatives Considered
Kubernetes
Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.
Read full review
Progress Software Corporation
We considered the three leading competitors in the field: Chef, Puppet and Ansible. Ansible is a very strong competitor and has a nice degree of flexibility in that it does not require a client install. Instead the configuration is delivered by SSH which is very simple. Puppet seems like it has fallen off the pace of the competition and lacked the strong community offered by Chef. We chose Chef because of the strong support by the company and the dynamic and deep community support.
Read full review
Contract Terms and Pricing Model
Kubernetes
No answers on this topic
Progress Software Corporation
The pricing seemed inline with our products in this space. Nothing out of the ordinary in contract, term, or pricing structure
Read full review
Professional Services
Kubernetes
No answers on this topic
Progress Software Corporation
The entire professional services team was great to work with. The curriculum was tailored to our specific use cases. The group we worked with were very responsive, listened to our feedback, was very easy to schedule and accommodate. I cannot say enough good things about our professional services experience
Read full review
Return on Investment
Kubernetes
  • Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
  • Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.
Read full review
Progress Software Corporation
  • Chef is a good tool for baselining servers. It will be a good ROI when there are huge number of servers. For less number of servers maintaining a master will be an over head.
  • One good ROI will be that the Operations Team also gets into agile and DevOps methodologies. Operational teams can start writing scripts/automations to keep their infra more stable and their application stack more reliable.
  • Implementation of Chef eliminates the manual mode of doing things and everyone aligns to automation mind set. It helps in change of culture.
Read full review
ScreenShots