 Welcome to my lightning talk and I'm going to be very quick like my daughter with chocolate which is chocolate that's already done So I try also breeze through and then everybody can go to lunch. So empowering giants guide your enterprise very important and Who am I that I can speak about enterprises? Yes, my name is Engendiri We're currently at Pulumi, but before I wasn't big enterprises. I'm really talking German enterprises insurance company Retail and all the stuff. So it can't get slower and it can't get any enterprise here than there If I'm not working with infrastructures code stuff and cloud I'm thinking about the CNCF landscape once a day sometimes more often and this leads directly to my question Because seeing the CNCF landscape What do you think is the problem of? Traditional enterprises when it comes to the CNCF or for the landscape in cloud world not going to waste any seconds I show you some of the problems I identified here. So first of all complexity and fragmentation in the DevOps tools. I just give you one word Jenkins Okay, so Jenkins in the cloud. Is it possible? Yes. No, I like the talk yesterday at rejects where he said yes It's possible, but still we come with a tool set with a landscape existing landscape Which may not fit any more the requirements you have second problem In an enterprise evolving standards things go so quick if you look right you come back And there's a new tool a new project going on promising and coming back again tool overload What to use and we're talking here enterprises of a speed which is not like the unicorn companies who say hey I can quickly change the stack. I have with some energy and put on it here in an enterprise environment It's not possible to be that quick And then we come to blurring definitions and new paradigms I really had problems in my old place to explain people get ops. So we got the open shift We got several clusters and then we had to use GitOps so go now to your classical operations team or your developers who may upload the Jarvia and win SCP And now talk about something like GitOps. Wow, that was a fight. So yeah, that's me head HD of death So what could be a possibility and now we come to a statement here I shot this one also down as I promised. I'm going to breeze through It's literally cheating, you know, so enterprises love to see what other do and they wait and they're like let the others do it and see and Maybe learn from their experience so they meet sometimes on conference like here and say hey what you do and they're like Yeah, we tried XYZ it didn't work out because of and that's nice. So cheating is the thing So There's help there's help and I wish that this is some project which would be available Money many many many years before it would have saved me the gray hair and the loss I have currently so Kuno That's the project or that's the framework and I'm going to explain a little bit about this So what is the Kuno framework? So It helps you Strategic alignment and cloud management So it helps you to identify the OSS projects and focus on this one and say, okay This is something people selected and I can now completely align myself onto it Risk mitigation through collaboration. Yes, we can now work together and we can sit together and have different members inside the movement and can Share our operational knowledge our operational experience so this is something very very useful here and gives you the framework and The way to do this and of course everything is modular and community driven So I can take out the parts which may be fits and I get the feedback of the community So very very cool three points. Of course, there's always more but this is three points I really love about and Of course, you cannot have no principles So here also Kuno has also some principles which are very very important First of all open source first. That's that's really nice. So we have fear open source We're not going any more into any proprietary technology. We really here in the in the open source world It's community driven. So you have an ungoverned body You have a community around this which feedbacks and vice-versa. So that's one of the things and Kuno is here about tools and not practices It gives you the freedom to adapt the tool stays suggest inside your your enterprise Because you know the best how your company is working. So it says you hey, this is the tool But doesn't say to you you have to change also the sculpture like on the on the roller coaster You have to be that high to use this. No, no, no This is the tool look how you can embed this in your customer in your company because you know The best the culture It's powered by cuban needs and but not limited to it. So you can use any other orchestration tool, of course cuban needs is also here Set it, but again, you can change it and you can use anything else It's standardized for the infrastructure part, which is very important for an enterprise environment But gives you the customer business Customize ability to adapt this also for your needs so for the application developers for example and Last note, but least it's built to be shared. So whatever it's created there You you make it public and people can use this also and come back again to the learning effect. So yay That's great, but but but but there is no light without darkness. So What darkness is maybe the wrong word? There are some things with Kuno is not so Kuno is not only a unified control plane It delivers you the building blocks, but it's not a unified. It's not only a unified control plane and Kuno is not only a CI CD tool It helps you to integrate and to deliver your application, but it's not only a CI CD tool And yes, of course It's not only about giving you new technologies and shiny toys of it but it gives you a way to interact with them and to integrate them and Last but not least You are still responsible for the operation of the toolchain So it doesn't give you the way to say, okay, we take this over. No, you have still to spend the money You need to allocate the funds inside your company That's nice. Okay Then again lightning talk. I want to be very quick. So no time for it There is a reference architecture go to the site. It explains you some examples on AWS very important We working currently also to get a Pulumi into this and key takeaways Try Kuno. It helps you to build a robust IDP and It captures you some of the key technologies and helps you to share and understand complex Technologies and key technologies. Here's the link to the site very interesting Session feedback if you want to give anything meet me at the booth and I'm gone. Thank you