Cloud Native Computing Foundation KnativeCon EU 2022, 2 Jun 2022

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Keynote: Knative and the Open Cloud: Why move Knative to the CNCF?- Aizmahal Nurmamat kyzy, Google

Description

Keynote: Knative and the Open Cloud: Why move Knative to the CNCF?- Aizmahal Nurmamat kyzy, Google

Google’s open cloud relies on open source, and we have long believed in the vision of Knative making it easy to run containers for serving. In this talk, we will cover why we believe that a long-term home in the CNCF is the right thing for developers and for Google’s open cloud.

A

Thank you, carlos. um Let me figure out how to work with this anyway, hello, everyone, my name, is aija mal and I work at google. I am very excited to be here at the first k-native con and I started working on the project somewhat recently, mainly helping with the transition of the k-native project from google to cncf and through this work I met a lot of wonderful people made a few great friends and I'm meeting a few of them here for the first time in person. So that's really exciting and again.

A

This is really special day, because um I get to be part of k-native corner. I get to um like celebrate a lot of like big milestones of the project and yeah. It evolved dramatically over the last few years and uh and the community has been like awesome, it's vibrant and big, and a lot of like big partners contributing to it, and it's really awesome to be part of it and yeah. I wanted to take this opportunity given to me just to take all of you back the history lane and remind how it all started.

A

It might be really hard to to do it all in five minutes, but I'll try. um So it's kind of impossible to talk about k native without mentioning kubernetes right and that's.

A

Why we're here and that's what kubecon is about and all of that and in 2014, when google open sourced kubernetes, it fundamentally changed how organizations manage their infrastructure develop and deployed their software like it created this whole new way of building services, where development teams could work independently and develop and deploy like services super super fast faster than ever before, and then in 2015 google partnered with the linux foundation and they formed cncf, where kubernetes lived since then and kubernetes evolved and matured, and there were a lot of new projects uh appearing close to the kubernetes ecosystem and a lot of like big collaboration.

A

Big partners started contributing to these projects in 2017, google and its partners. They released istio that addressed the need to easily connect and manage microservices that operators needed and it helped them to understand what was happening in the back of the infrastructure.

A

A lot better and around that time, people um like like understood that there was a new need that emerged for users to automate the boring parts of uh building and running services to uh to be able to focus on high value, differentiating like features and uh that's how people started thinking about k, native meaning, kubernetes native, and I did some digging into the original like design, dogs and the goals for the project and all of that and by the way, initially, the canadian project was called ella for us.

A

It's just a small fun fact for you and the original design goals were to have something that was very like familiar for kubernetes users. That would cover the tasks of building your containers and deploying and scaling workloads and managing events uh in your applications at scale and like that were also conformant, and um that is how okay nato was born. uh The first commit uh to canadian repository happened on january 30th 2018., so we invested in these projects and made them open source because at google we believe that open cloud enables faster and better innovation.

A

It reduces uh risks of vendor lock-in and um like gives customers the flexibility and choice to manage migrate and like build all their applications across different cloud providers, and customers have autonomy and control over their data and applications, and they can adopt google technologies without having the technology risk and open standard also creates value and trustworthiness for all the ecosystem partners, uh the users of software.

A

They they get transparency and consistency uh for the software they use and service providers get to rely on all the rely and benefit from partner ecosystem, like in case of k, native right and canadian, and its well-defined apis um enable all of these benefits uh for the whole ecosystem, like users can uh run workloads and kubernetes on prem or on cloud and service providers can build high value like for their customer customers by providing conformant and portable uh managed services, and that's exactly the value google gets out of k native as well.

A

We're able to bring google cloud services to more physical locations and work uh to provide the best in class managed service that is knative, conformant yeah and I said, and open cloud relies uh on open source to deliver the portability that users expect and that's why it was very important for the k-native community to release its official k-native specs and build the conformance process to have a single standard api that all service providers would meet and conform to.

A

And that way we could guarantee our users that their code would work out of the box if they were switched to other cloud providers, other service providers and um even like, if they want to move to different physical locations and so on, without worrying too much.

A

And um it was a big milestone for the project to to reach 1.0 conformance specs and a lot of people put a lot of work into it and we established a like clear conformance uh process and, as a result, uh google have now submitted uh cloud run and cloud run for antus uh to google products based on k native for conformance review and it's going through the process.

A

And um it's thanks to many people uh who worked on this conformance specs, that we were able to fulfill k, native's uh promise of portability, and this pull request is still open. If you, if you are assigned to to them, don't forget to to review them. Okay- and um I mean that leads us to where k native is today, I mean we can talk a lot about like different things.

A

That happened in the project, but I think that today it has like eight commercial offerings based on on k native and there's like 450 companies, contributing to it there's like more than 2 000 contributors to the project, and it's super like big and huge for any open source project, especially, I would say relatively this young and also k native became the most popular serverless uh layer on kubernetes, which is a big thing to celebrate over and over and and if you've been following the community.

A

More exciting things happened in the past a few months, and in november last year google announced their intention to donate okay native to cncf. In february this year, k native project was officially accepted to cncf incubation, which allows this new phase of community-driven innovation, uh inca native, to begin, and this is very exciting and we are super excited about things to come to k native uh within, like cncf, very close to kubernetes and its ecosystem projects.

A

We expect great collaborations to continue with the communities in cloud native ecosystem, especially now that we announced that istio will be also joining cncf and which means that there is a full stack for serverless applications, development now and as google. We are committed to support and improve critical cloud native, open source projects by working with our customers, uh our partners, uh foundations and open source communities and yeah. That's it for me. I wanna give the space to the next person before I get kicked out.