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 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."
"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 more time we use Komodor the more we save. Currently, we have seen around a ten percent return on investment."
"The product is highly scalable."
"This product has a rich toolset from the community including CNI plug-ins, Helm packages, operators, dashboards, various integrations, etc."
"The auto-repair function in Kubernetes is perfect. When something breaks, the auto-repair function automatically repairs it. If you are running the content in Kubernetes, you have a good set up. You do not need to do anything for the management of this. So, the automation of Kubernetes is number one."
"I like that it has really boosted cloud-native development and stood the test of time. The underlying architecture allows one to scale as per the business KPIs much faster."
"Kubernetes' most valuable features include scalability and deployment."
"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 solution is easy to use."
"There's a lot of community support if you need to get help."
"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."
"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 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."
"Komodor's visibility could be improved."
"The setup process could be improved as it's quite complex, especially for newbies."
"Security could be improved. It would be helpful if there were other security modules built into Kubernetes."
"Kubernetes could improve by having better integration with VMware solutions."
"The dashboard, monitoring, and login need improvements."
"The Kubernetes dashboard can be improved. It is currently a mess. We were using Rancher earlier, and everyone was happy with the dashboard. Right now, we are using Kubernetes, and it's not working with Microsoft workstations. We still have problems with the dashboard. It's terrible."
"Kubernetes could adopt UI-based approach. A UI-based approach would be really useful in the CI/CD pipeline. They should make everything a little bit more user-friendly. For example, when I'm deploying, it would be nice to load my code and be able to see which components need to be connected."
"Setup was not straightforward."
"We would like to see more validation tools added to this solution, this would provide pre-deployment analysis that developers could use before publishing their infrastructure."
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, Google Kubernetes Engine, Nutanix Kubernetes Engine NKE 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.
