Google Kubernetes Engine (GKE) Reviews & Product Details

I have been using GKE to manage multiple Kubernetes environments, including QA and production, and overall it has made managing our microservices much easier. What I like most is the Google Cloud Console UI. It gives a clear view of clusters, node pools, workloads, deployments, and resource utilization, making day-to-day monitoring and troubleshooting much more convenient.

Features like autoscaling, rolling deployments, workload identity, Cloud Logging, and integration with other GCP services are particularly useful. Being able to investigate pod issues, check logs, scale workloads, and manage node pools from one place saves a good amount of time.

I also like the flexibility of choosing different machine types and configuring node pools based on workload requirements. This helps us manage resources across different environments without having to maintain everything manually.

One unexpected benefit is how easily GKE fits into our existing GCP infrastructure, especially with Cloud Load Balancing, BackendConfigs, and Cloud Armor.

That said, it's not perfect. Spot instances are one area where I have had a mixed experience. Unexpected interruptions can affect workloads, and managing these interruptions requires additional planning. Some node pool and cluster operations could also be more straightforward.

Overall, GKE is a strong platform with a great UI and useful integrations. It has definitely simplified Kubernetes operations for us, but reliability around Spot instances and some aspects of cluster management still need improvement. Review collected by and hosted on G2.com.

My biggest frustration with GKE is the handling of Spot instances. While they are useful for reducing infrastructure costs, unexpected interruptions can cause workload disruptions and require extra effort to manage properly. Autoscaling and node pool behaviour can also sometimes be unpredictable, especially when workloads have specific resource requirements.

Another thing is that some operations, particularly around node pool upgrades, cluster maintenance, and troubleshooting networking issues, can be more complicated than they should be. Costs can also add up quickly when running multiple environments.

The overall UI is great, but I feel there is still room to make cluster and infrastructure management simpler and more predictable. Nothing is a major dealbreaker, but these things can be frustrating in day-to-day operations. Review collected by and hosted on G2.com.

What I like most about Google Kubernetes Engine (GKE) is the intuitive Cloud Console UI/UX, along with its deep integrations with Google Cloud IAM, Cloud Build, and Terraform. Getting a cluster up and running feels seamless, thanks to comprehensive documentation and dependable support channels that help me see operational ROI quickly. Autopilot mode delivers robust compute performance, and the native AI/intelligence capabilities—such as optimized TPU/GPU workload orchestration for LLMs—contribute to world-class infrastructure reliability. Review collected by and hosted on G2.com.

While the Cloud Console UI/UX is clean and easy to navigate, configuring more complex setups—such as multi-cluster ingress and private network integrations—can still come with a learning curve during initial onboarding. Also, when you’re running high-performance AI workloads across large, multi-tenant cluster deployments, tracking resource consumption takes careful governance to keep cloud pricing and ROI fully transparent. Review collected by and hosted on G2.com.

It allows me to manage many applications that are in containers. Being able to use kubernetes is a plus as a Software Engineer. There are many things that I can do with cluster. Whether it's deploying work loads or increasing/decreasing resources. I think google kubernetes engine has many good features when working with Google Cloud Platform. You are able to modify your cluster to fit your needs. Review collected by and hosted on G2.com.

Learning how to set up clusters can be a bit hard. If you know how to use kubernetes then it's pretty easy to navigate around. There are some things you have to be careful about when using this product. Such as knowing how much your going to spend. I think it could have better tools to help understand what your spending money on. Review collected by and hosted on G2.com.

I like that GKE lets me focus more on the application instead of managing the underlying infrastructure. It handles workloads without me having to manually provision servers, and the deployment process is quite smooth. If a pod crashes, Kubernetes can bring it back up, and I can check pod status, restart failed workloads, or roll back a deployment when something goes wrong. I find rolling updates useful because I can release a new application version without taking the entire service down, and autoscaling helps when traffic increases. The built-in monitoring tools, Cloud Logging, and Cloud Monitoring make it easier to check logs, track errors, look at graphs, and investigate issues without switching between too many tools. GKE fits well with the other Google Cloud services we use and makes managing our application deployments easier. Creating a cluster through the Google Cloud Console was pretty simple, and once everything was configured, things became much smoother. Review collected by and hosted on G2.com.

