Google Kubernetes Engine
Shares rank 2 of 4 managed Kubernetes services by recommenders
People recommend it as a managed Kubernetes service that is intuitive and reliable. The most common caveat is that bad nodes often need manual fixes and support tickets.
People recommend it as a managed Kubernetes service that is intuitive and reliable. The most common caveat is that bad nodes often need manual fixes and support tickets.
10 people gave an opinion
- recommend it
- 6
- criticize it
- 4
- approval share
- 60%
Recommended in 5 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 6 people recommend itNeeds 10 or more, not met.
- 1.5 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 5 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Managed Kubernetes praised as second to none
“their managed Kubernetes is second to none”
Comment from 29 Oct 2026 in “Gemini 4 Carbon” Easy and intuitive to use
“With GKE/EKS this is even easier.”
Comment from 27 Mar 2026 in “We Rewrote JSONata with AI in a Day, Saved $500K/Year” “I found it rather intuitive.”
Comment from 23 Apr 2026 in “I Am Building a Cloud”
Other managed Kubernetes services people recommend
The three most recommended other managed Kubernetes services, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Amazon EKS | 28 | 13 | 68% | 9 | — | Approved |
| Google Kubernetes EngineThis page | 6 | 4 | 60% | 5 | — | — |
| Google Kubernetes Engine | 6 | 0 | 100% | 5 | — | — |
| DigitalOcean Kubernetes | 6 | 0 | 100% | 3 | — | — |
What people said
8 of the 10 comments that mention it, newest first. Each links to the original comment.
“their managed Kubernetes is second to none”
“We had 110 pods per GKE (kubernetes on gcp) 4 CPU node because that was a network imposed pod limit at the time.”
“Nearly every failure required an engineer to manually intervene to get rid of the bad node, and then file a ticket with GCP support”
“Great idea, rebuild a whole fleet of VMs instead of adding the MTU configuration to your wg-down script”
“I found it rather intuitive.”
“With GKE/EKS this is even easier.”
“Im a third of the running costs”
“GKE's default behavior is to ingest 100% of this into Cloud Logging with no rate limiting.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.