Las Vegas 2018

Next Generation Infrastructure for Managers

Next Generation Infrastructure for Managers

JW

John Willis

Vice President of DevOps and Digital Practices, SJ Technologies

Transcript

00:00:05

Next generation infrastructure for managers. Um, so about four years ago, so I've been involved in this conference from day one and, and, uh, I think Jean asked me maybe four years ago to do like, uh, Docker for managers, right? It was about the time where everybody was incredibly confused about Docker, particularly managers, managers kind of is a, there's a lot of variation in there, what it means. But, but at time there was really a lot of confusion and that's fine, right? Everybody's kind of okay on the whole docker thing. And then, um, for at London, it was kind of, the conversation came up like Gene kept hearing about like service mesh and stuff like that. And he said, John, do you want to do, um, kind of very something similar, and I did it in London. And, uh, this is an updated version. So, uh, we'll go through it.

00:00:50

It's kind of a catchall. I got 30 minutes, it's like 29 minutes now to give you as much as I can tell you about, um, the broad stroke of what the ecosystem ecosystem looks like and what most people are thinking are the primitives that, um, that they're using. Um, that's me. Uh, if you don't know, if you know who I am, then you know all this. If you don't know who I am, I've done tons of startups, um, you know, um, the, probably, um, a lot of failed startups, but a couple of successes in the last five or six years. And, uh, one is a company I sold to Dell, and the other was, um, a company I created with a couple of friends called Socket Plane. We sold that to Docker. And I was a Docker for, um, uh, about two years almost, I guess.

00:01:32

And then, um, and I left. And now I'm with a company called SJ Technologies and doing really transformational consulting, which has been a lot of fun. I wrote the Handbook and all sorts. I'm on the selection committee, uh, the selection committee and whatnot. And, um, I went back and eventually authored, you know, if you saw a Snows thing, like he was IBM, right? It used to be a really cool thing called Red Books, right? And back in the day, like most, you probably never even heard of him, but back in the day it was a big deal. I'd forgotten it. I'd written seven red books, right? So, so I've written like 10 books. Um, this is the one I did this about a year ago. I think we're giving this out. So, um, today or tomorrow maybe, but it's just audio only. And me and Jean did it.

00:02:10

It's very geeky. 11 hours and I would say one audible credit, like to beg you to do it. But, um, but you're gonna get a free one this a or tomorrow afternoon. So I am working on two more projects, and this is the last shameless plug. I'm actually working with Shannon Leach, James Wickett, who we're speaking tomorrow. Do not miss that presentation. Uh, anytime you get to see Shannon Leach, you go to that presentation. She's incredible. Um, and, uh, I don't know when it's gonna be out, like hopefully in the next year. And then this is something even my close friends don't even know about, but at Cube Con, I'm doing something with Alan Shimmel from devops.com. We're calling it Digital anarchist. So think Netflix for geeks. So we will see, I don't know, we may like burn and crash all over the place, but could be very interesting.

00:02:53

So Cube con, alright, spoiler alert, right? Okay, you came here to learn about next generation platform. Uh, it's containers and Kubernetes. We're done. I'll see you later, right? <laugh>, let's go get a beer, right? Um, so, but you know, the thing is, it gets really interesting from here. And, and one of the things I, um, I'm not very organized as a person, but, but like, when I see things that are disorganized in our tech, in a way we talk about things, it drives me nuts, right? And so the first one, let's talk about Kubernetes for a second. I, I actually stole this from a Google presentation. Like, so Kubernetes is a container management system, and they said, oh, no, it's not. Uh, Kubernetes is a container management platform. Oh, it's actually not. Um, the truth is Kubernetes is really like this like kind of, um, kind of cyber incredible scale event loop, and we'll talk about the end.

00:03:43

