 Hello, everyone. Welcome to Cloud Native Live, where we dive into the code behind Cloud Native. My name is Taylor Dolozal, and I'm a senior developer advocate at HashiCorp, where I focus on all things infrastructure, application delivery, and developer experience. Every week, we bring a new set of presenters to showcase how to work with Cloud Native technologies. They will build things, they will break things, and they will answer your questions. Join us Wednesdays at 11 a.m. Eastern Time. In today's session, Diego and team have joined us to talk about from zero to production in less than one hour with Crateo, platform ops. This is an official live stream of the CNCF, and as such is subject to the CNCF code of conduct, which simplifies down to please be excellent to one another. Please don't add anything to the chat or questions that would be in violation of that code of conduct, and be respectful of all your fellow participants and presenters. With that, I'd love to hand it off to Diego and team to kick off today's presentation. Diego. Thank you so much for the invitation. I am Diego Braga, and I work as a solution architect. Be also an architect of a startup that is called the NIGIX, but I will tell you later on what we have prepared for you today. And I will pass the microphone to Luca. Okay, hi. I'm Luca, and I am working on Crateo. I'm a developer, and today I played the role of head of a platform team, and we will see you later. And then I pass the microphone to Mauro. Okay, thank you Luca. Hi Mauro. I work in Crateo as a developer. I am a JavaScript enthusiast, and I love to have you here. Yeah, and I'm Susan Daniels, and I work for Spotify, and more specifically, I do developer relations for an open source project called Backstage. You might be familiar with it. Yeah, pretty much familiar with Backstage. So let me break the ice for today's livestream. So we started to develop Crateo Alphamops last year. It's an open source solution, which aims to give us a centralized way to create a provision and orchestrate and coordinate any kind of resource in any kind of infrastructure adopting the collaborative approach. And what we would like to do today is to do some storytelling, some role playing. We will be the role of a startup that is called the DJIX. And let us change the t-shirt and put the t-shirt on the DJIX team. Okay, so we can start. Okay, Luca Mauro, I have a really, really great idea for our startup that is called the DJIX. I know it sounds like the DJIX, but it's because I had a really, really great idea. So, since we do know that bees are engaged in this time, and we must make sure to protect them and find a way to protect them, why don't we develop an application that gives advices on how to help them? What do you think? Yeah, it's a good idea. Besides, it's more important to take care of the poor bees. Yes, we must save bees. Okay, so we need, as an architect, I think that we need to find a way to go into production in really, really few fields. Because business is running, we have business requirements, we have a lot of things to do. And for sure, I do know that the dev team and the platform team will fight over the time. So, let's find out if there is a solution out there to collaborate and to spin up the infrastructure to deploy the application and do things in the right way. Yeah, as a head of the platform team, I've long been targeting Crateo, which contains so many technologies I love. And there is also a cool CLI. So, we can try to use it and to install the platform. What do you think, Mauro? Yes, okay, now I go to Google and I send you the link to the chat. Oh, okay, thank you. As an architect, I would like to spend a little bit of time. What is a platform? And what platform ops means? And usually I look at Google for definitions. So, I don't know if Mauro can Google platform ops for me, but basically what a platform ops is, is an approach, is a methodology, which aims to organize the platform team in a way that the platform team is a group of people. And the goal of this goal is to offer services that are consumable as APIs from the end users. And users can be any one can be developers, can be business analyst, can be data scientist as Luca knows, as a high-level platform team are struggling to find a standardized way to expose services and only a good way to do implement automation. Okay, so, I was reading this on Google about platform ops, and I think that Mauro could share the screen. Yes, I'm already sharing my screen. I found my repository of Croteo on GitHub. Okay, so let's wait for the monitor to come back. Yeah, because, okay, it is, okay. Basically, I was reading something about Croteo. Okay, it is here. Yeah. I was reading something about this solution, because actually I was looking for, as an architect to the Cloud Negativity Foundation landscape that is really, really rich of solutions. And it is rich, but it could be also complex for a company, regardless of their size, to choose, to charity technologies based on the maturity of the CNCF, based on the community, based on a lot of things. And I was really looking to different solutions that are interaction from the cloud native community. And I saw that Croteo is a platform that depicts the open source projects from the CNCF and standardize the way you offer these services on a catalog. So as an architect, I do believe that the platform team should construct the complexity of infrastructure provisioning, machine learning, model sharing, et cetera, and give only forms to the exactly as Google, Azure, Amazon, all the public provider to their console. So this solution of Croteo platforms, I think it should be tried. Also because it's based on a lot of interesting projects, like Backstage. And I was following Backstage in the last year, and Geiger is a really interesting developer portal that Spotify Engineering released to the community. And they made a lot of interesting features in the last month, but I don't want to still have the topics to choose. So I think that Croteo did the right choice to integrate Backstage for the portal. But also there is another interesting project that Croteo is leveraging, that is Cosplay, that we really love it. And it's the same way, I mean the approach is exactly the same as Backstage if you think about it. So you have manifest that describes something, everything is based on data, so everything is audited, so everything is based on Kubernetes. We are talking about Kubernetes APIs, there is no locking of proper language, et cetera. So I think these projects are really, really interesting. The fact that I use them and collaborate with them is something that our startup should use. So I think that Luca is right, and we should install Croteo in order to spin off our application. These are struggling, they are in danger, so we have less than one hour to work to save them. Yeah, I read this as well, the Kubernetes cluster for Croteo. So Luca, do you have a... Mauro, do you remember the EKS cluster that I gave you the reference later on? Maybe, no, I don't know, let's try to connect to it, wait. Yeah, you could try to install Croteo there. Yeah, okay, let's try to install. Let's check. Okay, so give me the kube-config file on the chat. Okay, I'll send you on the chat. Okay, here you go. Okay, so easy, okay. Brings to Croteo, okay. Just a second, I'm installing it on my terminal, just a second, okay, no, okay. You can view my screen, okay, it's installed. So what I need to do, okay, Croteo... Just a couple of commands. Oh, easy. Okay, that's fine. And if I can say something, I will complain to the guy that wrote that install it on me, because as an architect I would like to see more documentation. So I will look at the initials and say that the regular section should be expressed better. Do you agree with me, guys, because... Yeah, yeah, I hope so. Two instructions. Yes, yes, Bob. Absolutely. Easy, easy, install. And I think it's fast, 37. Okay. And so the second command is... Okay, Croteo install core. Two commands, okay. Yeah, it's super easy. It looks like super easy. We'll see if it works. Croteo install core. It's faster and it's easy. Oh, okay. Okay, here we go. Install. Let's check the cluster. Okay. My alias are very... Super alias. Yes. Okay, getting a space. And okay, I jump in Croteo system. Okay, and okay. Okay. Okay, I think it's installing the other component. Okay. Oh, Croteo dashboard back end from 10. Okay, creating a container. Creating. Okay. Yes, running. Okay, creating container. Okay, running. Okay, not yet ready, but I think... It's everything up. Yes. Yeah. I think he's building many things on the background, but we can wait some minutes. Guys, right back, can you hear me? Yeah. Yeah. It's kind of... So you are ready to go into production. Can everything is live? Not yet. Just wait some seconds. Okay. Okay. I'm worried that we are late for going into production. These are struggling and we find a way to go into production. We're still creating the back end. So as far as I read on the documentation, the core module that we installed, I think, there is backstage within it. So... Yeah, absolutely. Yes. The core part is leveraging backstage as a portal in services. So I think that... I never tried it, but that should work in this way. So what I love about the Cratero platform is the last graph that you are showing. So as an architect, I love the loosely coupled technologies. I love abstraction, and I love using manifesto to describe anything. So Cratero leverages Kubernetes APIs because backstage does it in this way. Cratero does it in this way. It doesn't mean that Kubernetes is the only environment in which resources can be provisioned. So cloud native is really cool and a lot of companies are transitioning to this approach. But we don't need to forget the rest of the environment. They need some primates, maybe some legacy environments, etc. So the fact that Kubernetes as a control plane can handle a lot of different, also, side Kubernetes is a really cool idea, in my opinion. I don't know what you think, guys. Sorry, Diego. I'm just putting this DNS in our Cloudflare DNS just to have a better address. And I'm back here. And Luca, what do you think about this slide? It's easy. It's cool. What do you think? Yeah, it's clear. It's super clear. I like the way all the pieces are connected together. Yeah, it's cool. Okay. And what we can do with Croptail? Okay, just to dox the install. Maybe there is some information about the install because the DNS is not yet propagated. And I think it's about five minutes and it will work. The power running and the service are okay. Okay, let's try to go to the dashboard. And so dashboard. Oh, okay. Cool. It's running. Okay, it's working. Fantastic. Okay. Just about five seconds, but please can wait five seconds. Five minutes. Okay. And now we don't have some components. And okay, we need to create our big picture. Yes. Yeah. How can we do that? I think I found an example. Okay, maybe it's time to speak about Croptail. Sorry, backstage of Spotify. Yeah, so thank you. So let's wait until my screen is shared. Okay. Thank you. So I joined this cool tech company called the Bee Geeks. And I was thinking it was about music, you know, coming from Spotify where I work with backstage. I thought, well, music and backstage. Well, it sounds like a good idea, but it turns out it was a whole different story. It was actually about bees. But anyway, long story short, I joined the company and I had my onboarding. And during my onboarding, they talked about the tools they used. And one of the tools, it was backstage. Now, most of my onboarding took place in backstage. And let me just sign in a little bit here. In one of the documents, they had this onboarding document with all kinds of information I could find on the tools they used, where I could find what kind of documentation, like literally anything I as an engineer would need to be successful. But yeah, then you have this onboarding, you get your laptop, you get this document. But actually, you do not get to see something in the kitchen. You know, during your interview process, people will not show what tools they're built upon. And well, as an engineer, you're really curious. So the first thing I do is go into backstage here and see what kind of services we have and discover more about that. So for this, I use this software catalog. And in this software catalog, I see all these things. But basically, I really would like to know things I own. My team owns, because a person basically normally would not own anything. It would be a team owning a service. So let me see. Well, these are the things I own, but I could add other things to fill around, like the marketing department or maybe some lifecycle or text which are used in the service definitions. Well, the actions workshop, that sounds kind of interesting. So I'm just going to click that one. And when I do that, I immediately see all kinds of relevant information. Like I can see what it is. I can immediately go to the source and find where it is on GitHub. But I also can read documentation and learn more about the service. So that is a rather good start. The other thing I could also look at is maybe looking at how the actions are actually going. Not that well, so it's good that they hired me maybe to get away those nasty errors in the whole process. So let's see what's going on there. Well, there's obviously some error here. Let me just go to the log files. And I can discover this all without leaving this portal. So as you can see, this is an aggregation of several services, which we are using. For me, that's super handy because I get all this information just in one place. Now, if I would like to solve this problem, I would have to click the link and look what's going on and solve it in the tool itself. But this is like my bird's eye view of what is happening. I can also discover what APIs are provided but also are consumed. Well, naturally, I'm really curious. So I read the documentation and I wanted to know how this actually works. So I can dig up definition and maybe get more information and really learn how I would have to use this API digging through the source code of the application. Building up my confidence about the organization. Now, I could also do it on a different level, like from the API going down. I can see the relationships between the different services. So if I would go to the Spotify API here, I can see that it is used in three different consumers. And if I click that, I get to that one as well. Now, Backstage is not a developer portal. It is a platform for building developer portals. And by that, I mean that in itself, Backstage is basically a collection of plugins, which means that it has no opinion. It will really fit in your organization because you have the freedom to add, modify, remove any plugins you might need and configure them in the ways you like to see fit. So for instance, I gave an example for GitHub. It could pretty well be that for the marketing mini site, we would also click on CI CD, but it would be hosted on GitLab. And this is basically what you can get with those plugins. It makes it really extensible. And that is one of the reasons that Backstage was developed this way. So there are different plugins, examples, Argo CD, which most of the viewers might know as well, CircleCI, JIRA, PagerDuty, SNCC. There's many, many plugins, and you can develop them yourself as well. So when we developed Backstage at Spotify, that was one of the big things which made it really successful because the engineers who own services or a certain domain, they were able to create their own plugins and by that enabling themselves and others to venture outside of their domain. So they could like discover the services or create them. That is a little bit of background. But yeah, basically every tab I click, every thing you see here is all based off plugins. So here you can see for instance the PagerDuty. Well, I don't know how, just my first day and I'm already on call for the marketing site. I don't know if this is a good company to join but anyway, this is what happens. So this whole catalog, it is built off of files, which is all YAML. You can populate it in different ways. It is not meant as a sort of truth. It is a place where you aggregate all your different sources of truth and offer that experience where I as a new engineer can easily discover this information. Another part is documentation. So like you can see, you can also create documentation here and aggregate it also from already existing sources. For instance, you would probably include the documentation with your source code. That's perfectly fine. But if you have other places where you have documentation, you can all aggregate them into this single place. So if I for instance would search on GitHub, actions on too many results, workshop, it will search both my catalog and all known sources for results. And then I can filter between documentation or things in the catalog that could find. And there I can resume my journey on the information I was looking for. The other thing is creating. And for this, we use software templates. And with the software template, I can basically create a service on base of a skeleton which would include all best practices the company has. So if I build up my confidence with documentation, learning about the APIs, the way the applications actually work, I could start my first project here and be also confident that it would align to certain standards and best practices as well. Once again, these templates, you can just edit them. It's all obviously YAML. And you can create it with actions which are already available. For instance, Bitpocket and GitHub and GitLab. But you can extend that as well. So let me just create something. If I fill out this form, let me just do that. I want to bore you with my guidepost. I can basically fill out all the information I need to do this. Let me select the correct team. It will create a repository. With the skeleton files, it will register it in the catalog and it will also create the documentation. So if it is finished and I would open it here in the catalog, you can see that already my project is there. So hopefully here are some things already in there to get me started. And also the documentation link is already there as well, as you can see. So that is a good starting point for me and it will massively improve my experience as a developer. So it being so extensible and by using plugins, it is a perfect candidate, perhaps for the big leagues to control their software with. We see many more different projects adopting backstage as well, creating a plugin or like building a whole experience with this beautiful project as a source. So thank you. Back to Diego. Awesome. Diego, are you still with us? I think we lost Diego. No. All right. While waiting for Diego. Oh, go ahead. Speaking about templates. Backstage templates, Mauro. I found that template is our application. Do you have the link? Let's try to apply this template. Okay. You share the screen. Okay, perfect. Okay. I'm getting the link from the chapter. Yeah. Okay. Okay. Thank you. Thank you, Diego. Okay. Let's try to create our BGX app. We put the whole of the template and let's analyze it. And import. Okay. It's fine. Well, we have the BGX app template. Yeah, great. What's this name for our app? Save B. Yeah, it's cool. Do you like it? Yeah, I love it. The description of our app. That's it. That's name. That name is a B plus. Yeah. Okay. And next step. Okay. We integrate our app with the captain delivery platform. So we have a super secure captain API token. Okay. And the owner is... Sure, two every month. Yes. I think it's not a good idea to share our captain aid token. So save B is the repository. Okay. Looks fine. Let's create. Okay. No. Something. Let's retry. Save B2. Maybe the second item is better than the first. The R7. I show you again the captain API token. So you can copy it. Repository. Save B2. Okay. Now it's publishing correctly. Maybe Github something... Some problems on the API. Okay. It's... Okay. Authenticating on our captain, creating project, creating service. So let's go in my Github page. We have a save B2. Save B1. Okay. Looks fine. Okay. In our captain we have a save B2. And we have three stages. We have test and prod. So in tests we can do some tests. And it's delivering. Okay. So I back on my terminal. And I get the name spaces. With my super alias. And I jump in save B2 dev. Okay. So give pods. Not yet running. But I want the service. Because I want this external IP. And I go here. Okay. Not still working. But the container is not ready. Okay. Stay here. And wait to deliver the app in all the stages. Okay. It's super easy. Just with one click. We are delivering our save B app. Okay. Just a second. Okay. Let's try our URL. Not yet. Okay. But. While it's creating our app. I go back in our. Crateo. And go in save B2. Okay. And I know there is this card. This is the overview of our app in captain. Only in dev stage now for now. But I know there is this overview. Okay. Dev is succeeded. And test is still running. Let's try to. Whoa. That was some hop. Yeah. Okay. We are the VGX. Okay. Congrats. Okay. But. I want to show something more. I think. We can do something better. Okay. Let's. Wait all the delivery in the dev test and production because in captain we have. I'm sorry. Three environment. In. Dev. All is there. The test is delivering and the product not yet. But I think. It will be. So fast. Okay. Okay. Let's wait. Some seconds. Okay. This is okay. So if I back in. My. Platform officer. We can. See the three stages. Off. Our. Okay. We have shoes to use. Captain to delivery. Because it's really. Faster and easy. Normally. All the operation that I. Done with our template. Is. Made from the captain. CLI but. We have. Integrated our. With the captain API. And so we did. Just. One click or one to click. We can delivery our. Application and. So this is. The second thing. I want to show you. We have. The. First. The. And I show you. How we can. The. So I. Go back. And. New delivery. My. This is. The stage is a dev. And this is the. Major with the. So delivery. Okay. I go back in captain. And. Just. Okay. This is the. Delivery of our. To. Second version of our application. The first version is. In devs test and the production. I just. To the. CLI. Get namespaces. Okay. We have three namespaces. One for that one for product one from test. And in every namespace. There is. A pod with our house on application. So. I go back in captain. And we wait. The delivery of. Ever. We have the zero one. Version. But. I think. Faster to. Switch. Okay. So the captain tab. Shows. The second context. Because in captain. And we have. The test product and. You can show. The details of every steps. Some information. In a test and product the second. Delivery is. Is given. From the previous context. But. Of. So I think it's delivery. I go back here. Okay. Okay. This is the second version of our application. So we have the home page. With a hive. But. If you. Go in Australia we have these. Amazing bee. But we need Italy we have these. Japan. And the USA. Okay. Great. Just with the one click. And then we have the delivery. Our application. For for now. Sorry. Look I have only one to. Images. I'm developing the. Up. And the night. And not yet ready for the. The version three. But I think it's a good. A good start. Yeah it's a great start. Besides we did all in a real time. And less. In a time less than one hour. So. Was great. Yes. Yes in 40 minutes we have. Two. Version of the. And with captain. We in the. Backstage we. We have all the tools. That works. Very cool. Really fantastic I'm sure the. The stakeholders or be handlers will be very happy about. Getting all of this out so quickly. So congratulations. Yeah. I do have a few questions for all of you. If there are any. If anyone out in. Watching the stream has any questions please. Feel free to throw those into chat. And we'll be sure to kind of. Get those questions answered. One thing that I did see come up was. In relation to backstage. And seeing that there was an Argo plugin. Is there a plugin for flux was one question that I saw. Or just. Do you all know of any plugins that are going to be added. That you all are excited about. Yeah so. If you want to. Know what plugins we currently have. You can go to backstage.io. There's the. Big big. Plugins button. And you can discover all the. The plugins we we have. I'm not aware of. Of flux. But. It just might be. You could also find it out by. Joining our. This quarter channel and just shouting out. Anybody. Is already working maybe on that. Or. Has interested in interest in that and. You know maybe even. Pick it up yourself it is. Since you have project so. Feel free to contribute well. Feel free. You're really really invited to contribute. And at the functionality you. You are missing. To backstage. Awesome awesome thank you so much. It's it's always fun to see what. Plugins people are looking for and then. You know like we said if you want to get involved with. Adding some. Now now might be the time to take a look at. How to contribute. How to help out on that front. Or at least raise that issue up so that other people can. Think on that and kind of work with you on that front. Another question. It's just adding an issue and. People will. Will reply to that and pick it up or. You never know. I think that's the biggest thing with open sources. There's kind of always that worry is just like. I really want this thing but. I have to do so much work to get it to that point but. Like you said you know if. Sometimes it's as easy as raising an issue and then people are. Like a good idea and then I can kind of help make that happen. Awesome. One other question that I have for you was. How does one add a new service to the. Catalog pertaining to back. Backstage. Yeah that that really depends. There's a there's a few way ways. So the. Like I. I've shown in the in a really really short demo. Is for instance by creating. A new component. With. Software templates that will add that to the. To the catalog. But basically. It'll. Like many things in life nowadays. It all comes down to. A little bit of Yammel. Which you which you would. Which you would add. This is something you could do manually. Adding that to your to your repo. And. Then importing it. So if I would go here to the create. I would register an existing. Component. I could just like point directly. To the. To the Yammel. It would be analyzed. And I can choose to import it. Another thing is I could. Basically also just point it to a repo. And. From there. And from there. It. Will offer to create it. Automatically as well. But there's many, many different ways. And you could. Like maybe have a. Have a custom processor. Which will read some source. Or maybe even a script. Which will generate all this. It's not up to me. It's up to you. That's awesome. Nice to be able to kind of have a framework to work within. And I know that in a few of the companies that I've worked with. That something like this would be. Highly beneficial. There's just so much time spent. Chasing down, you know who owns what. And how do I work with this. This tool or this API. Not opi, but the API. On that front. What's the best way to go about finding an owner of a service. Say if like something were down. Or I'm trying to take a look at an integration. How would I. What would be the best way to use backstage to look up that person. Yeah, I would just go to the to the surface. For instance, if it would be something. Which would be down for instance this marketing mini site. I would go there. I would see the description. I would see who's the owner. I would see who's. Who's on page or duty. I could create an incident like that. That functionality is in there as well. Provided by by the plugin. If I would like. For instance, I could click the team and I could see who's on the team. And that sort of things which other services to the own. So there's different ways to identify that. I could have also like type the service name in the in the search bar. And end up at one of these. Pages and go from. From there. It really helps because. The day infrastructure is becoming more complex. There's more and more and more engineers being onboarded. The prediction of the number of software developers working at companies is so high that I really wonder how we are going to even provide. Enough for them, let alone make sure that that they are easily on boarded. Into increasingly difficult. Companies. And another thing. Which is also. Quite complex is the infrastructure itself. Like. Well, let's just. Not mentioned the CNCF landscape map. That that alone says it all. But if you imagine that. You would work with. Only a selection of. A cloud native technologies. With. Within autonomous teams. Then. You can imagine that those autonomous teams might have their own implementation. Even or their own. A way. Of setting the standards. For for for their. Piece of platforms. So. Yeah, this really. Makes it it will not solve it. But at least you will be able to find it. And that's also why. Why this was started. Within Spotify a few years back. It's a music to my ears to hear that. So that's it's really fantastic. It's it's nice to be able to have that single place to look everything up. Because it is so difficult to, you know, rely on everyone to get their documentation together. It's it's difficult to do. Especially for, you know, things that aren't Greenfield. The things that are being. Either on boarded or just older system services. Maybe even. Some applications that require minimal maintenance. But the team really doesn't have time for. So it's nice to have a platform to kind of. Roll all those things up to you. So, so thank you all at Spotify for creating. This is really fantastic. And I wouldn't say that it is. Easy. But at least you can. Never. Never easy. Maybe straightforward. But possible is something that I'm happy to take. Awesome. One other question that I saw come in was. If my machine doesn't have enough resources to spin up an entire Kubernetes cluster. Are there some alternatives for me to be able to take in and actually start using some of these tools or inspecting some of them. I think that if no one has an answer one one thing that I've found helpful is the kind project the Kubernetes in Docker. I know that Docker for Docker desktop and Rancher desktop. There are a few platforms out there that enable you to kind of help out on that front. And to kind of get up and running as quickly as possible. I like Kubernetes in Docker in some of the some of the contexts that I work in because I can test things or pull down the latest version of Kubernetes as soon as it's been really close to as soon as it's been released and actually see what features are applicable and usable. Just a clarification. We will delivery. Sorry. Release. Yes. Version is a cloud version of all the platform. So if you don't have a power computer, you will can use our cloud version. That's really nice. I've seen one of the projects. I know we didn't talk about it today, but was telepresence and there's some interesting projects within this space. In order to kind of upgrade your computer or give it more capabilities. So definitely definitely recommend checking out that cloud offering if you all are curious about that. Awesome. I have two more questions, but if any of you out there in the interwebs have any questions, please feel free to throw this into chat and we'll get those asked and answered. My next question was taking a look at the integration environment. Everything had looked fine there. How could you kind of talk through how that promotion process works within the infrastructure configuration to bring things to production or kind of one environment on that front? What steps are involved? Sorry. I lost the connection for just a second that I can repeat the question. Sorry. No worries. So the integration environment that we started off with looked fine and was mostly straightforward to kind of understand. When it comes to promoting two different environments, can you kind of tell me what's involved with those steps with these platform operations? Okay. Okay. So in the web UI we have this button and this button calls the captain API. So for this demo it's very, very, very easy and very, very small that we just can delivery the dev stage in an image. But to captain API we can post a lot of settings and a lot of configuration and I think the next version of our planning will be more powerful. Awesome. Do you know if there's any way to ensure that deployment in production guarantees some predefined SLIs or SLOs? I'm assuming that would be with captain. But do you know how to go about satisfying those SLOs or setting them? The captain. Okay. It's based on the SLEI and SLAO files. And we have, I'll show you the plugin. We have a shipyard YAML in captain. And here we can define all the stages in our, for our application. We have the stages, the name, the test production, and the sequence. And we, with this button we have triggered the deployment delivery, the sequence delivery, sorry. In the delivery sequence it deploy the application in all of our stages. So when I click here, sorry, I click here, the starting stage is deaf but captain delivery all the application in all the other stages. So for example, yeah. Okay. We can post a delivery direct. So for example, if Luca wants to publish the application only in test, for example, it can post a trigger in the delivery direct and manage the version of the app in all the environment. And captain has some other cool functions. For example, we have a demo with the remediation. Remediation is that the application will pass to the next environment if only meet some requirements. For example, if an application, the second application is too slow to go in the production, captain can monitor it and can stop the delivery for the other stages. Excellent. Excellent. Definitely something to take a look at because that's nice to have those quality gates as we go up to each of the different environments. Wonderful. Wonderful. Well, thank you so much, everyone. One more thing. In captain, there are a lot of tutorials and very, very explained, very, very complete tutorial. And you can try the captain platform for the easiest environment, so in today's context, more complex. So I think it's a good product. Absolutely. Absolutely. And one more thing to add to that before we forget to mention that, but the Corteo team will release the backstage plugin, which you've seen in the demo for captain. So that is also something to maybe people are interested in as well. I think it's brilliant. You might think it's wrong. Thank you. Thank you. Yes. This is our first version of the captain plugin, but we are developing the first release to make it so stable. And we have the captain overview. And as you can see in the overview, we have the card, but we have also the card in the system. And not now for this demo, but we have a summary overview of all our environments. So for example, just for clarification in the system, you can use these details of your application. That's really fascinating. I really appreciate you all coming out today. Unfortunately, we are at time, but it's really nice to see kind of how all of these systems can integrate together and kind of connect. They are greater than the sum of all of their parts. So I think that that's, thank you so much for coming by to show us that as well. All of these things are, I've seen captain a little bit, but I'm kind of curious to check out all of the other things that you showed today. I've spent more time on stage than backstage, so definitely need to check that out. Thank you everyone for joining the latest episode of Cloud Native Live. It was wonderful to hear from the whole team today. We really love the interaction that we had from the audience. And join us next week where we're going to be talking about what's new with Coverno. Coverno is a policy engine designed for Kubernetes. Thank you again for joining us today. We hope to see you soon and have a wonderful week. Adios everybody.