I find networking and pod connectivity issues hard to troubleshoot, and finding the cause of failures from configuration issues can take time. Managing IAM permissions and service accounts gets confusing when multiple Google Cloud services or projects are involved. Setting up networking and the full deployment pipeline also takes hands-on work, with errors to fix one by one. GKE can feel costly when clusters and supporting resources run continuously, even when the workload is low. I’d like simpler troubleshooting tools and better visibility into which resources are driving costs. Review collected by and hosted on G2.com.

What I like about GKE is that it takes away a lot of the effort involved in managing Kubernetes infrastructure. Setting up clusters and deploying containerised applications is fairly straightforward, especially if you're already working with GCP.

I also like how well it integrates with other Google Cloud services, particularly IAM, Cloud Logging and Monitoring. Features like autoscaling and managed upgrades are quite handy, as you don't have to worry about managing everything manually. Overall, it's a good option for running containerised workloads without having to maintain the entire infrastructure yourself. Review collected by and hosted on G2.com.

One thing I find a bit frustrating is that GKE can get quite complicated when it comes to networking, permissions and cluster configuration. Even though it's a managed service, there's still quite a lot you need to understand about Kubernetes to troubleshoot issues properly.

Cost management is another area that could be improved. It's not always easy to understand how much a particular workload is costing, especially when you have multiple clusters and different node configurations. I also feel that some of the settings in the GCP console could be made simpler. Review collected by and hosted on G2.com.

I’m an MLOps Engineer, and GKE helps me automate the deployment, scaling, and orchestration of my MLOps pipeline. It also helps automate the provisioning of Google Cloud TPUs through the Cluster Autoscaler, including downscaling to zero when training finishes. Review collected by and hosted on G2.com.

Nothing as of Now. It is going in good direction. Review collected by and hosted on G2.com.

GKE provides fully managed nodes with built in hardening and best practice configs automatically applied. Review collected by and hosted on G2.com.

Bit expensive especially for smaller workloads and more complex for beginners. Vendor lock-in. In-consistent documentation. Review collected by and hosted on G2.com.

I like that GKE makes it easy to deploy and manage containerized applications. It handles much of the Kubernetes infrastructure and offers features like autoscaling, monitoring, and automatic updates. This helps reduce manual work and makes applications easier to maintain and scale. Review collected by and hosted on G2.com.

Nothing actually, it is working smooth with no issues. Review collected by and hosted on G2.com.

I like Google Kubernetes Engine (GKE) for its ability to reduce operational work despite the complexity involved in handling Kubernetes concepts. GKE helps with essential features like auto scaling, which is particularly powerful for my production requirements, making it a necessary tool. Also, while setting it up might seem a bit hard without some basic Kubernetes and cloud understanding, the basic initial setup process is pretty straightforward once you get started. Review collected by and hosted on G2.com.

I find the complexity of Kubernetes challenging. Even though Google Kubernetes Engine manages the infrastructure, it doesn't eliminate the Kubernetes learning curve. Auto scaling can unexpectedly increase costs, and idle clusters still cost money. Managing roles, services, account permissions, and securing clusters is difficult. The developer experience feels heavy with too many YAML configurations. Cost transparency is lacking, making it hard to predict billing. Network policies are hard to configure and log tracing is difficult. There are also issues with update stability, API deprecations, and version compatibility. Better built-in distributed tracing and simpler error insights would be helpful. Review collected by and hosted on G2.com.

GKE simplifies Kubernetes management through automated scaling, self-healing, high availability, and seamless integration with Google Cloud, significantly reducing operational effort.It provides automatic scaling, self-healing, seamless upgrades, strong integration with Google Cloud services, and high availability out of the box. Review collected by and hosted on G2.com.

The main drawbacks are the Kubernetes learning curve, occasional complexity in troubleshooting, and cost management challenges as environments scale. Review collected by and hosted on G2.com.