Google Cloud CEO Thomas Kurian says that its open source tool for microservices management, Istio, will be donated to a foundation in the near future
Google Cloud CEO Thomas Kurian has ended years of confusion by telling Protocol that Google will eventually donate its open-source project Istio … Tweets: @techjournalist , @chipchilders , @christianposta , @sogrady , and @tomkrazit Tweets: Sean Kerner / @techjournalist : Donated? ha. @IstioMesh should have had open governance under a 3rd party foundation at the 1.0 release..and i've heard Google ppl speaking about it for literally...years. https://twitter.com/... Chip Childers / @chipchilders : This is outstanding news for the @cloudfoundry community, which is increasingly relying on the good work of the @IstioMesh project > https://www.protocol.com/... Christian Posta / @christianposta : I'm welcoming of this news. @IstioMesh has already been an open-governance, multi-org, very successful project. Maybe this helps quiet the noise from the noise makers :) https://twitter.com/... Steve O'Grady / @sogrady : if true, this could bring an end to a large number of behind the scenes and off the record conversations https://www.protocol.com/... Tom Krazit / @tomkrazit : New from me: Google Cloud CEO Thomas Kurian told me this morning, which was a week ago, that Google still intends to donate Istio to an open-source foundation, after angering its partners last year by backing off plans to do so: https://www.protocol.com/...
Context & Ripple Effects
Istio has carried a governance asterisk since its 2017 debut by Google, IBM, and Lyft: the code was open source, but the project stayed under Google's operational control, and critics — including Red Hat's Sean Kerner in the reaction to this story — argued it should have moved to third-party foundation governance at version 1.0.
Kurian's pledge closes that loop by repeating a playbook Google has run before: donating Kubernetes to the newly formed CNCF at 1.0, then handing over Kubernetes' operational control to its community in 2018. Coming after Diane Greene's tenure, when Google Cloud struggled against AWS and Azure, it reads as a trust-building move aimed squarely at enterprise buyers.
First-order effects
- Enterprises running Istio get neutral stewardship of a control-plane component they already depend on, removing the single-vendor risk that kept some from standardizing on it.
- Co-creators IBM and Lyft move from junior partners in a Google-run project to peers in a foundation-governed one.
Second-order effects
- The main objection to adopting Istio on AWS or Azure — that the mesh is a Google-controlled project — weakens, pressuring rival service-mesh offerings to compete on technical merit rather than governance fears.
- Cloud Foundry and other communities that Chip Childers notes increasingly rely on Istio gain a formal seat in its direction rather than depending on Google's goodwill.
Third-order effects
- If the Kubernetes-to-Istio pattern holds, Google's open-source infrastructure projects become de facto industry standards governed by foundations while Google monetizes the hosted layer — a structure competitors must either match with their own donations or argue against.
- Foundation donation becomes the expected maturity milestone for vendor-born infrastructure projects, raising the reputational cost for any cloud provider that keeps control in-house.
The trend: Cloud providers are converting open-source control points into foundation-governed commons to win enterprise trust, keeping their advantage in the managed services built on top.