So, so in general, Kubernetes is really just an application on this thing. So we'll talk a little more about that. So it's kind of like, if you know what it really is and where the future might be going, it kind of helps you a little bit. Um, that may sound a little obscure right now, but hopefully near the end it will make more sense. But here's the thing, right? So like four years ago when I like did the doc, doctor, manager, everybody's clear, good, we get it. Thanks. Right? Now it is the wild, wild west. It's a mess. It is incredibly messy. Um, it's a, um, and not even the technology side, it. So here's the thing. I go into clients and I say, what container, what type of container are you using? Notice I don't ask what Docker. They docker, like, they don't know me.

00:04:31

They're like, Docker, you idiot. I'm like, okay, what Docker? And they'll say the open source Docker. I'm like, well, respectfully, there's no such thing as an open source Docker anymore, huh? It's Moby. Okay, we'll talk about that later. Um, you know, then you get to like, okay, what now can I ask you again? What container system music? Oh, yeah, I just called our guy. It's basically, um, the, it's basically Docker community edition. Okay? That's the free one, right? Uh, is that how you're gonna run your bank strategy? Uh, probably not. What you gonna do? I don't know. We're gonna wait, see what Google does, right? Like, it's a, it's a mess, right? And then if you're OpenShift, like, I don't know if you are right now, but you will be cryo. And again, if these things don't make any sense to you, I'm gonna cover 'em all.

00:05:16

But the point is, and then the second question I ask is, what container orchestration are you using? Right? Kubernetes, you idiot. And I'm like, well, okay, hold on. Which Kubernetes, and there's a whole shit load of Kubernetes distributions, right? And it matters which one you might pick or use and where you're going, right? Um, and you know, so the, you know, when we talk about, and I guess what drives me the, probably the insane is when I see a presentation or somebody just talks about Docker is if it's a Frisbee or a Coke, right? And I guess in some sense, that's okay. And four years ago, that was really the only way you described the system. But now today, I think we have to be a little bit better in having a conversation. So what I'm gonna do in this presentation is cover really four categories.

00:06:02

I wanna talk a little about the foundations that are in place, um, basically OCI and the CNCF, um, and then we'll talk about the container ecosystem. And I'll try to put some names on it where we just don't say the word docker. We actually start, um, decoupling what, what it really means to run containers in a container ecosystem. And then I asked this in London, how many people know, uh, or have heard about the, the, the service mesh as it applies to Kubernetes? Okay? There was three, and I don't count John <laugh>, you don't count Buddy. Um, the, he counts a lot, but, uh, but the, and watch his presentation, uh, Wednesday. But, um, it's a very low number, right? Like, and this is really important stuff for you to know about. If you think you're going down this path of next generation, which today looks like it's cap Kubernetes, right?

00:06:50

The distro not sure. Um, and then like, if you don't know about that, what do you hear about the, the thing that really is what all the cool kids are working on right now, which is called, uh, Kubernetes, API extensibility? And I'll tell you, it's very nascent, but it could be some of the most important stuff we should be paying attention to right now. It could be, right? So I'm gonna give you a little bit of flavor, what that is and why it exists. So that's what we're doing. What's outta scope quickly is no introduction to containers, no insurance, Kubernetes, um, if you came here for that, like, there's just a gazillion of those online. Um, I can't talk about storage network and ecosystem systems. I got 22 minutes left. Um, I mean, not that they're not really important discussions, it's just like I, I've, you know, I'm gonna be a miracle if I can finish this thing on time, uh, uh, covering the other topics.

00:07:42

And then, um, the only gonna say is serverless is like, you got Lambda, you got this new thing called Native. Um, although it, that's another nascent, um, you know, I think it, it, I I get the sense of some of the people I talk to who I think are like way smarter than me, that what we have is serverless right now will be completely different in maybe three or five years. So that, that's why. So that doesn't mean don't go out and use Lambda because if for a digital property or something like that. But anyway, I'm already talking about it. We're not gonna talk about it. So the foundations, um, is really two that you need to know about. Um, uh, the OCI and really OCI is about, um, primarily about kind of the, um, the standards for container technology. Um, basically, um, the, probably the most important one there is run c for the most part that has become the standard.

