 Hello, everyone. I'm Charly D'Orbettichet, and I'm going to share the news today about the Kivano project. So this is a very exciting opportunity for me to be there for a couple of reasons. The first one is that the Kivano project evolved a lot during the past years, and we have a lot of things to cover because we created new projects, we expanded the way Kivano works, and the landscape we can address with Kivano. Another reason to be excited is that I'm also a French guy, and I used to live in Paris for quite some years. So yeah, that takes very special to me to be there today. So, let's start, and I'm with a colleague today, so Shuting, can you start presenting yourself and tell us what Kivano is? Sure. Hey everyone, my name is Shuting Zhao, and I'm a Kivano designer, and we both work at Nomada. So the most common question we got from our community is that, you know, what does Kivano mean? Well, it's actually a Greek word which means govern. And Kivano starts as a policy engine which helps secure, automate, and enforce compliance of your Kubernetes clusters. And it's currently in incubating status. We have expanded Kivano beyond just Kubernetes, so really everything is around policy as code. So, Zhao, what does the Kivano community look like, and who are using Kivano? Okay, so Kivano has a great and large community. We have more than 3,000 Slack members today in our Slack channel, making it the second most active Slack channel in the Kubernetes workspace. We also have more than 300 contributors and 5,000 stars on GitHub. And the project was actually adopted by large companies like Spotify, LinkedIn and Yahoo. So it's more and more used by large companies. The project addresses security enforcement, and that's the most recurrent use cases like supply chain security, image verification. It also helps implementing multi-tenancy and tenant isolation. So the title of this presentation is Top 10 Kivano Features. And we are going to start with the shooting favorite top five. So let's go to you. Yeah, sure. So there's really no programming language required when you write a Kivano policy. And as Zhao mentioned, the typical use case is around validation to enforce your security posture of your cluster. We have the automation through mutation policies, and you can automate the generation of the multi-tenancy environments. And you can even also schedule the removal of your Kubernetes resources. And another interesting one is around securing the software supply chain, which is through our integrated image verification policy. We have the support for both cosine and notary. Another great addition to have is the external data lookup. So you can do it fetch it through the APS over directly or through any of the services that is running in your cluster. And the most exciting one is the Kivano Chansol, which is a testing framework that we developed recently, which improves our integrated unit tests as well as E2E testing Kivano. So those are my top five. How about you, Zhao? So my top five are on the slides, but not in this particular order. We had to choose another for the presentation. So I think one of the great possibilities with Kivano is to apply policies outside of a cluster. In a CI CD pipeline, for example, to validate that the pull request you are about to merge is not going to violate the rules you define in your policies. So it's really up in the chain. It's before the code is even merged in your main branch. Yeah, this is extremely useful. The Kivano reporting system is also extremely useful to quickly have another view of the violating resources in your cluster, what is good, what is wrong, what is correct, what can be improved. And it helps a lot working with teams to get more secure workloads, more reliable workloads. The recent addition of policy exceptions helps a lot in this area. You can have policy exceptions completely decoupled from your policies and from your resources to allow temporarily a resource to violate a certain set of rules. And this way, at some point, when everything has been fixed, you can delete the exception. And if the violation comes back, it will show up. In 112, we are adding new features to support much conditions at the policy level. And this allows filtering resource that will be sent to the webbook by the API server in a very fine-grained manner. So it makes the webbook mechanism more reliable and more performant. And in the same spirit, we now can generate validating admission policies directly from Kivano policies. So everything happens at the API server level for better performance and better reliability. Shooting, do you want to talk about other projects? Sure. I would like to take this opportunity to introduce Kivano family. We have the Kivano playground. The idea is originated from the need of showcasing Kivano without a running Kubernetes cluster. It's easier for collaboration and troubleshooting. And we have policy reporter, a big shout out to Frank over there. He donated the entire project to Kivano, which helps visualize the violations. And you can send notifications to the configured targets like Elasticsearch, Grafana Lowkey, Slack, and so on. Two more exciting projects. Kivano JSON allows you to apply Kivano policies anywhere. And Kivano JSON, we just mentioned, which is built on top of Kivano JSON to allow declarative A2E tasks in Kubernetes. So there's always more to tell, but, you know, we're short on time. And Charles, where to meet us? Yeah, sure. So it's all about community. So thank you for joining. You can join us on Slack. We have a booth in the project pavilion. So you can come and talk to us at the Kivano booth. And we also participate in the Contrip Fest on Friday. So don't hesitate to join and open your first pull request on one of our projects. That's it. Merci beaucoup.