Google Kubernetes Engine is used for orchestrating Docker containers. We have 30 or 40 customers working with this solution now. We'll probably see 10 to 15 percent growth in the number of customers using Google Kubernetes Engine in the future.
Head of .NET Department at Evozon
It's a good solution for orchestrating Docker containers depending on your technology stack
Pros and Cons
- "Google Kubernetes Engine is used for orchestrating Docker containers. We have 30 or 40 customers working with this solution now. We'll probably see 10 to 15 percent growth in the number of customers using Google Kubernetes Engine in the future."
- "Google Kubernetes Engine is less stable in some highly complex deployments with many nodes."
What is our primary use case?
For how long have I used the solution?
We've been using Kubernetes Engine for five years.
What do I think about the stability of the solution?
Google Kubernetes Engine is less stable in some highly complex deployments with many nodes. However, those are probably edge cases.
What do I think about the scalability of the solution?
Google Kubernetes Engine is scalable
Buyer's Guide
Google Kubernetes Engine
February 2025
![PeerSpot Buyer's Guide](https://www.peerspot.com/images/peerspot_logo_lt.png)
Learn what your peers think about Google Kubernetes Engine. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
837,501 professionals have used our research since 2012.
How was the initial setup?
The ease of deployment for Google Kubernetes Engine is about average.
What's my experience with pricing, setup cost, and licensing?
Google offers yearly and monthly subscriptions.
Which other solutions did I evaluate?
We don't prefer Google over Amazon or any other Kubernetes solution. It depends on the technology stack that our customers choose based on project needs. It's not better than the others.
What other advice do I have?
I rate Google Kubernetes Engine eight out of 10.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
![PeerSpot user](https://www.peerspot.com/assets/media/images/anonymous_avatar-ddad8308.png)
Director at a tech services company with 11-50 employees
I like the plugin management and configuration sync features
Pros and Cons
- "GKE's plugin management and configuration sync are excellent features. The amount of data it provides is good, and I've been able to integrate it with the things I need."
- "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."
What is our primary use case?
All of our clients are using GKE lightly. The companies are big, but the usage is small.
What is most valuable?
GKE's plugin management and configuration sync are excellent features. The amount of data it provides is good, and I've been able to integrate it with the things I need.
What needs improvement?
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.
For how long have I used the solution?
I have only been using GKE for a couple of months, but I have been working with Kubernetes for about six years and EKS for a year.
What do I think about the scalability of the solution?
GKE is scalable.
Which solution did I use previously and why did I switch?
We were previously using basic Kubernetes that we set up and managed ourselves. I've also used EKS.
How was the initial setup?
Setting up GKE is somewhat complex. There are lots of concepts that are involved and many options to consider. At the same time, you can easily automate it. It's easy to interact with the client and the APIs, and the documentation is good. Sometimes it is confusing, but you can find most of the stuff that you need.
Which other solutions did I evaluate?
I think EKS and AWS are very similar usages. I don't know if one is superior to the other. Google might be better at working with identities for workloads and resource integration. I think it's a bit better and easier than AWS's IM.
What other advice do I have?
I rate Google Kubernetes Engine eight out of 10.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Google Kubernetes Engine
February 2025
![PeerSpot Buyer's Guide](https://www.peerspot.com/images/peerspot_logo_lt.png)
Learn what your peers think about Google Kubernetes Engine. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
837,501 professionals have used our research since 2012.
CTO at a tech services company with 11-50 employees
An user-friendly solution from the leader of Kubernetes service
Pros and Cons
- "The solution is more user-friendly than AWS or Azure. I can also easily scale out the service in the future when the number of customers grows. GKE is the leader of Kubernetes service and it can be easily updated. I love the tool's user interfaces."
- "I use the Firebase tool with GKE and it would be helpful if the solution can give notifications when we reach the budget limit."
What is our primary use case?
I use the tool to host a SaaS application.We also provision the clusters to help students learn how to use Kubernetes.
What is most valuable?
The solution is more user-friendly than AWS or Azure. I can also easily scale out the service in the future when the number of customers grows. GKE is the leader of Kubernetes service and it can be easily updated. I love the tool's user interfaces.
What needs improvement?
I use the Firebase tool with GKE and it would be helpful if the solution can give notifications when we reach the budget limit.
For how long have I used the solution?
I have been working with the solution for more than 8 years.
What do I think about the stability of the solution?
The product is stable.
What do I think about the scalability of the solution?
The tool is scalable and we have around 3000 users for the product.
How are customer service and support?
The tech support's service is good.
How would you rate customer service and support?
Neutral
How was the initial setup?
The solution's setup is very easy.
What was our ROI?
The solution's ROI is good.
What's my experience with pricing, setup cost, and licensing?
The solution's price is reasonable.
What other advice do I have?
I would rate the product a nine out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Solution Architect at a tech consulting company with 501-1,000 employees
Good for microservices and almost zero downtime for deployment
Pros and Cons
- "Stability-wise, this solution is really good."
- "The network configuration has to be simplified."
What is our primary use case?
We primarily use this solution for authorization and service deployment.
What is most valuable?
The CLI commands are good.
What needs improvement?
The network configuration has to be simplified.
I would like to see a more user-friendly interface. Currently, it is a little complex, and the technical guides are not easy to follow. Compared to other applications, the documentation needs a lot of improvement.
Cluster-based software support needs to be improved.
For how long have I used the solution?
Two years.
What do I think about the stability of the solution?
Stability-wise, this solution is really good.
What do I think about the scalability of the solution?
Scalability for this solution depends on the application. For normal microservice-related applications where there is no clustering, it is really evolved and easy to scale. However, for cluster-based applications such as MariaDB, or other cluster-based tools, scalability is complex and it needs to have more documentation.
We are using the solution for managing deployments, so there are only five or six users.
How are customer service and technical support?
We have not subscribed to outside help for this solution. We have been using Google to search the forums for issues that we encounter. There is no defined place where I can refer problems and find answers.
Which solution did I use previously and why did I switch?
We did not use another solution prior to this one.
How was the initial setup?
The initial setup is not straightforward. While it is not too difficult, there are some complexities. For example, sometimes when we add to the network there is an error and something goes wrong, which means that we have to start again, from scratch.
What's my experience with pricing, setup cost, and licensing?
This is an open source solution, so there is no pricing or licensing.
Which other solutions did I evaluate?
I evaluated Docker Swarm, but compared to that, Kubernetes is very good. Docker Swarm is only for small applications.
What other advice do I have?
This is a really good product for independent applications or microservices. The downtime is minimal, and we have even made it zero downtime for deployment. However, when they are cluster-based applications, it is really complex.
I would rate this solution an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
![PeerSpot user](https://www.peerspot.com/assets/media/images/anonymous_avatar-ddad8308.png)
Buyer's Guide
Download our free Google Kubernetes Engine Report and get advice and tips from experienced pros
sharing their opinions.
Updated: February 2025
Product Categories
Container ManagementPopular Comparisons
VMware Tanzu Platform
Red Hat OpenShift Container Platform
Rancher Labs
Kubernetes
Nutanix Kubernetes Engine NKE
Amazon Elastic Container Service
HPE Ezmeral Container Platform
Buyer's Guide
Download our free Google Kubernetes Engine Report and get advice and tips from experienced pros
sharing their opinions.