 Hi, this is Alexis Richardson from Weaveworks, also monadic on Twitter. Very happy to be talking to you today, GidOps, Kahn in the keynote. I want to talk about great moments in technology. If we look back in time, these things are very obvious. But sometimes they're less obvious in the present, aren't they? I think radar is a really good one. I'm not so sure about the teddy bear, but maybe so. But let's think about the present day. What great moments in tech can we think of? Well, I'm here today to talk a little bit about phones, actually, as well as GidOps in a minute. Let's have a look at this. This is the history of what appled it. Many of you probably know about this. And you can see a very obvious change in their financial fortunes, not long after the iPhone launched and also the app store there in 2008. That was a very significant moment for Apple and then the iPad as well. It was almost a new era for them. The iPhone moment to be called it. And the app store was just as important. That let you choose what apps to run, run them on your phone or multiple devices when it was supported as well. This made things just really easy and fun. And probably was responsible for the growth of Facebook and many other things that we take for granted today. But GidOps Kubernetes, they're enterprise software. So let's think about the iPhone while we ask the question, will the enterprise have its iPhone moment or its app store moment if you prefer? When will that be? I don't know if it's happened yet. Everything is still in the early stages, a bit like the web in the 90s. Enterprise, that's a funny word, isn't it? It crunches up enterprise IT and things like the IT crowd and all of the jokes. Have you tried turning it off and turning it on again as I frequently ask my say to my parents? But actually the irony here is, you know what? It's very hard to turn off enterprise software compared with say something app on the phone. It just keeps on running. If you can't turn it off, you may keep on paying for it. That's a bit annoying as well. Secondly, have you ever tried to upgrade a complex piece of enterprise software? It can take a very long time. And if it does happen, it may not happen in the way you expected. Do you get a chance to go back and do it again? Not necessarily. That's not great. Dependencies, question mark. So upgrades are tricky. So typically people don't delete enterprise software. It just goes into a kind of sedimentary layer. If you go into a big company, you might go in deep down into that layer and find things at the bottom. Or know that there's open stacks somewhere down there. So the three demons, if you want to have enterprise software, you can't stop it. You can't upgrade it. You can't delete it. That's pretty tricky. What if we could have a better world? Now, I'm not saying this is true of all enterprise software, but let's compare it with the phone. Come on. Much easier to install, which means concepts like migration across devices is there. Simple life cycle we can understand. We can stop apps whenever we want to. We can delete them, remove them from our lives. And they can be kept up to date automatically. Or you can have it on gateways to say, hey, do you want this patch? And what's really nice is the app store model. You've got this concept of a group of people who are certifying and checking verifying changes for you before you get sent applications that you might want to install or not. They'll certify those changes. And therefore you are happy. You trust them to give you only the things that you want or need and not do anything damaging or insecure. Very, very important. So could that be true in enterprise? And I'm an optimist. Cautiously optimistic. Panda says, perhaps we could do this with Kubernetes and GitOps. First thing is Kubernetes does actually serve apps. This is an app server. It's not a cloud. It doesn't do multi-tenancy very nicely on-prem. It's much better if you have lots of clusters, lots of applications in lots of places. Now, people think that's complicated to manage, and we're getting better at that. But it is much more like an app server than a cloud. And it's also something you can customize, which is really powerful. And it runs everywhere. Look at these vendors. We've got Google and Fast, Azure, Arc, Amazon, EKS, anywhere, VMware, TNT, and others running on-prem and in the cloud and in the edge. So I can have Kubernetes apps on any of these clusters, wherever I like. That's a bit closer to a phone world. Standard API is probably one of the main reasons that Kubernetes is like the Linux of its era. It's going to be around for a while. And the cluster API in particular is a new standard for managing clusters declaratively, which means that you can treat whole fleets of clusters as just a set of declarations and orchestrate them to correct state. Using GitOps, of course. And that, in turn, is that if you've got clusters from different vendors, like an Amazon, VMware cluster and an open source cluster from QBDM or something, they all support CAPI today. So you can manage them for a single point using your own tool that speaks CAPI, or a vendor tool. One tool to rule them all, or one tool to do them all at least, is much more useful than having lots and lots of different incompatible vendors. And then speed, you know, getting a cluster booted up is getting really quick now. Once it's fast enough, and I was talking today to a colleague who's done a two-minute boot on metal, once it's fast enough, it starts to become part of an application experience, as we automate and simplify Kubernetes better, lower the cost of operating it, then this will just become invisible, dial tone infrastructure, which is great perhaps. And look, Code Spaces shows in Amazon Lambda as well, how quick you can be. If you've got warm environments, you can get things down to seconds, that's incredible. That is the future. People will be able to start and stop environments, applications, clusters and stacks in the time they need. Operations, the missing piece always left to last. GitHub solves this, provides a mechanism to deploy, update, manage and operate changes and applications and hold clusters through CAPI and fleets through CAPI and using tools like Flux to do apps and services and Flagger for rollouts. All these things, whole stack, a full stack solution can be done using GitOps, using your choice of Git and CI tools. You pick which ones you want, GitHub actions, GitLab, you know, runners, et cetera. GitOps is something that we can use in very advanced cases like policy management for fleets, progressive delivery, dealing with complex workflows or new applications or very simply day zero, just deploy my app, please. Will just start me a cluster and then update it, please. Thank you very much. So GitOps is both for beginners and advanced users, just like apps. One of those new advanced cases is platformers code. So unlike typical consumers, enterprises want to have their own customised app developments. They don't want to have just apps out of the box like Salesforce and write their own. That's why they have large numbers of developers working for them who then need to operate these things. So that's a difference. Can we manage that in the iPhone to the phone style world? I think we can. If we have a way of describing and managing, patching and updating these platforms, which I just add on to the clusters like Prometheus, Helm, Fluent D, et cetera, et cetera, in a single way using things like profiles or application management tools. There's actually a bunch of different ways of doing this. We've worked with our profiles. It's a way of capturing groups of features. And the other thing about platforms is that you can embed policy into them so that you can prevent people from doing the wrong thing or make sure they do the right thing. Don't accidentally use the wrong password, for example. And so let's look back at that app model and compare it with what it gives us in the enterprise now. Gosh, we can have clusters that we can start and stop where we want to because of GitOps, we can turn things off and we can restart an identical cluster wherever we want to because GitOps lets us manage whole stacks correctly based on the description in Git. Certification changes slightly instead of having the app store to instead of finding our apps and enterprise platform ops team will certify them for us and the policies and the verified operations tools for monitoring observability that we might want to use. But we can do customized apps in a way that suits the app world. We get updates, again, probably going to want to permit the updates to come through don't necessarily want to automate everything. But by and large, what you can see here is we're getting much closer to an app store type of world. That's the incredible benefits and simplicity of Kubernetes and GitOps coming together for you for any cloud, any apps on any Kubernetes anywhere. So you must help us make this world happen. You must start your journey today using GitOps. We've GitOps is a good way to start. Let's not be dinosaurs. Let's be in a new simple, simple world of applications like an app store world. And I hope you're part of making that happen. And I hope we can help you make that happen too. Thank you for listening today.