Re:Google admits Kubernetes container tech is too complex
by wdenniss on Friday February 26, 2021 @02:23PM
(#26278715)
Hey, it's William from Google here. You're right about the costs, I just wanted to point out that Autopilot does include one cluster in GKE's free tier. So you'll only pay the ~$73/month if you have more than 1 cluster.
There's (almost) no limit to what you can run in one cluster too, and Kubernetes namespaces can help to separate different environments to allow for sharing.
Cloud Run sounds like the perfect solution for your workloads though!
Re:Google admits Kubernetes container tech is too complex
by je42 on Friday February 26, 2021 @05:27AM
(#26273328)
yep, cloud run is pretty good. unfortunately, it doesnt cover all cases. (i.e. stateful stuff like: websockets and chunking, and recurring jobs)
for these case, i still have gke cluster around.
Re:Google admits Kubernetes container tech is too complex
by flakiness on Friday February 26, 2021 @09:01AM
(#26274799)
Nitpick FYI: WebSocket is coming.
https://cloud.google.com/blog/products/serverless/cloud-run-...
(Still agree that Cloud Run isn't for everyone.)
Re:Google admits Kubernetes container tech is too complex
by mping on Friday February 26, 2021 @03:40AM
(#26272632)
I think you mean 70$, not 700$
Re:Google admits Kubernetes container tech is too complex
by jillesvangurp on Friday February 26, 2021 @03:55AM
(#26272719)
Eh yeah, thanks for correcting me.
I like Cloud Run for the same reason because I can use it without needing a lot of devops skills in my team or without sacrificing my own time (because I have those skills but have more valuable things to do). It allows me to focus on keeping my CI/CD pipeline (cloud run sets that up with a button click) busy with new functionality. And our hosting cost are close to 0$ because we stay below the freemium layer until we actually need to scale.
Edit. corrected the typo 700->70