HPE Ezmeral Container Platform vs Kubernetes comparison

"The stability of the HPE Ezmeral Container Platform is good, and I rate it an eight out of ten."

"If customers focus on primary apps or if they are using them for data science, this is a good solution."

"The most valuable feature of Kubernetes is the integration with other solutions, such as Formative and Grafana."

"The most valuable features of Kubernetes have been autoscaling and its resilience mechanisms."

"One of the most valuable features is the thickness of the cloud platform or on-prem file, which makes the solution straightforward to shift and scale. It works well with different types of deployment strategies and networks."

"We use this solution for the hosting of micro-services. Kubernetes helps us to orchestrate all the containers hosting these micro-services."

"The most valuable feature of Kubernetes is its support for load balancing."

"Kubernetes provides scalable clustering for containers and other means of deployment."

"The cloud-managed Kubernetes allow us to take care of a big system and deployment and container management without having a big operational team."

"Once you get it configured properly, it's a stable solution."

"HPE Ezmeral Container Platform is not user-friendly and has many parts that are more difficult than Cloudera. It is also a complex solution and has low features for data management."

"The modernization in Ezmeral could be improved."

"Currently, in Kubernetes, all of the health deployments or monitoring, and the discrete tools need to be configured. Changing this would make it much easier. Otherwise, we have to rely on a external tool to implement the monitoring."

"Although we face issues when migrating to new versions of Kubernetes, such as misunderstandings on using new features or integration with proxy services, these issues can be addressed with proper preparation."

"The tool needs to improve its UI. The tool is very complex and basic."

"Kubernetes can be complicated to understand."

"The setup and operation of the product should be simplified."

"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."

"Setup was not straightforward."

"It's good for bigger organizations, but for smaller organizations or a few workloads, it may be too heavy, not easy to deploy, and the ROI may be less because it requires a control plane, worker nodes, and multiple VMs to run."

"Pricing isn't a major concern for us. Since we resell Kubernetes services and focus on providing support, integration, and education, we don't usually have pricing issues. Our customers are more concerned with getting the right support and services than the cost. So, the value we provide is more important than the actual pricing. Pricing might change in the future, but it’s not a big issue for us right now."

"In addition to Kubernetes, you have to pay for support."

"Kubernetes is open-source. Kubernetes is free, but we're charged for AWS utilization."

"You need to pay for a license if you buy branded products. For example, if you take the services from Azure, AWS, or Google, the price of the Kubernetes cluster is inclusive of the service that's being offered to us on a pay-and-use model."

"It's an affordable solution"

"If you're using a public cloud, the cost depends on the number of nodes you are planning to deploy Kubernetes on."

"Kubernetes is open-source."

"The solution is affordable."