Google Kubernetes Engine

Google Kubernetes Engine

About TrustRadius Scoring
Score 8.6 out of 100
Google Kubernetes Engine

Overview

Recent Reviews

Reviewer Pros & Cons

View all pros & cons

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Google Kubernetes Engine, and make your voice heard!

Pricing

View all pricing

Autopilot Mode - 3 year commitment price (USD)

$0

Cloud
GKE Autopilot Ephemeral Storage Price GB-hr

Autopilot Mode - 1 year commitment price (USD)

$0.0000438

Cloud
GKE Autopilot Ephemeral Storage Price GB-hr

Autopilot Mode - Regular Price

$0.0000548

Cloud
GKE Autopilot Ephemeral Storage Price GB-hr

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://cloud.google.com/kubernetes…

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Starting price (does not include set up fee)

  • $0.04 vCPU-hr Autopilot Mode

Features Scorecard

No scorecards have been submitted for this product yet..

Product Details

What is Google Kubernetes Engine?

Google Kubernetes Engine supplies containerized application management powered by Kubernetes which includes Google Cloud services including load balancing, automatic scaling and upgrade, and other Google Cloud services.

Google Kubernetes Engine Video

A Short Explanation into Google Kubernetes Engine

Google Kubernetes Engine Technical Details

Deployment TypesSaaS
Operating SystemsUnspecified
Mobile ApplicationNo

Comparisons

View all alternatives

Compare with

Frequently Asked Questions

What is Google Kubernetes Engine?

Google Kubernetes Engine supplies containerized application management powered by Kubernetes which includes Google Cloud services including load balancing, automatic scaling and upgrade, and other Google Cloud services.

How much does Google Kubernetes Engine cost?

Google Kubernetes Engine starts at $0.0445.

What is Google Kubernetes Engine's best feature?

Reviewers rate Support Rating highest, with a score of 8.9.

Who uses Google Kubernetes Engine?

The most common users of Google Kubernetes Engine are from Enterprises (1,001+ employees) and the Information Technology & Services industry.

Reviews and Ratings

 (51)

Ratings

Reviews

(1-7 of 7)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
Review Source
The major issue that Google Kubernetes Engine solves for us is that as a managed service, it makes maintenance of the cluster much easier - autoscaling and updating nodes, reliable, and cost-effective.
Using the cluster to keep the microservices for an application up and running - it is intended for workloads that can scale.
  • easy setup for users
  • strong documentation
  • integration with other GCP services
  • errors from liveness probes can be ambiguous to resolve
Google Kubernetes Engine is well suited for dynamic and large workloads since it can scale up with usage. It is easily configurable, which allows for flexibility.
User interface is simple to navigate, which reduces roadblocks for a team with people unfamiliar with Kubernetes.
Great if you are already using other GCP services as it integrates well with that.
  • GCP makes submitting support tickets on the platform easy and provides a form that makes collecting information on any issue convenient
  • having a paid support contract might be helpful as it allows for better detail and attention devoted to a problem specific to your team
  • abundant documentation makes navigating GKE a lot easier
Borislav Traykov | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
Two products I work on are using Google Kubernetes Engine clusters. For the most part, the development efforts mostly go as far as "put service in container," so stuff such as scalability is left to 3rd party components that we use. The Google Kubernetes Engine can use a specific Google-provided ingress controller that is very beneficial when it comes to integrating with other services/products such as Cloud Armor, but it's also vendor-specific, so it has its own quirks and learning curve. Thus, we use the Google Kubernetes Engine just like a regular managed Kubernetes cloud service. The products we have in the Google Kubernetes Engine cluster deal with data piping, collection, and even some machine learning. The major problem that the Google Kubernetes Engine solves for us is a completely managed cloud Kubernetes service - we have an easier time managing our clusters (updates, scaling, and uptime SLA), doing physical and virtual migrations (moving nodes geographically, data in volumes, etc.).
  • Engine upgrade rollout strategy - well documented and configurable
  • Integration with other Google Cloud services like the Compute Engine, SaaS databases, and some cloud networking like Cloud Armor
  • Graphical interface for a lot of operations - either for a quick peek/overview or actual work done by administrators and/or developers (via the Google Cloud Console, for example)
  • It cannot reach true zero scale - they have a competing(?) product for that - Cloud Run Kubernetes clusters. It seems like the Google Kubernetes Engine may not be as flexible as some people need - in terms of costs and infrastructure.
  • Some networking for the Google Kubernetes Engine is way too "hidden" from other similar services from Google Cloud - like network whitelisting (for the control plane), external IPs(s) are not a part of the VPC network overview, data storage.
  • We had to make a hack for node-specific changes (max open file descriptors) because we put Elastic in our Google Kubernetes Engine clusters. These changes were made as hacks because there is still no official API/command approach to have such a form of control over the cluster's infrastructure.
The Google Kubernetes Engine clusters are very good at being a managed cloud K8s platform - lots of documentation, features, and updates are available. It's also newbie-friendly - for both administrators and developers. Unfortunately, currently, it cannot reach true zero scale - thus, costs (rent for the service) are still involved even if you are barely using it.

