| Thank you for the detailed response. > In addition to the raw compute costs for those nodes, there's the SRE overhead for managing, upgrading, and securing them. By that logic, can we expect to see charges for GCP Projects and the GCP Console? Cloud IAM? > people have created many zero-node clusters I'd be really curious what is driving folks to do that. Are they using the backplane for CRDs and custom controllers and no compute? This feels like it could be addressed similar to alpha clusters, or with a quota, e.g.: clusters with 0 nodes for > 24 hours will be terminated? Separately, It seems like handing everyone 3 months to figure out what to do about a new $73 * X fee isn't the best plan. Including some kind of estimate in the emails that were sent out would have been helpful. There was a change in pricing for StackDriver a while back that did this. It was very helpful to understand how we would be impacted. > Furthermore, each billing account gets one zonal cluster with no management fee. My feedback is that you would probably get getting way less blowback if that free-tier didn't come across as inadequate. I can appreciate that there are use-cases where it makes sense for you all to be charging. But one zonal cluster... It makes the whole thing feel punitive. > I'm not sure what you mean by that verb. I have a feeling we're all about to go on a journey of discovery together. |
I was one of those people. I got an email from Google this morning and thought "that's weird. I didn't even know I was running a Kubernetes cluster." I think I created it years ago to work through a Kubernetes tutorial and, since it was free, never bothered to delete it.
So, I can imagine this being a problem. Though it seems like having a minimum hourly charge per cluster would have been a better way to handle this (i.e. if your cluster is using less than $0.10/hr in resources, you get charged the difference).