00:08:29

So if you think what happened is Docker went ahead. So Linux containers had been in the, uh, in the kernel for quite a while. In fact, it was a collaboration IBM Google, and I forget who else. But, uh, and, um, and what Docker did, like their brilliance was, it was really hard to get it in a way that was usable unless you were like a geeky developer shop, like Heroku or somebody like that. And so what they did is they put an abstraction lxe, and then they, they actually kept building that extraction. Um, they had something called Lib container. And at some point they felt that this was very commodity and the industry was starting to split up on containers. So they donated, uh, what they, what's called run sea. So for the most part, people run run Sea, and the ownership of that is part of OCI.

00:09:11

There are some, you know, in our industry, if we don't argue, like, what are we doing, right? Like, yeah, like we, we love to argue about, especially when we try specing a foundation. But, but one of the big arguments about, uh, the image specification and all that, and that's actually starting to get some grounding where, um, there's still some downstream discussions between Red Hat and Docker about image, but ultimately everybody agreed that the foundation of images are gonna work a certain way. Um, so, um, and so the other project, oh shoot, I'm missing a slide. Darn. But anyway, that's okay. I thought I updated it, but it's not really an important slide. Um, this is CNCF, like, so the CNCF is very important here. Um, they're the primary, uh, stewards of Kubernetes. Um, they are Linux Foundation based, which is good. So I'm trying to compare like the mess of OpenStack, right?

00:10:00

The tragedy, the Titanic called OpenStack, right? Um, sorry if you're running OpenStack right now, um, the, um, and, and our we is this happening all over again? And for those part, I don't think it is, uh, because CNCF first, it's Linux Foundation based. I, I, I, you know, Linux Foundation, sorry. Yeah. And, um, I, you know, the people that are running this, are, they, they have their head together, it's, and they're doing some things like on patent control, and if you join, there's certain rules you have to play. So, so again, uh, follow this lot activity, very interesting stuff. Lot of training. So you got your Kubernetes and there's actually some, uh, interesting products, projects just since we're here, <laugh>, um, that you should know about. Um, and I'm not saying the other ones are not important, but, um, but container D and we'll talk about container D and, and why it exists.

00:10:46

And then, um, the, um, just dis uh, which one I, my glasses and on, um, um, why am I hate when I just getting old socks, everybody. So just giving you a heads, oh, Envoy, yes, of course, Envoy, we will talk heavily about Envoy, but the one, uh, I won't spend a whole lot of time on is Yeager. Um, and then, um, there's, uh, open Zipkin, um, there's two of 'em. I'm not sure why Zipkin isn't. This is distributed tracing. Like if you go in Greenfield, get your teeth into distributed tracing, I've got a couple of clients that have built head to toe composable data center infrastructures and everything is running Yeager. Like the stuff in the value you can get outta the distributed tracing is like off the chart. Um, so, and a ton of other projects. Alright, so that's the foundations again, we're, we're running through quick, right? Um, so the container ecosystem, right? This is the thing where I ask people like, you know, what are you running? They say, Docker, and then we have this kind of decoupling of a conversation. And so I, I'm saying like, if we wanna decouple the conversation, and we really should be talking about, um, container runtimes engines and orchestration, right? And, um, you know, if we wanna get it right, really not everything is docker and

00:11:52

You may actually not be running Docker. Um, so first the run times, basically I told you run c that was what was donated. I think most of the, um, most of the different distributions of, you know, like kind of the engines and whatnot are running run c there are some interesting, uh, run LX C is interesting. Um, it, it's actually from Alibaba. And what they did is abstracted run c uh, run V, which is actually, um, A KVM implementation. And, um, but the other thing they're trying to solve, which is interesting, this has been a kind of a thorn between Red Hat and Docker forever. I mean, the idea originally of a container was it's kind of a single process or single PID mindset, right? You, you literally start the container and the first process that's running is the application. And then those knuckleheads are at, I'm sorry, wait a minute.

00:12:40

