Google Kubernetes Engine Reviews

Our primary use case is to arrange the correct CICD (Continuous Integration / Continous Deployment) conveyor to provide for continuous changes in production.

The improvement is mainly connected to the speed of change implementation. In the case of the automatic convenor, we spent less time due to the automation of the process. Before using this solution, it was a lot of manual tasks and a lot of people participated in the process.

The most valuable feature is the horizontal staging of applications. Other important features include isolation of applications and more effective usage of infrastructure due to less consumption of resources by containers.

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.

We have not seen any signs of instability, and have an optimistic view of the solution.

Scalability is an important feature of this solution, and we are happy with it.

We have approximately one hundred people using the solution. It is mostly developers and quality assurance people who are working on the preparation for CICD.

Once we move to production, next year, our usage will increase.

I think technical support is good enough.

We did not use an integrated solution prior to this. Rather, it was done in a more traditional way. This included virtual machine creation, installation of additional software, and connection to an external CICD conveyor, etc. We are switching because we are interested in more widely using continuous technology.

Our motivation for switching is to simplify creating a CICD process. We have a lot of small changes and after testing, we will be using an automated process for product delivery.

We are currently in a test phase and are estimating the feasibility of moving this to production. Our plan is to finalize testing by the end of this year and move the solution to production at the beginning of next year.

We have two people working the maintenance of this solution, but frankly speaking, it is not enough. We are planning to improve our skills and capacity and expand these resources.

We communicate directly with somebody who is part of OpenShift. They are top guys and have enough experience to help us build our system. It's no problem.

We do not have a local team in Russia, but at some point, that may change and we will use a local integrator. 

We are planning to reach a positive ROI using this solution.

We are planning to use external support, and hire a commercial partner for it. Usually, this is about twenty percent of the solution.

We have been watching what is happening the market, and for some time it has been obvious that Kubernetes has the most followers and most potential. This is why we are starting with Kubernetes from the beginning.

My advice is not to implement this solution unless there is a genuine demand for it from the business side. It can be useful to start from the bottom of the infrastructure and take it to the highest level because it requires changes in the development and business levels to work with this technology.

I think that there is enough documentation available to start to work with this product. The technology provides a very good opportunity to grow and improve.

I would rate this solution a six out of ten.

Mainly, we target SMEs for Kubernetes services. Currently, we have a few customers, and they expect more customized experiences.

The features are typical Kubernetes, but Google One offers a better GUI-based deployment. It's more sophisticated and integrates well with other services, providing a better customer experience.

There is room for improvement in this solution. For example, auto-scaling can be complex. We expect it to be easier to set up and manage, even for our customers.

We started recently. I have around one and a half months of experience with it.

The stability is good. I would rate it a nine out of ten.

It is a scalable solution. I would rate the scalability a nine out of ten.

The customer service and support are good. 

Positive

The initial setup is pretty simple; we can deploy a cluster within a minute. Just choose a region and the required parameters.

One person can handle it unless they're inexperienced.

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

I would rate the pricing an eight out of ten, where one is a low price, and ten is a high price. 

The auto-scaling can be complicated, so they should be prepared for that. It is difficult to hand over the solution to customers because of scaling up and scaling down issues. If Google improves that aspect, it'll be easier to manage.

Overall, I would rate the solution a nine out of ten.

The autoscaling feature is the most important feature in Google Kubernetes Engine. It also supports containerization. The solution is available across AWS, GCP and Azure and is seamless.

It does not require much investment if you move from AWS to GCP or Azure. The entire cloud process remains the same, with only minor changes.

The console for this solution could be improved because it is very limited. In addition, features like a desktop for the Docker image, drag and drop into a node could be added.

In terms of visualization, the solution could also provide some integration with other tools. We have heard about Grafana and AppDynamics offering these features, but they still require better tools. Google is going in the right direction because they believe in open source integration and give opportunities to other players to work with them. However, they should provide packages where they integrate more features to demonstrate more encouragement in the marketplace.

Training, tutorials, tooling, samples, and more case studies should be included in the next release.

We used this solution for one year.

