The ‘Foreseeable Future’ Ends With Knative’s CNCF App – The New Stack


Well, well, well – after all of that, it looks like Project Knative is about to join the Cloud Native Computing Foundation (CNCF).

In 2019, Google caused some controversy when Donna Malayeri, product manager for Google Cloud Run and member of the Knative steering committee at the time, wrote in an update that Google had “decided not to donate Knative to any foundation for the foreseeable future.”

This week, the Knative project opened a draw request to join the CNCF as an incubation project, thus officially ending the so-called “foreseeable future”, with no reason given as to what had changed in the meantime. In a separate blog post, the Knative Steering and Trademark committees wrote that they were “very excited” by the news that Google had “just announced its intention to donate the Knative project. “

The Google blog post on the subject offers a brief history of the project, noting that it was first founded and published by google in 2018, before being “subsequently developed in close partnership with IBM, Red Hat, VMware and SAP”. As for the reasons for the change of mind, once again, it is especially mom who has the word. The only passage that could even apply offers bland platitudes about open source:

“Finding a home at the CNCF secures Knative’s long-term future and encourages continuous and open innovation. This donation recognizes community adoption and investment in Knative, and will encourage multi-vendor innovation, broader education and training, ”writes Google.

Chris DiBona, Google’s director of open source, explained that the reason boiled down to “maturity” in a tweet:

This, of course, is a far cry from what was said about a potential donation when we wrote about Knative’s independent future outside of a foundation in early 2020, when the former board member Jaïce DuMars said in a Ask me anything (AMA) that donating to Knative wouldn’t really offer the project or its users anything beyond what Google could offer.

“There’s a whole bunch of assumptions about what the CNCF does and doesn’t do and I think it’s a little dangerous to make those assumptions because if you assume that by donating you get these things. , this is not true. If we gave this project tomorrow, nothing would change in terms of governance, ”said DuMars at the time. “The CNCF would not make any changes. The only thing that would be different is that they own the copyright to the Knative name. “

It was around this time that Knative actually adopted an elected, officially cut off control of google of the project, which was perhaps the first step towards the independence of the project. Without any specific public word on the reasoning, however, there is only room for speculation.

One of those speculations could be that there had been some pressure on Google from the aforementioned “close partnerships” – IBM, Red Hat, VMware and SAP – which could just as easily branch off the project. With many original Knative players leaving Google for these other organizations, it appears that a distinct possibility that a forked version could be created and submitted separately to the CNCF, leaving Google to play alone with the original Knative.

But again, this is just speculation.

IBM, one of these partner companies, offered its own applause regarding the candidacy, writing that the news was “an important step in the right direction for Knative’s future”, again laying out the basics of what it means to join an independent foundation, summing it up as “a win-win”.

Of course, you might be wondering after all of this – what about Istio?

This week in programming

  • Docker to obtain single sign-on: For you Docker Company users there, it looks like single sign-on (SSO) is coming to Docker. News of this upcoming feature briefly graced our RSS feeds before being pulled from the Docker blog, where someone apparently took the plunge by posting the details. According to that blog post now non-existent, Docker SSO will allow users to authenticate with their organization’s standard identity provider, including “a number of popular SAML IdPs including Google, Okta, Azure Active Directory, etc.” Additionally, if things stay true to what was briefly released, Docker will (at some point) start inviting a few “current Docker Business customers to preview Docker SSO before it’s generally available in January 2022”.
  • JetBrains unveils its competitor VS Code: JetBrains Fleet released, its lightweight code editor, last week and many people see it as the company’s direct competition for Visual Studio Code (VS Code). Fleet, they write, is “a lightweight editor with a twist!” “In that it” starts up as a full-fledged editor that provides syntax highlighting, simple code completion, and everything you would expect from an editor “but is also” a fully functional IDE providing smart completion, refactorings, navigation, debugging, and everything else you’re used to having in an IDE. According to the blog post, Fleet works with multiple languages, is built using a architecture which makes it work well with remote development, and works with JetBrains space, which makes it easy to start a remote server instance from a source repository, which can be customized using a Dockerfile. Fleet also provides collaboration capabilities, allowing multiple developers to work together on a project. Right now, they say the tool is in its ‘early stages’ and is therefore available to those who apply to join the limited Fleet Explorer program.
  • The best news from AWS re: Invent: Ho, my boy! AWS re: Invent took place this week and if you haven’t paid attention to it, you might have a hard time catching up. Fortunately, Amazon posted a blog post briefly summarizing (and cross-referencing) the details of the major AWS re: Invent 2021 announcements. The blog post highlights more than 50 announcements made at the conference, with further links to The official AWS podcast and the totally overwhelming list of all the news at AWS in 2021. Now if you prefer something a little more organized you can always check out The New Battery Newsletter, which offers coverage from the past week, and keep an eye out for the week ahead for more on our pages.
  • How is the migration from eBPF to Windows going? Earlier this year, we wrote about how eBPF was heading towards Windows, as Microsoft announcement then, and now the company provides an update on its progress. The Extended Berkeley Packet Filter (eBPF), writes Microsoft, is “a well-known, but revolutionary technology for providing programmability, scalability and agility” and the company claims to have “reached important noteworthy milestones.” For example, the last few months have seen the creation of the EBPF Foundation, and a opening speech and speak on the subject. More specifically, Microsoft notes the progress it has made on the EBPF Project for Windows, which started out with “relatively few APIs available for eBPF programs, and no support for the de facto standard yet Libbpf API, “and now has many, many more, including” some of the most used APIs and card types, to unlock key application scenarios. “Additionally, Microsoft said it has made sure that all eBPF hooks for Windows, helper functions and Libbpf APIs have been fully documented, next to documentation on how to create a new extension with hooks and aids. Going forward, the company says it wants to allow other existing eBPF applications and projects to run on eBPF for Windows, as well as “to expand the set of eBPF program types and connection points to which they can. be attached, “eBPF for Windows secure enough to be used in production.

The New Stack is a 100% subsidiary of Insight Partners, an investor in the following companies mentioned in this article: Docker.


Comments are closed.