Um, the, you know, wanted to put system D in there and it like, like, okay, I mean, I'm just kidding. I don't know what's best for, for your, so it's, but, but it's been a little bit of like, how do you mitigate, like should containers have kind of process control and stuff like that? And so one of the things that the Alibaba people did is they, they put a nice lightweight thing that kind of gives you best of both worlds. And I think that's kind of interesting. So, um, and then container engines. So, so like if I said it's all Kubernetes, then any discussion about running containers outside of Kubernetes is a moot point, right? Um, if you believe that, then the Kubernetes, it's interface for running containers is called, uh, container runtime interface to cry, CRI. And so under that, so you, um, basically the flavors of engines is container D.

00:13:31

So what Docker at some point wind up, um, contributing not only run sea, but they, they contributed their kind of engine, which is their demon and all this like, really good stuff, right? And so that became something that contributed to the CNCF. And so you have today, Docker and Google, GKE both run under container D um, but Red Hat has gone down and they're another path where they've created something called cryo, which is their own implementation. So you have OpenShift, you're most likely to be going down if you're not already into the cryo path, and that's kind of a convergence at the end of the day. Um, they all run containers and follow the container spec and they run run sea. So it's not the end of the world, except there is a little bit of divergence here. Um, so when we talk about Docker, what Docker really has is the open source upstream is something called Moby.

00:14:25

So what they did, um, is basically they wanted to protect the BA brand. It was somewhat like the fedora and, um, for, you know, red Hat and stuff like that, right? So they decided they were not gonna rip out all this open source contribution. So they basically took, what was GitHub? Docker. Docker and called it GitHub. Moby Moby. It was a ter. Does anybody from Docker the room? <laugh> good. I can really talk bad now. Um, I mean, it was a terrible idea. It was a terrible, terrible idea, but they did it anyway. And then they took the brand to proprietary. So basically you have non-open source, uh, engine enterprise and engine community. Um, it is the upstream, but like, I just did the, uh, check, I mean checking, like, you know, is this thing work? And nobody, the activity on Moby is not, I mean, it's existent because it is the upstream for, uh, for the Docker stuff, but, but the point is the only contributor, as far as I could tell of the Docker maintainers that worked for Docker, like in the past, it was like a gazillion people contributing to Docker.

00:15:26

What they absolutely did is like close the, the gate they put like the sewage canal in, in, uh, in there. And again, i I, I just don't like, that doesn't, like if we think about community and building and how we're doing things, it was a terrible idea. Um, the cloud ones just going through these quick, just like, you know, you don't know. Um, there are kind of as a service first, uh, based container AM Amazon has ECS, uh, Azure has a CS and Google has GK interesting about Google is you kind of get Kubernetes and the container thing together. They, they were doing that long before some of you were born <laugh>, no, uh, um, but, uh, the, uh, um, and so like by the time they were ready to make a service is like, we don't need a container service. Like it's, it's really just Kubernetes running these container things, um, uh, a CS, right?

00:16:14

If it's your stack. And then if you file some of the announcements, um, of where, uh, Google announced that Google next about the things they're gonna start putting on prem. So in general, um, there's this kind of migratory path to being able to run, uh, both of those as a services to a certain extent or some variant of that, um, on-Prem, you know, and, uh, we'll see where, uh, Amazon ends up in that, or, uh, so orchestration I said is Kubernetes. Uh, dock originally had something called Swarm, uh, another terrible idea <laugh>, uh, where they literally decided at one point they were to combine their engine and their orchestrator together, and then within, less than a year later, decided to go with Kubernetes anyway. Um, so actually what you do get in the Docker enterprise solution is you get a swarm and Kubernetes together, but there's really, um, no story for swarm in my opinion, although it was a great product, it just got s swallowed up.

00:17:10

