 I'm just here to have a little fun, speculate on the future, and kind of reflect on the past of Kubernetes, GitOps, and where we are today. I should take off my mask before I do that, though. There we go. So yeah, the future is declarative. I would say the future is now based on what I've seen today. But let's dive in and reflect. So I'm sure most of you are familiar with these logos. These Docker for sure, we all know and love them. We're all familiar with Kubernetes because it made it possible for us to orchestrate containers, and Docker made it possible to easily build them for app developers. So these were kind of a genesis set of technologies, I would say, to goddess where we are today. They basically made managing infrastructure and orchestrating containers accessible to the masses. You build your container using Docker or maybe Podman now. I'm a red hat, so I have to mention Podman. You design your, sorry, you define your desired state in a declarative fashion, which we all like because we're Argonauts here today. And then you apply it to your Kubernetes API server with kubectl. And then Kubernetes will reconcile that state and make sure you have the correct number of pods and the correct version of the pod or container image running. So it's kind of magic, right? It's kind of amazing you can just declare something in a text file or a YAML file, and it's suddenly available on three nodes in a cloud and highly available. So I think it's worth reflecting on that and how far we've come to get there. So I think we can all say we really, really like this. It gives us superpowers and it's kind of abstracted things in such a fantastic way that we can deploy more efficiently. But it's not all fun and games, right? You think, oh, I've Kubernetes, I've Argo, I've Git, I've Docker, I've all these amazing technologies. I'll have five nines of uptime, no downtime ever. But the reality is often not quite the case, right? So you think you're going to be the guy on the left, but actually you're going to right cowering and screaming about etcd and some of your Kubernetes nodes being down. And that's why companies like these came along and started offering managed Kubernetes, right? Kubernetes managing it is not your main job. Your main job is to deliver value to your customers and using Kubernetes is a means to an end. So using managed Kubernetes is probably something lots of people in this room do, but it still doesn't solve all your problems. There's tons of work to do. You have to configure, manage your deployments, do audits, rollback, logging, observability, all these other things that I couldn't fit on this slide. So we're all super busy and we need more help. And then Argo came along and helped with some of that, right? It helped with a lot of it, actually. So we're using Argo, Customize, Helm, all these other technologies to make sure our Kubernetes clusters are actually in the state we told them to be in, because we get sloppy, right? We run commands and we accidentally run them on prod and then everything's broken. So Kubernetes with Argo has helped avoid that drift. And we even went further, right? So we all know the default CRDs and Kubernetes are amazing, but we can do better. So we decided to extend Kubernetes with our own CRDs, right? So you can do that with Argo, right? You have the application CRD. You can do it with Kafka, the Strimsy operator. So obviously, again, I'm with Red Hat, so I have to mention the operator framework, which came from CoreOS. And it allows you to do fantastic things, like create your own custom controllers, run them on Kubernetes, and keep your application in a desired state, or do installs, which is a day one type operation, and then upgrades as part of your day two activities. So one of my favorite examples, actually, before I move on. So we enhanced CUBE. So yeah, CUBE by default is probably already like the one on the right, but we made it even bigger and better. So yeah, you can take something like a Kafka cluster, define it again in YAML, and suddenly you have a highly available Kafka cluster running across multiple nodes in your Kubernetes cluster. And you can change the settings, you know, the number of gigabytes assigned to those brokers, easily using declarative interface with YAML. And you can even go as far as managing off cluster resources now, using things like cross-plane. So maybe people are using cross-plane with Argo to manage, I don't know, S3 buckets, or SQSQs, or SNSQs, or the equivalent in whatever your preferred cloud vendors environment is. So we've gone from managing Kubernetes to managing things off of Kubernetes, and I think it's pretty amazing. So the question is what now? And I think, you know, we've seen a lot of today. So today we've seen a lot of what now, or now what, I think it's amazing seeing NUMA project, observability in AI tools. I think the future is pretty bright, looking for Argo in the community. And I would like to see GitOps becoming even more adopted. When I interact with cloud vendors, you know, I use a CLI. I don't use declarative fashion to interact with them often. I do it with my Kubernetes cluster on the vendor, but I use a CLI for the getting started piece. So maybe in the future, we'll use GitOps to actually interface directly with services that aren't just Kubernetes. I don't know, speculation. And that's it. I'm out of time. So I'll say thank you very much for listening, and I hope we've all had fun at ArgoCon. I know I did. Check out developers.redhat.com, and I'll talk to you all soon.