"Google opens up the management of Kubernetes testing and releases with the community" (or something).
Fwiw, I like HN, precisely because the community rewards healthy dialogue. My good comments are upvoted and the shitty ones are down voted. I worry about whether or not my comments are getting upvoted by lots of Googlers, but I sort of trust the HN moderators to have built in defenses against that in the voting ring detector. I also don't go asking anyone to upvote my comments or submissions, and I actively remind people of the same.
Besides that, 2 people does not an army make...
I don't have the negative impression you have obviously gotten from previous instances where this occurred, however. Perhaps it was less than honorable in those other instances.
This kind of missing functionality makes Google Cloud dead on arrival for anyone needing low latency connectivity to customers on T-Mobile, Verizon and any other cellular network that only provides direct connectivity via IPv6. Natted IPv4 gets much shorter state table entries, and worse yet you get a latency penalty as legacy IPv4 traffic gets encapsulated in IPv6 on most LTE networks.
I think the headline confuses the issue. The community wanted more input and ability to control the release and testing process for Kubernetes. It was a fair question to say "Why can only Google cut a release?". We're still happy to fund it, but to make Kubernetes more fully owned by the community and not Google, this was an important step.
Edit: Fwiw, I think William's blog post (https://cloud.google.com/blog/products/gcp/google-cloud-gran...) is more informative, since the TechCrunch article just quotes from it.