And then you have Mesos Mesos Fear. Well, interesting. And there, there's a whole bunch, and I'll show you some buttons later, uh, when I go to some of the CNCF uh, projects. But, um, it's funny, Mesos Air, like a lot of the, the vendors out there, Docker or Mesosphere, um, they all were holding out like, nah, this Kubernetes thing's not real. This Kubernetes not found like one day, okay, we're all gonna support Kubernetes and Mesos. I think Meso might be the one of the last ones because, and apologies to anybody's meso sphere, um, if I'm using a little bit of literary lights, just, but they argued that, um, and this is important, they would argue they were arguing that, yeah, that's all great, but we're the only one who do stateful clustering containers. Well, by the way, that's probably the primary problem that service mesh solves today.

00:17:52

And certainly the, um, API gateway stuff. So I'll talk about that. So that's like, okay, we've lost. Um, and then the only thing I do wanna mention, this was not on my list, um, even in the beginning of the year, um, HashiCorp is just like that kid <laugh>, you know, I met him like, uh, 10, 8, 9 years ago. Uh, Mitchell, uh, Shimoda, um, like, so Nomad is an interesting story. One story is that, well, first off, it's incredibly easy to implement and it can run your containers just fine. It's very lightweight. Um, if you're doing like a femoral batch and you want build something, it's gonna go away. Do you really want to build a very complex Kubernetes cluster? That's one. And then recently, I was actually, it's kind of already public, but one of the guys I know that's building, uh, Samsung's version of Siri, the whole data center is built on Nomad Vault and Terraform, and it's completely composable.

00:18:48

And he cycles search by the hour. He can build a data center like a Siri, like data center in 30 minutes. So I'm like, okay, better start paying more attention to this thing called Nomad. 'cause the beauty is because Terraform is a great product, Vault's a great product, and if you wanna run those two really, well, guess who's the really cool solution? It's Nomad. Um, in general, I will stick with the Kubernetes and containers is where all the Mindshare is right now. I just think you might wanna put Nomad on your radar. Um, and then of, and then there, there's, uh, like, there's a lot of ways to, those are a couple of distributions. I, I'll, I'll list a whole much more in a minute, but there's a classic Kelsey High Tower, it's a blog article. It's called Kubernetes The Hard Way. Like, it's like you wanna really learn how Kubernetes work.

00:19:37

It's, uh, it's a, um, a GitHub project, but it, like some people tell me, I'll say what Kubernetes just shouldn't, like the hard way. Like we're just, we, you know, we, we get it from GitHub, we manage it, we build it like, you know, there's like, there's all sorts of risk reward discussions we can have about, you know, dis um, distributors Kubernetes, who add a lot of enterprise stuff, but some of it is actually really not open. And then others where you're gonna have to do a lot of work yourself, but you have a complete path to openness, right? There's a little bit of, um, little bit of mitigation there. Here's the kind of list of, uh, there's like 42, uh, certified Kubernetes from the CNCF perspective, but like, you can see 'em canonical. I mean, everybody's got one, uh, uh, pizza Hut I think has one, but, um, that was a joke.

00:20:22

Come on. Uh, you know, Docker, Google Heptio is interesting. They're some of the, the original developers of, um, of, um, Kubernetes. They, they call it kind of un distribution. It's an interesting thing to look at. Of course, you got me Fear Red Hat. Um, again, more so these little ones that I've kind of played with. So, um, not so much that, um, they're the best on the list, but they're ones I've, uh, and then orchestration, um, like people run Kubernetes. This is a service. You've got Amazon, EKS, Azure, and GKE on Google, right? Again, we're just kind of giving a landscape survey. So let's talk about service mesh, which I think like six people answered. Heard of this. I gotta go probably a little quicker now. Um, so the service mesh is, I mean, you know, it has broader definition, but is in, in the context today as we talk about Kubernetes, we talk about it as an infrastructure layer for service to service communication.

00:21:14

