47 engineers on Hacker News describe using Google Kubernetes Engine first-hand: 19 endorse it, 8 regret it, 2 are mixed.
“Even when you get an XID, by default GKE only responds to one or a few of them.”
regret · production · 2 yr · claytonjy · 2026-07-23 · source ↗ · wrong label?“Even when I got tired of waiting for GKE to spin up a node”
regret · personal · mrj · 2024-03-04 · source ↗ · wrong label?“GKE patched the Spectre/Meltdown vulnerable for me weeks before the public announcement.”
endorse · production · theptip · 2023-02-22 · source ↗ · wrong label?“not all Kubernetes are created equal (think GKE node label, EKS custom AMI to get Linux kernels but not other places)”
regret · production · jlandgraf · 2022-12-08 · source ↗ · wrong label?“Of course using managed/hosted K8s makes a big difference.”
endorse · production · anchochilis · 2022-08-12 · source ↗ · wrong label?“the API calls from the GKE applications are perceptively slower than that of the shared AWS t2.medium instance based deployment.”
regret · production · pritambarhate · 2022-06-27 · source ↗ · wrong label?“it is a chore compared to GKE.”
endorse · production · jrockway · 2021-07-27 · source ↗ · wrong label?“we moved to google cloud specifically for GKE and it's been pretty great.”
endorse · production · jordanthoms · 2021-03-01 · source ↗ · wrong label?“I've been using GKE in prod for ~4 years, and have never needed beta features.”
endorse · production · 4 yr · theptip · 2021-01-18 · source ↗ · wrong label?“we have had very few issues in over three years of running production workloads on GKE.”
endorse · production · 3 yr · markbnj · 2020-11-29 · source ↗ · wrong label?“Taking my first GKE project (done essentially as two man team in the side, and then maintained at quite low level of work most the time)”
endorse · production · p_l · 2020-11-23 · source ↗ · wrong label?“we migrated to Google Kubernetes Engine which has been great.”
endorse · production · jordanthoms · 2020-05-15 · source ↗ · wrong label?“I am really disappointed by this. One of the reasons we moved to GCP from AWS was the ability to create multiple clusters at no extra charge.”
regret · production · MightySCollins · 2020-03-04 · source ↗ · wrong label?“GKE is significantly easier to manage.”
endorse · production · 2 yr · atombender · 2020-03-04 · source ↗ · wrong label?“In almost four years of running production workloads on Google's GKE we've had... Notably none of these issues have ever left any of our clusters or workloads inoperable.”
endorse · production · 4 yr · markbnj · 2020-01-13 · source ↗ · wrong label?“GKE is much better than EKS or AKS, IMO; BigQuery is awesome.”
endorse · production · 6 yr · devy · 2019-12-17 · source ↗ · wrong label?“The advantage of GCP/GKE is that we're using preemptable instances; ridiculously easy to set up on GKE”
endorse · production · 013a · 2019-09-20 · source ↗ · wrong label?“we run several Kubernetes clusters via GKE on Google Cloud Platform”
endorse · production · atombender · 2019-08-23 · source ↗ · wrong label?“We switched to GKE last year and haven't had a single problem with infra since.”
endorse · production · mpmpmpmp · 2019-07-28 · source ↗ · wrong label?“We've been running in production on GKE for a little over two years and it's been a solid platform since day one.”
endorse · production · 2 yr · markbnj · 2019-04-05 · source ↗ · wrong label?“My team is running a couple thousand cores on GKE and have been in production there for a year.”
mixed · production · 1 yr · halbritt · 2018-11-17 · source ↗ · wrong label?“I've yet to encounter a single, Docker related bug on Google managed GKE on Container-Optimized OS since we've switched all of our services there a year ago.”
endorse · production · 1 yr · endymi0n · 2018-05-14 · source ↗ · wrong label?“when we were experimenting with auto-scaling node-pools on GKE, and the cluster would scale a node-pool up then fail to scale it back down”
regret · production · markbnj · 2018-05-12 · source ↗ · wrong label?“two gke managed, which .. is limiting, three with our own bootstrap”
regret · production · sleepybrett · 2018-05-08 · source ↗ · wrong label?“We ditched managed kubernetes on GCP and rolled our own using kops on AWS. Things are more stable.”
regret · production · eknkc · 2017-11-29 · source ↗ · wrong label?“Been using GKE for over a year now. No issues at all.”
endorse · production · 1 yr · maktouch · 2017-11-29 · source ↗ · wrong label?“Currently we're running five or six of our core production apps on the GKE version of the platform and the experience has been very positive.”
endorse · production · markbnj · 2017-10-29 · source ↗ · wrong label?“unless you use the cozy Google Cloud Container which I did but isn't cheap ($100/month before bandwidth for 2 containers)”
mixed · personal · hackerboos · 2016-11-22 · source ↗ · wrong label?“on production, GKE handles it nicely too w/ the Logging system.”
endorse · production · eggie5 · 2016-11-11 · source ↗ · wrong label?“I've been consulting on EKS/GKE cost optimization for a few mid-sized companies and kept seeing the same pattern”
neutral · production · rvz · 2025-12-13 · source ↗ · wrong label?“I've been consulting on EKS/GKE cost optimization for a few mid-sized companies and kept seeing the same pattern”
neutral · production · wozzio · 2025-12-13 · source ↗ · wrong label?“Our internal application logs were already being scooped up by GCP because we run our services in GKE”
neutral · production · bhyolken · 2023-11-17 · source ↗ · wrong label?“it handles all of our CI, which runs on a separate GKE node pool.”
neutral · production · tapoxi · 2022-12-21 · source ↗ · wrong label?“We run VMs, we use CloudSQL, we use GKE.”
neutral · production · busterarm · 2022-09-24 · source ↗ · wrong label?“we run notebooks on the Kubernetes clusters (AWS' EKS, GCP's GKE, Azure's AKS, or DigitalOcean) of the users”
neutral · production · Jugurtha · 2021-12-16 · source ↗ · wrong label?“it took our org a solid year of work from 3 dedicated engineering teams to be comfortably deploying on GKE & EKS.”
neutral · production · busterarm · 2021-11-17 · source ↗ · wrong label?“We migrated from Appengine Standard to GKE.”
neutral · production · alooPotato · 2021-09-29 · source ↗ · wrong label?“Our servers are just low-tier GKE nodes, and we run around 3k/visitors at any given time”
neutral · production · fbrchps · 2021-09-07 · source ↗ · wrong label?“when we migrated the last stuff to GKE and our spending dropped to nothing instantly”
neutral · production · jordanthoms · 2021-04-12 · source ↗ · wrong label?“We run two independent compute clusters on different managed infrastructure products (GKE and GAE)”
neutral · production · tompic823 · 2020-10-08 · source ↗ · wrong label?“The key-value service itself is Go and we run it on GKE alongside some of our other services.”
neutral · production · kochman · 2020-09-14 · source ↗ · wrong label?“because almost all of our needs are GKE/VMs”
neutral · production · manigandham · 2018-11-14 · source ↗ · wrong label?“we transitioned out of AWS ... to GKE in Google Cloud where we migrated to a helm chart and custom orchestration tooling on top of that.”
neutral · production · halbritt · 2018-10-02 · source ↗ · wrong label?“on GKE you have to modify your nodepool's access scopes to give the whole node read-write access to all your buckets.”
neutral · personal · lobster_johnson · 2017-12-18 · source ↗ · wrong label?“We run on GCP/GKE and aren't moving”
neutral · production · manigandham · 2017-11-30 · source ↗ · wrong label?“spin up thousands of nodes in the middle of the night for (for a grand total of $40/hr on GKE...)”
neutral · production · slap_shot · 2017-09-06 · source ↗ · wrong label?