The solution is stable, and I think even more stability will occur over time. Google Kubernetes Engine is moving in the right direction, especially when you consider concepts of Docker image, pods, nodes, clusters, control planes, data planes, gateway, and the ingress. Many projects run in production on Google Kubernetes Engine, and companies partner with AWS, GCP, and Azure to provide training and assist in completing modules regarding portals.

Google Kubernetes Engine is a scalable solution.

The setup was confusing. We were able to install it locally, but it was slow.

Because I worked in production, I did not use technical support directly. It was required but most likely very minimal.

I do not know specific details about the price, but I believe Google Kubernetes Engine is cheaper than Pivotal Cloud Foundry.

We compared Google Kubernetes Engine with Pivotal Cloud Foundry and found that Google was better.

I rate this solution seven out of ten. I believe Google Kubernetes Engine is the best solution in the market.

Google Kubernetes Engine's most valuable features are microservices and its acquisition rate, which is very useful for scaling perspective.

The user interface could be improved. In the next release, I'd like to see better notifications.

I've been using Google Kubernetes Engine for a few years. 

Kubernetes is stable because it has scalable architecture, so if any part goes down, it starts from the other parts. 

Kubernetes is scalable.

The initial setup was simple.

I would rate Kubernetes' pricing four out of five.

I also evaluated VMware, which is more expensive than Kubernetes.

I would give Kubernetes a rating of eight out of ten.

This is Prophaze deployed in Kubernetes. So we have a Kubernetes. For example, Uber, they have all their sectors deployed in Kubernetes. There should be a native production for Kubernetes. We can have a separate cloud security solution for Kubernetes. Your solution has to be in Kubernetes. Because it should be a Kubernetes solution. So the WAF, in general, can be deployed in Kubernetes as a network solution.

It's like instantaneous scaling up. If you have a lot of traffic coming in, things like RAM and hard disk are easily able to scale.

It should support the latest GP use. I also think it should support load balancing.

I have worked with Google Kubernetes Engine for about three years. We are using version 10.

It's pretty much stable. I would say 99.9%, excellent.

Google Kubernetes Engine is very scalable, in fact, that is one of the best features.

For Google and Amazon, the Kubernetes is along the line of normal support. You email them or you can call them, but email is the preferable way of contacting them.

I heard about the normal service. Some of the eCommerce stuff, size or any of the other sites, you have a lot of traffic coming to your size. It is easy to buy if you have little traffic. You'll be able to buy and resell or if you still have money you can buy you two together. So, if you look at the last five years, people started to think about the cloud. You buy a cloud instance, you customize your configuration. People are now starting to look at Docker and Kubernetes.

The initial setup of Kubernetes Engine is quite straightforward. With just a few clicks, you can have it up and running.

We do everything from scratch here in our company. We have complete control over our selection. We use three people for maintenance.

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. 

My advice to anybody considering this solution is to understand that you need to have everything ready before implementation. You need to have a migration strategy.

I would rate Google Kubernetes Engine an eight out of ten.

We use this solution to run the AI models that we have developed for anomaly detection, cloud workload prediction, as well as setting up clusters.

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

We would like to see some improvement in the ease of integration with this solution.

We would also like to see the addition of some automated realization of data pipelines.

We have been using this solution for nearly three years.

We have found the stability of this solution to be good during our time working with it.

This is an easily scalable solution.

The setup for this solution is reasonably simple.

We implemented this solution using our team of in-house, GCP-certified architects and operators.

We would rate this solution an eight out of ten.

We use the product to host a loyalty application.

The product has valuable security features. It can connect with multiple DevOps tools. It offers vouchers during service upgrades.

The product’s visible allocation feature needs improvement.

We have been using Google Kubernetes Engine for one year.

The product is overall stable.

The technical support services need improvement in terms of response time.

We use AWS EBS.

It is easy to install.

It is a nice tool. I recommend it to others and rate it a nine out of ten.

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

An area in which Google Kubernetes Engine could improve is configuration.

I've been working with Google Kubernetes Engine for a few months.

Google Kubernetes Engine is stable.

Generally, Google Kubernetes Engine is easy to scale, but it can be difficult in some cases.

The initial setup is generally straightforward but can become a bit difficult with more complex projects.

The price for Google Kubernetes Engine could be lower - I'd rate its pricing at three out of five.

I'd rate Google Kubernetes Engine as eight out of ten.