Um, it gives us the ability to lightweight proxies, um, uh, through deployment. But, um, but ultimately, um, what it does, it's basically a proxy. And I'll, I'll show you a little more detail here. But the idea is if you're gonna run these kind of, these, they're called pods if you don't know, but you'll run containers in a pod and they're ultimately clusters. Um, what you do is you put another container in there that is, is designed conceptually as something called a service mesh. Um, and then from there it sees all egress, um, ingress egress from that. And then in, in it, and there's rules and constructs that allow you to do observability monitoring, traffic control, load balancing, service discovery, resilience. And we'll see some of this here in a minute. And, um, and so it's based on a, um, a very software defined architecture. So if you know anything about software defined networking around, that's layer three.

00:22:09

Um, it has got a control plane data. Plane data plane is the packet. It's control plane is kind of how you abstract the intelligence outta those packets. Um, this is a layer seven. This is a proxy based, and it's, but it's got the same architecture, but it's at a layer seven. Um, and the data plane basically is, is really the proxy itself. And the control plane is kind of all the policy in the meta to make it work. Um, and oh, and, and this is where we, we introduced the word Istio. So I, I didn't, I, I wanted how many people have heard of Istio? Oh, so a lot more. That's interesting. Okay, I'm asking the question the wrong way. Still. Probably less than only a third of room if that. Um, so, so here's the deal. Um, there really, um, the way this is played out is there is, uh, open source technology that was developed by Lyft.

00:22:57

That was they, and they had a problem with scale, and they decided that nGenx couldn't solve their problem, and it wasn't written in a way they needed to run like containers and Kubernetes and all that stuff. So they wrote their own kind of proxy called Envoy. And so today, basically the, um, the data plane is this thing called Envoy. In fact, a Kup coupon. They actually have an Envoy day. It's, uh, it is, it is really where all the work is going on, like your, uh, the service discovery load balance and TLS termination, uh, circuit breaker has built in circuit breaker patterns, right? So it's already built in. Um, it actually got, has, um, some kind of, um, uh, deployment strategies like, uh, stage rollouts and, and like, you can actually augment it with like canary and stuff like that. It also does like fault injection and it's got chaos kind of kiss monkey ish things in it.

00:23:44

Um, and then on the right hand you have the control plane, which really is just all the policy. So at the end of the day, Envoy was this thing written by, um, Lyft. They didn't really create a gooey or a way to kind of manage it. Google basically defined distinct called Istio and Dig in a sense is a configuration management for Envoy. Although Engine X now is trying to create the, or already has their own version of a data plane proxy. Um, but right now Envoy is taking all the oxygen. Alright? So that's the th we just finished the first three subjects. Again, we're racing through a lot of stuff, right? Um, but the last piece, right is this is where all the cool kids are hanging out today, all right? Um, and it is actually sometimes the cool kids are hanging out someplace where you like, who cares?

00:24:27

And sometimes they're hanging out a place where we might actually want to care. And so I'll go through this reasonably quick. It's a very complex, it's very nascent, um, is a really small set of people that actually can do this right now. It's so complicated. But, but it might have incredible impact on how, if the theory is that Kubernetes might be the 10 year winner from a platform structure. And there's a lot of people that that kind of believe that now there's a big if there, so that we might be running all our kind of clusters for the next there, you know, some people kind of put like, maybe Kubernetes could be that abstraction on over the kernel that just may be part of our, our way. And in a world where everything changes three years, that does sound kind of silly, but I'm buying into it for now.

00:25:15

And if that's the case, then getting a jumpstart at least understanding where this stuff is going. And by the way, the, the people who are gonna give you the best intel on this are your vendors. 'cause they're all doing this right now. So you can actually get them, any of your vendors that are playing around the Kubernetes, you could pull them in and help you understand more of how this works. Um, 'cause they know and they're learning how to do it. Basically ap. So Joseph Jacks, uh, gene actually put a thing on him this morning. I didn't, it was kind of cool. He, he's doing an o uh, open source fund, but he's been heavily into Kubernetes system. And you just quote in the beginning this year, he said, uh, all complex for, delivered as a service or behind the firewall should be implemented as a set of Kubernetes, uh, API, extensions and controllers, radical efficiencies will bound.

