 Okay, I'm just going to kick this off myself. My name is Robert Hodges. I am a d. Okay ambassador I'm going to be doing a lightning talk called my database runs on Kubernetes. What's next? Well, the answer is data platforms This was originally supposed to be about a 30 minute talk. It's down to five So I'm just going to talk about one little teeny tiny aspect of building data platforms But I hope you'll find it an interesting one so Intro's make this I keep this under 10 seconds. I've been writing code for 52 years I've been on Kubernetes since 2018 My company does a lot of work with Kubernetes. We are service providers for click house run a cloud on it we wrote the click house operator and Are very very invested in in Kubernetes as a way of running analytic apps Let's talk about platforms So data platforms they are basically custom Stacks that solve specific business problems So a few years ago people used to talk about the modern data stack. The idea was hey, we'll just take a bunch of Sass services and we're going to weave them together. We're going to create data pipelines and storage and Ingest event processing all this stuff, but it's all going to be based on SAS services Well Forward eight years Kubernetes now makes it possible to just put that all in a single Kubernetes cluster Thanks to things like operators. Thanks to wide availability of open source components And so you get these stacks which are increasingly run in the cloud, of course So you've got the basic cloud infrastructure sort of undifferentiated compute storage and networking and then an entire stack on top of it running in Kubernetes and as you get to the top layers of the of the stack increasingly Customized the specific business problems so What are the issues in building this? Well, there are many but I think there's two that really stand out that become very interesting when You see a lot of people do this one is there's a huge array of tooling That's now available to do this and just to take a few examples You can use Kubernetes to set up Excuse me, you can use Terraform to set up Kubernetes and cloud resources, but on the other hand if you're deploying You know services within Kubernetes itself. You might use Argos CD There are many other tools as this picture shows and they overlap. So that's issue number one Issue number two is a little less obvious There's different types of knowledge required to build this stack in particular There's knowledge about clouds, which is specific to things like hey, do you understand how I am? works in Amazon or in Google all the way to Building applications sort of you know, do you understand how developer tools work to build pipelines build containers get them deployed and And bring the application up. So these are very very different types of knowledge and they they tend not to reside in the same person So what happens when you have technology that has this kind of complexity in this sort of tooling associated with it Well, if we look at history, it actually has an interest interesting effect on social structure This is a Norman Knight Circa take 1066 happily invading England what he actually is also is a complex expensive weapons system and These nights that those two properties led to changes in medieval society Around things like land ownership feudalism so on and so forth some of which are even visible today We get the same sort of thing in Kubernetes and the key thing that really stands out as you look across Platforms that people are building is you tend to have a platform function That is to say the folks who understand and run the the underlying platform the the Kubernetes and the And the underlying cloud resources and the apps team So those are the folks that actually build the app that rides on top of this and runs in Kubernetes So this can become a and this is surprisingly durable. I see this even in in startups with two people So Joe takes care of the cloud stuff Susan writes the app because it's just more efficient to split this up So the question is how can you how can you make this work best and not have these teams become bottlenecks for each other? or or or do things inefficiently because they're they're repeating work and One of the answers to this is that that we have found in our work is to pull Management particularly of resources as much into Kubernetes as possible Example don't use external load balancers. Just have a load balancing service inside Clickhouse. It's inside Kubernetes Another example pull the management of cloud resources into Kubernetes itself so people can do cloud operations Without leaving Kubernetes How does that work? Let me give you an example We are really big fans of EBS storage and GP3 storage has the ability to dial Bandwidth up and down at will the problem is you have to step outside of Kubernetes to do it So what we did was developed a controller that can read labels on your volume claims and Automatically adjust do the adjustments to EBS for you without you ever leaving Kubernetes so this is an example of a shim which allows your application team to do platform Management things without having to be cloud experts or necessarily even to know how it's done so This is the point I wanted to make about this talk is that when you're trying to build these These these stacks you have to allow for the fact that the that you have the apps team or the apps function They have a certain set of tools that they like to work with they have a certain Certain amount of domain knowledge you have the platform team that understands clouds has a certain set of tools that they prefer By building these shims and and you know sort of mechanisms like what I saw you can enable them to work productively together So Platforms are the next big thing for databases on Kubernetes This is how we take the databases which now run well and make them solve real problems at scale So what I like to invite you to do is if you are interested in this topic come contact me Let's talk about it. This is something we want to focus on in the data on Kubernetes group And I think also for many of us as vendors or as users. This is a problem. We want to solve together So thank you very much. You can get hold of me on LinkedIn or on the dok slack or right here I'm around all week. So thank you very much