 Hi, everyone. I'm pleased to be presenting in front of you all about Meshree today. First of all, I would like to thank KCD Chennai for giving me this great opportunity. So basically, my presentation would be about giving an overview of Meshree, which is a cloud native manager and a CNC project. So a quick introduction about myself. I am Pranav Singh. I am from the layer 5 community. I am being around the community for almost two years now. I do all kinds of open source contributions in the Meshree ecosystem. And last year, I also did an LFX internship at layer 5. And in case you'd like to know more about me or if you want to see my work, do check out my social handles. And you can check out my GitHub, Twitter, or layer 5 community profile. So moving forward, personally, I like to understand the features of a project only when I first understand the architecture. So first, let's talk about that. So on a high level overview of Meshree architecture, so Meshree, as a tool, supports a number of different deployment scenarios. So you can deploy Meshree either in a Docker-ized environment or in a Kubernetes environment. No matter which deployment scenario you use, Meshree auto detects Kubernetes config. Or you can always pass your special configuration either through CLI or the UI. So once Meshree detects a Kube config, what it does is that it deploys the custom controllers onto each of the detected Kubernetes clusters through the Kube config. And once it does that, like one of the which, so Meshree server deploys Meshree operator. The responsibility of Meshree operator is to manage the lifecycle of other two custom controllers, that is Meshshink as well as Meshree broker. The role of Meshshink is to fingerprint and determine resources in your cluster. And the role of Meshree broker is to send those discovered data from Meshshink to Meshree server. Basically, Meshree broker is an implementation of NATS, which is also a separate CNC project. You can read more in depth about that in the documentation of Meshree. But once Meshree server receives all the data discovered by Meshshink, what it does is that it saves all the data into its local SQLI database, which helps in later retrieval of data for Meshree UI and other functionalities. So Meshree also have a first class integration with Prometheus and Grafana, which means like all your already running Prometheus and Grafana in Kubernetes clusters are auto discovered. That means like Meshree UI will prompt you to connect to them. They will auto detect the URLs. And once you connect to it, Meshree will actually auto ingest all your already configured Grafana charts onto the Meshree UI so you can see all the observability which you are already seeing in other of your tools. So a couple of other features of Meshree is like it helps you manage Kubernetes lifecycle, your service misses lifecycle, as well as your applications. So in case you don't know, you can ingest all your Helm charts, your Docker Compose application, as well as your standard Kubernetes manifest directly from Meshree UI. You can import them through the UI and also through CLI. Moreover, Meshree also supports continuous optimization through its performance management side, which like earlier we were discussing how difficult it is to do performance management in one of the earlier presentation today. So basically Meshree, as of today, supports three low generators, which are WRK2, FortiO, and Nighthawk. So based on your needs, you can use any of them for your use case. Next is the low code visual configuration, which we would be seeing in a minute in my demo. And next is the service catalog, which is basically a public facing catalog on which you can publish your designs, your infrastructure design to the community where you can get feedback on the designs and you can share your designs with others so that others can also use, provide you feedback. Your work would be appreciated. And next is about integrations. Meshree, as of today, supports 200 plus integrations with different projects across the CNCF landscape, as well as other open source projects. So in case you'd like to know more about the integration, about each of them, make sure you check out Meshree.io slash integrations. And next is about the Meshree catalog. So Meshree catalog, if you'd like to see, you can go to Meshree.io slash catalog. And as of today, it supports Wassum filters and designs, or you can also know, also known as patents. So basically patents are a representation of the infrastructure in a codified way. So you can not only publish them on the catalog, you can also save in your Git repositories and version them. And Wassum filters is a hot topic if you don't know, like it's a great way of using them through Meshree. And now quickly I'll show the demo. So currently we are seeing the Meshree dashboard, which basically give you a high level overview of different stuff, which is either discovered by Meshree server or registered by Meshree server. So currently we can see in the workloads, they are different Kubernetes sources discovered under different, across different namespace connected to Meshree server. Then we can also see Mesh model categories and constructs basically. So a little bit overview of Mesh model is like, it's a different way of representing applications, which can be used as an integration with Meshree. So if you know about OAM, OAM is open application model, which is a way of defining your application in a platform agnostic way. It's very similar to that, but it's like OAM on steroids because you can not only describe your application, but you can also describe the policies as well as the relationship which would be used for those applications. So now in the settings area, we can see different Kubernetes clusters connected to my specific playground deployment. So here you can see the status of your Kubernetes cluster. You can do different stuff with, you can check the connectivity of the Kubernetes cluster. You can also see the state of the custom controllers of Meshree, whether they're healthy or not. So that's quite helpful. Now we would be seeing, now we'll be seeing a visual way of doing stuff in Meshree through a plugin of Meshree, which is MeshMap. So currently it's about two modes that is designer and visualizer. In visualizer, it's a read-only way of discovering, read-only way of seeing your Kubernetes cluster. So for today's demo, we would be focusing one of the cluster that is Kubernetes. And we would be, like it helps you, you can filter the resources based on your need to increase or decrease your views. So we have filtered on namespace, deployment and pod, and we are currently seeing just Meshree and KCD namespace. So you can see currently KCD namespace is not available, but we'll quickly deploy that through the designer mode. Designer mode basically helps you to visually configure your infrastructure. And I'll skip quickly to show the importance of. So I would be like dragging and dropping namespace onto my canvas. I would be giving the name of the namespace, KCD namespace, and then I would be dragging and dropping deployment. And I would be filling a couple of standard stuff, like the name of the deployment, KCD deploy, the namespace, KCD namespace, which is autofill. Quickly, why I'd like to give an overview, like whenever I deployed, whenever I dragged the deployment onto the namespace, the name of the namespace got autofill. How it does that is because internally, Meshree also integrates with OPPA. Meshree internally have an OPPA integration engine. What it does is that it actually evaluates the relationship between different components on the canvas. So currently there's a hierarchical relationship that got evaluated by OPPA, and it allowed the deployment to be a child of the namespace, which is a separate component. So then the namespace value got autofilled. So now I would be just filling the labels for specific ports. Labels are app and the value would be KCD app. Similarly, the label for the ports. Then I would be configuring the container that is name would be engine X latest. Image would be engine X latest. Application name would, container name would be KCD app. Then the standard port, port 80. And you can also see that on the left hand side, number of people collaborating on the designs. So the best part is that a number of people can collaborate in the same design and you can share your design with others as well. Like currently you can share your design with any number of people. You can write their email address. Once you click on the publish button, what it will do is that internally, Meshree will send an email to the specific people who you specify and then they will receive an email. And the content of the email is like publicly available. You are on which they can open the design and they can start contributing with you onto your design. Next is that we'll deploy. I'll just quickly go over this. Then we will be deploying this specific design onto our cluster. So as you can see currently, we can check different clusters onto which we would like to deploy this specific design. You can check one Kubernetes cluster or many based on your requirement. And you can also see that what this deployment model does is that it also dry runs this specific design beforehand. So how it's helpful is that, for example, even before you deploy a design, you would be knowing whether that design would be deployable or not in the infrastructure. It can cause any problems or not. So it's quite helpful when you're debugging in your production environments. So currently I quickly deploy it in Kubernetes cluster. By the way, don't get confused. The name of the cluster itself is Kubernetes. So in case you're wondering why I'm calling it. So as you can see, once I came back to my visualizer mode, I can see the exact same namespace that I defined in my designer. The name of the deployment is also same. And inside, as you can see, inside of the deployment, there are two pods. Inside of each pod, there's one container. And this configuration is exactly what I did in my designer mode. And we'll now quickly, a couple of quick items is that you can also start up an SSS terminal directly from here. Or you can also stream logs for any of your containers from here so you don't have to go outside. You can also connect to your metrics and see directly here. Like you can see your metrics as well coming from either the nodes or the containers. OK. So now we'll just deploy and go back to our final slide. So once you deploy, you'll go back to the visualizer and realize that the designer, your specific deployment does not exist. And it's got, I'm deleted from your cluster. So just last slide I have. Can we switch this one slide? Yeah. So in case all this was, actually all this which I just showed was just a 10% of metrics I can do. It can do a lot more things. But considering the time constraint, we would be moving forward. So in case you liked all this and you want to contribute to the project, do join the layer 5 community. You can join the Slack channel where everybody would be very welcoming to you. And you will actually make new friends. You can check out the beginner's guide, which will help you to get started to understand which text that you should be knowing and how you should be going about it. You can also connect to any of the mesh mates. Schedule a call with them. They will help you get started instantly. You can, if you want to take a screenshot, this is the best slide. Do take a picture of that. So you'll have an action item after the presentation. And yeah, that's the final slide. That is like, Meshree is also the number one LFX project and the LFX mentorship program. And yeah, in case you have not started using Playground, then do check out play.meshree.io and start using it. It was actually unveiled in the recent KubeCon EU 2023 by the CNC of Tags Working Group. So in case you missed out. And also do check out Meshree's GitHub, Twitter handle, LinkedIn, Slack, YouTube channel, as I discussed for them so that you don't miss out on the important information. So that's it. Hopefully all that was intriguing and you didn't get bored. So thank you for listening and bearing with me. Thank you.