 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 in Q&A. We also an architect of a startup that is called the DJIX, 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'm 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. I am, and then I pass the pot 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 in the 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, the role of a startup that is called the DGX, and let us change the t-shirt and put the t-shirt over the DGX team. Okay, so we can start. Okay, Luca Mauro, I have a really, really great idea for our startup that is called the DGX. I know it sounds like the DGX, 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 advice 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. So, yeah. Yes, yes, we must save bees. Okay, so 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 DGX team and the platform team will fight all 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 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 more time. What is a platform? And what platform ops means. And usually I look at Google for clinicians. 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, anyone can be developers, can be business analysts, can be data scientists, as Luca knows, as a high-level platform team are struggling to find a standardized way to expose services and a unique 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. As I can read it. 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 so complex for a company regardless of their size to choose how to charity technologies based on the maturity of the CNCF, based on the community, based on a lot of things. And there was a look to different solutions that are really touched on 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 how 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 models, sharing, et cetera, and give only input forms to the exactly as Google, Azure, Amazon, all the public provider to their console. So, this solution of Croteo platform ops, I think, should give it a try. Also because it's based on a lot of interesting projects like Backstage. And I was following Backstage in the last year, and it's really interesting. The developer portal, the Spotify engineering, released to the community. And they made a lot of interesting features in the last months, 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 cost-playing that we really love it. And it's the same way, I mean, the approach is something 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 looking of proper language, et cetera. So, I think these projects are really, really interesting. And the fact that I use them and collaborate with them is told me that something that our startup should use. So, I think that Luca's right. And we should install Croteo in order to spin off our application. These are struggling and are in danger. So, we have less than one hour to work to save them. Yeah, I had 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 kubeconfig file on the chat. Okay. I'll send you on the chat. Okay. Here you go. Okay. Oh, it's so easy. Okay. Very easy. Okay. Just a second. I'm installing it on my terminal. And just a second. Okay. No. Okay. You can view my screen. Okay. This is installed. So, what I need to do... Just a couple of commands. Easy. Okay. That's fine. If I can say something, I will complain to the guy that wrote that install. Because as an architect, I would like to see more documentation. So, I will look at the initial data that... That particular section should be expressed better. Do you agree with me, guys, because... Yeah. Yeah. Two instructions. Yes. Yes. Absolutely. Easy. Easy install. And I think it's fast. 37. Okay. And so, the second command is... Okay. Two commands. Okay. Yeah. This is super easy. It looks like super easy. We'll see if it works. Cordeo installed 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. Super alias. Yes. Okay. Getting in spaces and... Okay. I jump in Cordeo system. Okay. And... Okay. Odd. Okay. Okay. I think it's installing the other component. Okay. Look. Oh. Cordeo dashboard back end from 10. Okay. Creating... Creating. Okay. That's 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. Can you hear me? Yeah. Yeah. It's kind of... So you are ready to go into production. It's done. Everything is live. Not yet. Just wait some seconds. Okay. Yeah. I'm worried that we are late for going into production. These are struggling. And we find a way to... It's still creating the back end. Okay. So as far as I read on the document page, in the core module that we installed, I think there is backstage within it. Yeah. Absolutely. Yes. The core part is leveraging backstage as a portal for supporting services. So I think that... I've 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 loosely coupled technologies. I love abstraction. And I love using manifest 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. A lot of companies are transitioning to this approach, but we don't need to forget the rest of the environment. They need some premise, maybe some legacy environments, etc. So the fact that Kubernetes as a control plane can handle a lot of different... ... is a really cool idea, in my opinion. I don't know what you think, guys. Sorry, Diego. I'm just putting this DNS, FQDN, in our Cloudflare DNS just for whoever has 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 Cretail? 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 service are... Oh, okay. Okay, let's try to go to the dashboard. And so the dashboard is up close here, this one. Oh, okay. Cool, it's running. Okay, it's working. Fantastic. Okay, just about five seconds, but please can wait five minutes. Okay, and now we don't have some components. And okay, we need to create our widgets. Yes. How can we do that? I think... I found an example. Okay, maybe it's time to speak about Cretail. 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 Big Eaks and I was thinking it was about music, you know, coming from Spotify where I worked 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. 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 what kind of 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. 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. Another 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, that stage 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 will, 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 minisite, 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 discover the services or create them. That is a little bit of background. But yeah, basically every tab I click, everything 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, yeah, 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, no actions, don't want 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, a bit bucket and get up and get lab, but you can extend that as well. So let me just create something. If I fill out this form, let me just do that. Paste it. I want to bore you with my guideposts. 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 backstages 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. Okay. Backstage templates Mauro. I found that template is our application. I do think. Okay. Do you have the link? Okay. 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. Well, 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. What's this name for our app? Save B. Yeah. Do you like it? Yeah. I love it. The description of our app. I'd say that's name. That name is a B plus. Yeah. Yeah. Okay. And next step. Okay. We integrate our app with captain delivery platform. So we have a super secure captain API token. Okay. 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. Okay. Let's create. Okay. No. 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. Okay. So you can copy it. Repository. Save B2. Okay. Now it's publishing correctly. Yeah. Maybe Github is 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 an in 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 hop in all the stages. Okay. It's super easy. And just with one click we are delivering our save B app. Okay. Just some seconds. Okay. In testing. Okay. Let's try our URL. Not yet. Okay. But while it's creating our app. I go back in our. And go in save B2. Okay. And then I know there is this card. This is the overview of our hop in captain. Only in dev stage now for now. But I know there is this overview. Okay. Okay. Dev is succeed. And test is still running. Let's try to. Whoa. That was some hop. Yeah. It's so cool. We are the digits. Okay. Congrats. This is awesome to see you. Okay. But Luca 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. They have all is there ever the test is delivering. And the problem not yet. But I think. It will be. So fast. But okay. Okay. Let's wait. Some seconds. Okay. First is okay. So if I back in my. Platform ops. We can see the three stages. Offer our. Okay. We have shoes to use. Captain to delivery our hopper because it's really. Faster and easy. Normally. All the operation that I. Done with our template is. Maybe from the captain. CLI but. We have integrated our. With the captain API. And so we just. One click or one to click. We can delivery our. Application and. So this is. The second thing that I want to show you. We have. The. First. Major the big. One zero zero. And I show you how we can. Delivery the. Version two of our. Application. So I go back in. And. Okay. New delivery. I change. My. Version. This is. The stage is a dev. And this is the. Major with the. Tag. So delivery. Okay. I go back in captain. And. Just. Okay. This is the. Delivery of our. BG. So. Two. Second version of our application. Okay. I think. All the. Up the up the first lesson is. In devs test and production. I just. To the. CLI. Get namespaces. Okay. We have a tree. This is a one for that one for product one from test. And in every new space. 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. It's really fast to. Switch. Okay. So the. The captain. Tab. Shows. The. Second context. Because in captain. Every delivery is a context. And. We have. The test product. And. You can show. The details. Off. Every steps. Some information. In a test and product. The second. Delivery. Is. Is. Given from the previous. Context. But. Of. Dev. 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. In Japan. These. But. We need Italy. We have these. In Japan. These. And USA. These. Okay. Great. Just with the one click. We have delivery. Our application. For. For now. And sorry. Look. I have only one. Two. Images. I'm. Developing. The. Up. And. At 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 real time and less. In a time. Less than one hour. So. Was great. I think. Yes. Yes. In 40 minutes. We have. Two. Version of the. Up. And. With. Captain. We in the. Backstage. We. We have. All the tools that. Works. Very. Very cool. Really fantastic. I'm sure the. The stakeholders or B. 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 plug in. Is there a plug in for flux was one question that I saw or just do you all know of any plugins that are going to be added that y'all are excited about. Yeah. So. If you want to. Know what plugins we currently have. You can go to backstage that I owe there's the. Big big. Plugins button. And you can discover all the plugins we we have. I'm not aware of flux but. It just might be. You could also find it out by joining our. Discord channel and just shouting out if 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 projects so. Feel 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 how to contribute and how to put 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 is 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 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 all like many things in life nowadays it all comes down to a little bit of YAML 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 YAML 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 it will offer to create it automatically as well. So there's many many different ways and you could like maybe have a custom processor which will read some source or maybe even a script which will generate all this that's not up to me it's up to you. That's awesome it's 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 API but the API on that front what's the best way to go about finding an owner of a service say if like something we're down or I'm trying to take a look at an integration how would I how 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 done 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 on pager duty I could create an incident like that that functionality is in there as well provided by by the plug-in 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 do their 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 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 a lot of scene up for them let alone make sure that they are easily onboarded into increasingly difficult companies and another thing which is also quite complex is the infrastructure itself like well let's just not mention the CNCF landscape map that that alone says it all but if you imagine that you would work with only a selection of cloud native technologies within autonomous teams then you can imagine that those autonomous teams might have their own implementation even or their own way of setting the standards for their piece of platform 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 this will start within Spotify a few years back. It's music to my ears to hear that so that's really fantastic it's nice to be able to have that single place to look everything up because it is so difficult to rely on everyone to get their documentation together it's difficult to do especially for things that aren't Greenfield things that are being either onboarded 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 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 it 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 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 found helpful is the kind project the Kubernetes in Docker I know that Docker for Docker desktop and Rancher desktop there are 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 you know close to as soon as it's been released and and actually see what features are applicable and usable just a clarification we will delivery sorry release SES version is the 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 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 capability so definitely definitely recommend checking out that cloud offering if if y'all are curious about that awesome I have two more questions but if any of you out there in 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 it looked fine there what how how could could the promotion process works within the infrastructure configuration to you know bring things to production or we're kind of one environment on that front what what steps are involved sorry I lost the connection for just a second that I can you repeat the question sorry yeah no worries no worries so the integration environment that we started off with looked you know looked fine and was mostly straight forward to kind of when it comes to promoting to 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 just can delivery the dev stage but to captain API we can post a lot of settings 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 the 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 is based on the SLEI and SLAO files and we 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 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 the our stages so when I click sorry I click here the starting stage is deaf but captain delivery all the application in all the other stages so for example yeah 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 have 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 the second application is too slow to go in the production captain can monitor it and can stop the delivery for the all other stages excellent excellent definitely something to take a look at because that's nice to have those quality gates as we kind of go up to each of the different environments but wonderful wonderful well thank you so much everyone one more thing in captain there is there are a lot of tutorials and very very very very complete the tutorial and you can try the captain platform for the easiest environment so in today complex 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 so you might think it's well thank you yes this is the 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 environment so for example just for clarification in the system you can view these details of your application that's really fascinating I really appreciate you all coming out today because we are at time but it's really nice to see how all of these systems can integrate together and connect they are greater than the sum of all of their parts so 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 curious to check out all of the other things that you showed today I've spent more time on stage than but 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