Thankfully, it's possible to have alternatives in Google Cloud:
  • Your own K8s cluster on Compute Engine VMs - you manage it completely; it will have access to a lot of Google Cloud services.
  • Cloud Run cluster - less documented but more flexible
  • Anthos clusters - you can use this service for a lot of types of K8s clusters - Google Kubernetes Engine, Cloud Run, on-prem, AWS, Azure
Score 9 out of 10
Vetted Review
Verified User
Review Source
We are a B2C PrivacyTech company running multiple GKE clusters in different regions. I am the only DevOps engineer at the company responsible for all GCP-related.
  • Uptime
  • Reliability
  • Easy UI
  • Logging
  • Cost visibility
  • Dull UI
GKE compared to Azure is a lot easier to quickly bootstrap a project for demo purposes. GKE has much better integration with the Kubernetes open-source project and GKE is the first provider to adopt the newest features and it looks like many of the features on the Kubernetes are well suited for GCP purposes.
Score 9 out of 10
Vetted Review
Verified User
Review Source
GKE provides a seamless installation method across a whole organization. It is a fair starting point with Kubernetes technologies. Managed Kubernetes allows deploying application test pipelines for software companies with a reasonable overall price. Moreover, the number of POP helps setup quite reliable installation in a regional way.
  • Deployment method (single, zonal, regional).
  • Lifecycle management (stable, regular, rapid).
  • Integrated GCE services (loadbalancers).
  • Multi-regional deployment (better reliability).
  • GPU node availability.
  • Integrated market place.
At the moment, the best-managed cluster on the market. Quick deployment with quite specific project requirements. The mesh ingress (istio) allowed the building of a quite complicated upgrade process for applications.
Very good Kubernetes distribution with a reasonable total price. Integration with storage and load balancer for ingress and services speed up every process deployment.
Kadu Barral | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
Google has made the setup of Google Kubernetes Engine easy in the Google Cloud, it comes somewhere in the middle of Iaas and Paas, the user interface is very intuitive, and you can manage your cluster directly through the web interface. It is an excellent tool with lesser management overhead with servers or Kubernetes installation, etc. At the same time gives you the flexibility to manage the cluster and related settings. You can scale up with a few clicks or set up automated scaling based on traffic and various parameters.
  • Automated orchestration, deployment, and scaling of containers
  • Integrated Logging
  • Persistent storage configuration and options.
  • Routes and external DNS integration
Google Kubernetes Engine increases productivity and helps teams focus on their core product without worrying about where to run it. If your application is very small and simple, a serverless option could be better.
Google support is excellent and helpful, but the first answer is always so bureaucratic no matter how many logs, evidence, and information you sent.
Score 8 out of 10
Vetted Review
Verified User
Review Source
Google Kubernetes Engine is being used by our I.T. Department as part of its Cloud Infrastructure. At this time we have decided on Google Kubernetes Engine as our primary tool for Kubernetes and are running test/evaluation workloads with it. The idea is to drive down our cloud infrastructure costs by moving resources off general-purpose cloud environments.
  • Simple setup for new users
  • Easy integration with existing Google Cloud environments
  • Cost effective
  • Not as intuitive as it could be
  • Documentation could be better, especially for people using other Google Cloud tools
  • Not the preferred Kubernetes Engine for many apps
Google Kubernetes Engine is a natural addition for users/organizations already using the Google Cloud Platform. For us, it was a simple addition and was up and running within minutes. Our challenge has been that the public documentation for applications that use Kubernetes is aimed at Amazon Web Services, so it requires extra research and work to get running on Google Kubernetes.
Direct application support and documentation for Google Kubernetes is still significantly lacking. Anyone getting an application running on the platform will mostly be on their own. The world is dominated by Amazon. Having a paid support contract with the Google Cloud Platform should help, however, our organization does not have one which complicated things.
Bhargav Nanekalva | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
Google Kubernetes Engine is used for running our product across different environments in the cloud over a dedicated Kuberenetes cluster that has been configured by us. It's being used by the GCP DevOps specialists and developers who write build scripts as part of each of our projects. GKE has solved us the problem of efficiently running production payloads with consistent runtimes, seamless scaling and reliability, application logs and APM using StackDriver.
  • It's super easy to get started - to creating a cluster to deploying your applications to it
  • Dead simple container orchestration and networking which can all be managed by yaml code
  • Support for docker
  • Auto scaling, upgrades and repairs of nodes in the cluster
  • Built-in application monitoring and logging using StackDriver
  • Automatic service discovery and DNS
  • Kubernetes is built and supported by Google
  • There aren't any but there's a steep learning curve for your team especially if they are new to the Kubernetes world
GKE is well suited for production/preprod loads as it's meant for reliably running services with zero downtime and at scale. GKE is not required for anything other than a production load like staging and development. Also if you want to test your deployment, you can use any k8s cluster because what works on a local k8s cluster works on GKE.