Run 5000 VMs more or less continuously. Spin up/down hundreds of kube clusters every day - on every GitHub Pull Request. Serve 9-digits worth of container images per month. To name a few.
> We’re funding this move with a $9 million grant of GCP credits to the CNCF, split over three years, to cover infrastructure costs. In addition to the world-wide network and storage capacity required to serve all those container downloads, a large part of this grant will be dedicated to funding scalability testing, which regularly runs 150,000 containers across 5,000 virtual machines.
> Between the testing infrastructure and hosting container downloads, the Kubernetes project regularly runs over 150,000 containers on 5,000 virtual machines, so the cost of running these systems quickly adds up. The Kubernetes container registry served almost 130 million downloads since the launch of the project.
It sounds like the k8s project has behaved as if it has infinite cloud resources at its disposal, and as such has made no effort to conserve usage.
If this really is a matter of giving the community a mountain of credits, they could probably make it last a whole lot longer with a quick housekeeping pass.
This is explicitly part of the process of transferring each property. We need to be able to produce reports on spend in each area, and those reports are property of CNCF, not Google.
All I'm suggesting is that there are probably low-hanging fruit to make the credits last longer, if up until now the community has been behaving as if resources are free and unlimited.
How does one spend $9 million in Cloud computing by just running CI operations and Unit Testing in 3 years????
$9 million/3 years for Dev Ops Infrastructure for just one specific product sounds out of this world to me.