 Thank you, Carlos. 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 Knative Con. And I started working on the project somewhat recently, mainly helping with the transition of the Knative 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, this is really a special day because I get to be part of Knative Con. I get to celebrate a lot of big milestones of the project. And yeah, it evolved dramatically over the last few years, and the community has been awesome. It's vibrant and big, and a lot of big partners contributing to it. And it's really awesome to be part of it. And yeah, I wanted to take this opportunity to give in to me just to take all of you back to history lane and remind how it all started. It might be really hard to do it all in five minutes, but I'll try. So it's kind of impossible to talk about Knative without mentioning Kubernetes, right? And that's why we're here, and that's what KeepCon is about, and all of that. And in 2014, when Google open sourced Kubernetes, it fundamentally changed how organizations manage their infrastructure, develop and deploy their software. Like, it created this whole new way of building services where development teams could work independently and develop and deploy 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 appearing close to the Kubernetes ecosystem. And a lot of big collaboration, big partners started contributing to these projects. And in 2017, Google and its partners, they released Istio that addressed the need to easily connect and manage microservices that the operators needed. And it helped them to understand what was happening in the back of the infrastructure a lot better. And around that time, people understood that there was a new need that emerged for users to automate the boring parts of building and running services to be able to focus on high-value differentiating features. And that's how people started thinking about Knative, meaning Kubernetes native. And I did some digging into the original design docs and the goals for the project and all of that. And by the way, initially, the Knative project was called LFROS. It's just a small fun fact for you. And the original design goals were to have something that was very familiar for Kubernetes users that would cover the tasks of building your containers and deploying and scaling workloads and managing events in your applications at scale. And that was also conformant. And that is how Knative was born. The first commit to Knative repository happened on January 30, 2018. So we invested in this project and made them open source because at Google, we believe that Open Cloud enables faster and better innovation. It reduces risks of vendor lock-in and gives customers the flexibility and choice to manage, migrate, and 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. The users of software, they get transparency and consistency for the software they use. And service providers get to rely on all the rely and benefit from partner ecosystem, like in case of Knative. And Knative and its well-defined APIs enable all of these benefits for the whole ecosystem, like users can run workloads on Kubernetes on prem or on cloud. And service providers can build high value for their customers by providing conformant and portable managed services. And that's exactly the value Google gets out of Knative as well. We're able to bring Google Cloud services to more physical locations and work to provide the best-in-class managed service that is Knative Conformant. Yeah, and I said, Open Cloud relies on open source to deliver the portability that users expect. And that's why it was very important for the Knative community to release its official Knative specs and build a conformance process to have a single standard API that all service providers would meet and conform to. 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 even if they want to move to different physical locations and so on, without worrying too much. And it was a big milestone for the project to reach one point dog conformance specs. And a lot of people put a lot of work into it. And we established a clear conformance process. And as a result, Google have now submitted a Cloud Run and Cloud Run for Anthos to Google products based on Knative for conformance review, and it's going through the process. And it's thanks to many people who worked on this conformance specs that we were able to fulfill Knative's promise of portability. And this pull request is still open. If you are assigned to them, don't forget to review them. And that leads us to where Knative is today. I mean, we can talk a lot about different things that happened in the project, but I think that today it has eight commercial offerings based on Knative. And there's 450 companies contributing to it. There's more than 2,000 contributors to the project. And it's super big and huge for any open source project, especially, I would say, relatively, this young. And also Knative became the most popular serverless layer on Kubernetes, which is a big thing to celebrate over and over. And if you've been following the community, more exciting things happened in the past few months. And in November last year, Google announced their intention to donate Knative to CNCF. And February this year, Knative project was officially accepted to CNCF incubation, which allows this new phase of community-driven innovation in Knative to begin. And this is very exciting. And we are super excited about things to come to Knative within, like, CNCF, very close to Kubernetes and its ecosystem projects. 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, 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, our partners, foundations, and open source communities. And yeah, that's it for me. I want to give this space to the next person before I get kicked out.