00:25:57

Like, so his notion is like, if you're SAP or your workday or whatever, and the world is gonna be clusters on Kubernetes, then this is a, um, this is an event loop that you can sit on. And maybe you should say, if you're doing Greenfield development right now on some new project and you think you're gonna be on Kubernetes, this would be a nice time to do a little bit of investment on. I'm not telling you it works for you or it doesn't work for you. I am telling you that I, I have enough confidence that if you think Kubernetes is gonna be kind of in your ballpark as something that's gonna be around from a, and I think when we say next generation infrastructure, right now, most people, most people would tell you it's containers and Kubernetes, right? Um, so then the question is, should you get into this game way before anybody else is, right?

00:26:47

Maybe not be an expert, maybe not re-architect stuff, but literally just start like, um, some POCs and projects to do some research on it. So, um, the Kubernetes API basically, um, this, um, I'm gonna skip this slide because I wanna go to this. Basically, um, there's, the documentation is confusing as all get out, but basically there's, um, what you can call custom resources and, um, and aggregators, but custom resources are really the most important thing. Lemme see something. Make sure I, I must have scooted around with my slides to minutes. I wanted to, yeah, I, I, I miss, I'm missing a very important slide. Darn it. Let me, oh, there it is. Um, yeah, so custom resource and control. So this is, this is where you need the, the aggregator is interesting, but right now this is probably the most interesting. So you might hear 'em call CRDs, uh, custom resource definitions, basically when you wanna create your own.

00:27:41

So if you, I know I'm sounding confusing here. If you think about Kubernetes has some core resources like nodes and replica sets and, and, um, services and pods. And so really all you're doing is actually defining your own resource controllers, which is the execution logic for what you wanna do. And then the resource definition. So a really simple example might be you want a state full, uh, MySQL database in a cluster. So you might wanna create that as a custom resource and custom research. In fact, Oracle has already done this and has a sample. But, um, but here's why, because I, I told you earlier that Kubernetes is this thing that actually is much bigger than Kubernetes. It's basically an API that sits on a control loop that sees all egress and, um, basically all ingress and egress, inbound out, out traffic for everything that happens on a cluster in Kubernetes and at a millisecond level.

00:28:41

And it's Google saying it scales at Google scale. I mean, <laugh>, you know, um, and that I, if anything, I'm gonna run on there. I can get in a p and sit on event control event loop and be able to do anything I want from an operation observability, right? Like I, I, I hope some of you get the picture of like, I think go back to Joseph Jackson, radical of efficiencies a pound. I, I mean, I agree with him on this. Um, I will say it's very nascent. It changes very quickly. The documentation changes quite quickly. But, but it basically, because what you have then is, um, you have to create a custom resource. I talked about that. Um, these create the kind of custom rules and basically in events and what you want to do, do you wanna monitor, you wanna change the cluster, you wanna scale, you wanna auto scale change pods, oh geez, I want time.

00:29:28

I got a couple more seconds. But basically one of the primary benefits of doing this is giving you the ability to do stateful applications. And, um, and then here's are some of the, the examples that are out there, but there's a lot more. Um, there's also, if you wanna see all the community activity, um, going on here, it's just insane. You can list all the people that are actually pretty active in this custom resource thing. And the last thing I wanna say, which I'm gonna steal like about 30 seconds, is this is a movie from 96 6. It's actually a French, but it's, there's um, there's a subtitles called King of Hearts. Basically it's, uh, it's basically the metaphoric the, um, the inmates are running the asylum. So now I've told you Kubernetes and all that stuff is like the, the shit. I'll tell you right now, I'm scared to death that the people who are making all these decisions for industry might be the inmates in the asylum. They're young kids that are brilliant, that are moving incredibly fast. Things are changing really fast. So I don't know what the right answer is, but I do scare it does, like we, we need to kind of put the temperature gauge on and try to figure out where we, how do we run a bank when every three months there's a bunch of smart kids adding all these new extensions. Anyway, thank you so much. Um.