We performed a comparison between Komodor and Kubernetes based on real PeerSpot user reviews.
Find out in this report how the two Container Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The service overview is definitely the most valuable feature. With it, I can see all the services and see if they're healthy or not without having to go specifically into each workflow individually. It has been immensely helpful for us whenever we've had network issues or other such issues. We've been able to use Komodor and see at a glance where there might be potential issues."
"The more time we use Komodor the more we save. Currently, we have seen around a ten percent return on investment."
"Komodor's multi-cluster centralized event timeline is the most valuable feature."
"The most valuable aspect is the speed with which I can narrow down what's going on. Usually, I look at the overview of events and then the timeline of an event and the status of the logs to quickly check what's happening or what has happened."
"The event timeline has been super helpful, enabling us to overlay node events in the same timeline as deployment events... That helps an engineer very quickly troubleshoot without having to do too much digging."
"The most valuable aspect of the solution is the scalability."
"The most valuable feature is the Zero Touch Operations, which involves a new way of performing operations and support. We do not have to do maintenance, the operations are very simple."
"The most valuable feature is that it's a container orchestrator. It has a huge user base and it is easily incorporated into all of the public clouds."
"With the use of our blueprint, my experience with the initial setup has been a ten out of ten where one is difficult and ten is easy."
"The self-serving feature allows our developers to grab a container and complete testing."
"The most valuable features of Kubernetes have been autoscaling and its resilience mechanisms."
"The implementation, and the way that they can, with a few clicks, load hundreds of machines without any trouble is very useful."
"The autoscaling feature is the most valuable. Kubernetes itself is an orchestration tool. It automatically detects the load, and it automatically spins up the new Pod in the form of a new microservice deployment."
"One thing we don't have visibility into, which I would love to have, is metrics, such as user logins and usage. It's really hard to know what people are doing when I don't have any metrics on that directly."
"I like the alerts that Komodor provides, but I think the alert interface could be improved."
"I would like to see improvements in how the product is installed. We've already communicated these things directly to Komodor. One feature we would like to see is for Komodor to be highly available on the clusters. Currently, it's only able to run in one instance within the cluster."
"Komodor's visibility could be improved."
"I hope that the cost analytics and resource usage allocation areas will see further development. For example, where we can now see if the pods are over- or under-provisioned, I wouldn't mind higher-level development."
"It would be useful to have a basic and stable interface for monitoring and quick deployment purposes, especially when the deployments are big like a proof of concept or proof of technology. Currently, you need to use the Kubernetes console for all functionalities. It is not a quick-to-learn product if you are not from a Linux background. You need to be very skilled at Linux to learn it quickly. It took me two to three months because I mostly work with Microsoft products. For people who are not from a Linux background, the learning curve is a little bit longer."
"The tool needs to improve its UI. The tool is very complex and basic."
"It would be helpful if the UI were more graphical."
"The setup and operation of the product should be simplified."
"The configuration is a bit complicated."
"One feature I would actually like to see is the network monitoring part. When we talk about communities, it's mostly the computer side. But it does have some enhancements on the networking side which they have recently released. I would like to see more enhancement where we can monitor the networks of the Kubernetes cluster or the Kubernetes workloads."
"I'm a beginner, and I recently started working with Kubernetes. As of now, I don't see any bugs. However, it would be better if it could be deployed without coding."
"Kubernetes can improve by providing a service offering catalog that can be readily populated in Kubernetes."
Komodor is ranked 12th in Container Management with 5 reviews while Kubernetes is ranked 4th in Container Management with 67 reviews. Komodor is rated 8.8, while Kubernetes is rated 8.6. The top reviewer of Komodor writes "Provides extensive visibility into our nodes and has been incredibly useful in freeing up our DevOps staff for other projects". On the other hand, the top reviewer of Kubernetes writes "Container orchestrator that deploys our machine learning solutions". Komodor is most compared with Portainer and Amazon EKS, whereas Kubernetes is most compared with VMware Tanzu Mission Control, Amazon EKS, Nutanix Kubernetes Engine NKE, Google Kubernetes Engine and OpenShift Container Platform. See our Komodor vs. Kubernetes report.
See our list of best Container Management vendors.
We monitor all Container Management 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.
