> Why did Google create Kubernetes and open source it?
I think it's misleading to conflate questions whether Google's k8s engineers can use shortcuts through the organizational fabric around k8s with the project's source licensing.
k8s being open source merely means that the code is open and for everybody to use under clear and rather generous (even if potentially reciprocal) terms that are OSD compatible.
In particular "open source" doesn't mean that everybody gets to have a say on anything or everything: those with commit rights always reign supreme.
As for the part about procedural rules and their (ab)use like the ability to take shortcuts because everybody outside the cabal happens to be absent for whatever reason: that could have happened just as well in any body under pay-to-play rules that covers "software standards" (or anything, really), eg. OSF, X/OPEN, UEFI Forum, ...
You don't don't get to hear about the drama.
I think it's misleading to conflate questions whether Google's k8s engineers can use shortcuts through the organizational fabric around k8s with the project's source licensing.
k8s being open source merely means that the code is open and for everybody to use under clear and rather generous (even if potentially reciprocal) terms that are OSD compatible.
In particular "open source" doesn't mean that everybody gets to have a say on anything or everything: those with commit rights always reign supreme.
As for the part about procedural rules and their (ab)use like the ability to take shortcuts because everybody outside the cabal happens to be absent for whatever reason: that could have happened just as well in any body under pay-to-play rules that covers "software standards" (or anything, really), eg. OSF, X/OPEN, UEFI Forum, ... You don't don't get to hear about the drama.