Google Kubernetes Engine vs HPE Ezmeral Container Platform comparison

"The deployment of the cluster is very easy."

"The most beneficial feature is the ability to separate each project and manage permissions more effectively."

"The logs are important for detecting problems in our clusters."

"The solution simplified deployment, making it more automated. Previously, Docker required manual configuration, often done by developers on their computers. However, with Google Kubernetes Engine, automation extends to configuration, deployment, scalability, and viability, primarily originating from Docker rather than Kubernetes. Its most valuable feature is the ease of configuration."

"Google Kubernetes Engine's most valuable feature is container deployment."

"We appreciate that it is quite easy to set up a Kubernetes cluster in Google Cloud, using the managed services within this solution."

"The most valuable aspect of Google Kubernetes Engine (GKE) is its managed nature, which significantly reduces the burden on our platform team."

"The solution is available across AWS, GCP and Azure and is seamless."

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

"The monitoring part requires some serious improvements in Google Kubernetes Engine, as it does not have very good monitoring consoles."

"The product's stability is an area of concern where improvements are required."

"The management UI could be improved."

"I think that security is an important point, and there should be additional features for the evaluation of data in containers that will create a more secure environment for usage in multi-parent models."

"I would rate the scalability a seven out of ten."

"There are some security issues, but it might just be because we are not up to speed yet as much as we should be and so we haven't found it in the documentation yet. That's why I don't want to confuse this. Still, it could be a little bit easier to understand and implement."

"The user interface is a bit confusing sometimes. You need to navigate between the various consoles we have. It's hard to figure out where things are. It's frustrating. The documentation could be a bit better."

"While the GKE cluster is secure, application-level security is an essential aspect that needs to be addressed. The security provided by GKE includes the security of communication between nodes within the cluster and the basic features of Kubernetes security. However, these features may not be sufficient for the security needs of an enterprise. Additional security measures must be added to ensure adequate protection. It has become a common practice to deploy security tools within a Kubernetes cluster. It would be ideal if these tools were included as part of the package, as this is a standard requirement in the industry. Thus, application-level security should be integrated into GKE for improved security measures."

"The modernization in Ezmeral could be improved."

"Pricing is a bit expensive compared to some other products, but it's acceptable."

"Currently, it costs around $1000 per month which sorted our deployment. So once we get more clients, having a huge suffix, costs can go up."

"I would rate the solution's pricing a nine out of ten. The tool costs around 3000 dollars per month. There are no additional costs apart from these."

"The tool's licensing costs are yearly."

"The pricing for GKE is dependent on the type of machine or virtual machine (VM) that is selected for the nodes in the cluster. There is a degree of flexibility in choosing the specifications of the machine, such as the number of CPUs, GPUs, and so on. Google provides a variety of options, allowing the user to create the desired cluster composition. However, the cost can be quite steep when it comes to regional clusters, which are necessary for high availability and failover. This redundancy is crucial for businesses and is required to handle an increase in requests in case of any issues in one region, such as jumping to a different region in case of a failure in the Toronto region. While it may be tempting to choose the cheapest type of machines, this may result in a limited capacity and user numbers, requiring over-provisioning to handle additional requests, such as those for a web application."

"I would rate Kubernetes' pricing four out of five."

"It is competitive, and it is not expensive. It is almost competitive with AWS and the rest of the cloud solutions. We are spending around 3K USD per month. There are four projects that are currently running, and each one is incurring a cost of around 3K USD."

"This is an open source solution, so there is no pricing or licensing."