Google has announced general availability for Cloud Run, the serverless container environment it first debuted in beta back in May.

The GA-ization of Cloud Run covers both the fully-managed service debuted in Spring, and the Cloud Run for Anthos service, which was unveiled in September.

The former is described as “a fully managed serverless execution environment that lets you run stateless HTTP-driven containers, without worrying about the infrastructure”.

Google said it “allows you to write code in any language you choose, using any binary, without having to worry about managing the underlying infrastructure.” Being serverless, “You’re also charged only for the resources used, billed to the nearest 100 milliseconds.”

At the same time, Google said, Cloud Run workloads are “totally portable” and can be run across Google Cloud, or on-prem using its Anthos service “or on a third-party cloud platform that supports Knative.”

Google has made a big play of supporting hybrid cloud, hence, it has also unwrapped Cloud Run for Anthos, its multi-cloud platform, which it says will allow organisations to leverage Kubernetes and their existing resources to “modernize in place.”

More temptingly, perhaps, as Kubernetes is still a bit of a handful, Google claims that with Cloud Run for Anthos, developers can more easily write serverless applications and deploy them “without having to learn Kubernetes concepts first.”

Once organisations are feeling fully confident, Google suggests, “you can redeploy to the fully managed Cloud Run. You can even choose to move your workloads back to your own datacenter or another third-party cloud running a Knative-compatible environment.”

To drive home the open point, Google cited support from a raft of companies in the CI/CD and security spaces, including CircleCI, CloudBees, Datadog, Sumo Logic, and Sysdig. 

Cloud Run is based on Knative, the Google-backed serverless workload management platform. It might be a coincidence that the Cloud Run announcement coincided with an “update” from the Knative steering committee on “governance” for the project.

The committee declared that the Kubernetes project had defined “explicit” community values, and “We will work to construct similar values and vet them across our community.”

Amongst other things, it declared that “no one company should aspire to control outcomes, as that is inherently in conflict with the goal of community stewardship.”

The steering committee will oversee usage and implementation of the Knative trademark, while “Google will provide the Steering Committee with a legal escalation path for enforcement when needed.”

The committee added “the community we have now is ideally a small subset of the community we aspire to see in a year, we will target a one-year transition period to the new governance we define, similar to how the Kubernetes project moved from a bootstrap committee and charter to the new community-driven model.”