 It's so great to be here. How many of you were at Ozcon a couple years back when we announced 1.0? Yeah, I mean it's just like amazing how this community's changed and so I'm very happy to be here today I could be Denise is just the most amazing journey I've your technical journey I've seen in my life and I think it's been as a result of this unique fusion of three things right what we've seen is a Community evolves this incredibly strong technically grounded Smart community that is invested in the same set of things and that's been very powerful the second thing we've seen is a set of End users start to emerge and actually be part of that community really make the technology their own be a part of it build their business around it and then the third piece has been the vendor ecosystem Organizations that are willing to make huge strategic bets in this technology now When I put this presentation together I wasn't looking to tell you what Kubernetes is gonna look like in a year's time. The community's gonna figure that out right? Like that's not that's not my job but what I was thinking about a lot was How do we as a community? What can we do that's really strategic to make sure it comes together well and? This is largely grounded in what I've seen over the last year as a startup guy I used to come here and say hey, I'm a product guy and I'm a startup guy These things three things are really obvious But when you start pulling them together it really tells a story about how important it is to hold communities together How important a number of attributes of communities are and I'd like to just sort of tell the story for you The first point here is develop a productivity really matters and I have Developed such a strong sense of this over the last year when working with some of the larger organizations I'm also starting to see this deep legitimacy around multicloud I always used to kind of like nod and smile when people said multicloud and never really believed it I'm starting to see it for reals now and Having spent a little bit of time with some of the world's larger technology companies I can tell you firsthand enterprise is complicated and these three things brought together Actually create some really interesting opportunities for the ecosystem some interesting challenges and so I want to talk through So let's start with the first one developer productivity matters We work with some organizations that hire tens of thousands of developers tens of thousands right and Some of these developers, you know spend their life Writing code and some of them spend their life waiting 90 days for a virtual machine to be provisioned. It's not a great experience Anything we can do even a 5% improvement in developer activity will have this proportional impact on those organizations When you think about it technology is changing the world technology is driving every business. What's driving technology? it's developers and Kubernetes has been the sea crystal to this new way of getting development Running forwards getting code into production and we tend to think about it a lot from as a sort of a developer framework and One of the things that I've really observed and I want to think about as we move this forwards is it's not just about development It's really about operations at the end of the day the thing that's holding those developers back is the operations team It's the operational drag. It's the thing that is Constantly gating their ability to produce and deliver great code And so when you start thinking about, you know, what has been driving developer activity particularly with that operations lens It's this idea of moving from static Code to living services and nothing embodies this more than the cloud, right? When you think about the cloud everything in the cloud is something as a service. So software is a service Kubernetes as a service Infrastructure as a service and what that means is I'm going to take a technology Whatever that technology is that I plan to deliver a service I'm going to wrap it up with a provisioning and integration API so that instead of me having to worry about Filing a ticket I can actually get an API to provision it for me and then Bundling a really powerful and capable operations team around it when you go to Amazon when you go to a zero when you go to Google you're not just buying basic infrastructure, you're not just buying Access to an open-source technology you're buying SRE right you're buying an operations team that's going to deal with this for you And there's nothing stopping you from bringing those practices into your own organization There's nothing stopping you from developing this incredibly rich way of thinking about delivering your software not just as Static dead things that you throw over the wall at the business every 90 days But as a living service with an expert operations team that is delivered to the entirety of your organization That is really powerful when you start making this step a lot of great things start to happen You can start looking at a world where you know I speak to so many of these organizations today that are living in the world of virtual machines and traditional infrastructure and They talk about resiliency. It's like, you know enterprises about resiliency. It's about how long to take to these things Before they go down. That's that's that's gonna impact my business And I look at them and I always say like you're focusing on the wrong thing You should be focusing on Recoverability how long to take you to get it back up when it goes down, right? Is there's a lot of different ways you can cut three nines That could be one second every thousand seconds where no one even notices an interruption in service It could be an entire business day once every three years where everyone really notices it That's the type of thing that really focusing on these sort of operational practices will get to you The relentless focus on automation, you know, removing toil out of the day-to-day life of an organization Getting to a point where your operations team is creating a gate a back pressure on your developers Doing things like SLA budgeting all of this is possible and Kubernetes really is the sea crystal for this It starts to deliver a framework where you can tease apart these various concerns, right now This here gives us a way to start thinking about and let's just start on the right there with the the cloud world You can look at the stack where organizations have started to create these expert operations functions and tease apart different services So you have one team that's racking and stacking VMs and delivering it as a service where you can request it with an API It's called infrastructure service The goodness that every major cloud provider out there is now delivering Kubernetes in the same way It's kind of creating this Goldilocks abstraction where you actually have a pretty harmonized story above it You have the cloud service for the cloud services that you know exist, you know potentially in the future Who knows maybe they'll be writing on Kubernetes. I suspect it probably will be in a lot of cases Or you can actually get a fully packaged application, you know in the form of SAS So that's that's the world of cloud Now you can do all of this yourself as well like why wouldn't you if you're a massive enterprise You could run an infrastructure operations team and have a dedicated near set of organizations You could introduce Kubernetes as this Goldilocks abstraction that creates a very clean abstraction above it You could take a lot of your services and deliver them in the same model the same metaphor as the cloud providers are delivering And you could create You know entire applications that are run that same way that separation of concerns is very powerful You get the same efficiencies that the cloud providers do or you can mix and match you can say hey You know what I'm just going to use the cloud providers Kubernetes as a service But I'm still going to start thinking about creating my own service operations teams. This becomes very powerful But to really light it up you start to need to have a set of common policies that span across these areas, right? If you're starting to mix and match I want to use my infrastructure a cloud providers infrastructure We use Kubernetes as its abstraction zone I still probably have security and governance policy that needs to exist need to think about that and in many ways That's why Kubernetes is so powerful like you could draw that line across that cluster ops area You can get a perfectly harmonized Solution that works well in both those environments and then you know create commonality above it so you can Flexibly pick where things run With that in mind It's worth mentioning that multi cloud is really happening and this is kind of one of the key ingredients That I think is really driving multi cloud and for multi cloud to happen We rarely need strong conformance, right? So I have to take a moment to congratulate every one of the major cloud providers out there Who have introduced Kubernetes as a service offerings, right? It's not just Kubernetes as a service offerings They've introduced upstream friendly Kubernetes as a service offerings. That's a very powerful thing and Part of the reason that we can feel good about that is that we're getting into a situation where it doesn't matter Who is delivering the communities? It doesn't matter how it is operated. It doesn't matter how it is provisioned The thing that matters is how it runs And for us to get to a point where we have high levels of assurance that Kubernetes is working exactly as it should Conformance really matters. We need to have the ability to attest that these clusters are semantically consistent that they have the same behavior and You know for that. This is why the CNCF Certified Kubernetes program is so important when you see that Kubernetes logo on someone's offering You can have a relatively high degree of assurance that it's working as it should And this leads us to some really good places It makes hybrid cloud wheel, right now you can say, hey I'm gonna run something on-prem and it could be something I construct myself It could be something from one of the distro providers and I'm gonna have something that's running in my public cloud that's delivered by my Favorite container as a service or Kubernetes as a service provider Now, how would I make sure that these things are semantically consistent? How would I be able to say that hey when I'm using my development tools They're gonna be able to focus on with these environments. The answer is you need to run the same test in both places, right? You need to be able to certify your on-prem piece So this is why we've been working with the community to create a technology like Sonoboy So you can actually package up and run these technologies and make sure that you're getting that semantic consistency across both of these environments Now, how do we take that one step further and get multicloud to be real? well Multicloud is interesting like I don't think about multicloud as being hey I want to take this application and I literally want to run in two clouds I mean there are some applications where you can if you're in a bank and you're running these big old Markovian Processes that are largely stateless and just have long, you know compute runtime cycles. Yes, it works great If your Bitcoin mining works great if you're doing anything that has massive amounts of data like nothing creates Gravity or inertia like data, right? And then we start to pull in service dependencies That's also gonna kind of hold you back. See you have to be judicious about that like multicloud To me means having the flexibility to pick which cloud I want to deploy my new service into it means being able to say Hey, I would like to run Listen different regions and I have my data sharded out by those regions and I can pick different cloud providers to make those sense of those regions But to really get there we need to get to a point where we have not just You know, there's a tested stable Narrative where everything is working all these other in these areas But you can also start to extend your governance risk management compliance policy and security Enforcement across all of those with a common abstraction across the top of them And that's why extensibility is going to become so important I'll give you an example of this, you know, this is one of the things that we were working on with our friends at Microsoft so, you know Brendan and that crew are good friends of ours and We've been looking at ways to help them You know inside the Azure Kubernetes service and one of the examples of that was hey backup restores heart, right? Like let's make sure that we have a great solution for that. And so they've been working with us to make sure that the ARC Technology provides a great backup recovery solution for them But being able to take your cluster state actually gives you a line on Multicloud that I think is going to be really exciting as we look to the future like this technology enables you to not just You know take your Cluster state and back it up and restore it there, but potentially restore it somewhere else now. We're not there yet on the persistent Volumes, you we there's a whole bunch of work that will need to be done to make sure that that's real But you can see the promise of this as a way to start moving things around inside clouds, you know directly So inside something like Microsoft's cloud or potentially between clouds or from on-prem to cloud and Kubernetes is the key to that whole thing Now Ken did a great job of talking about this earlier, and I think there's a couple of reasons why Extensibility is so important, right Enterprise is complicated When you start working with a really big organization, you know from our perspective and this is just a message to the community For folks that are sort of early on the journey. I'm sure the people that are late in the journey already have experienced this in in buckets There's a lot of unique needs right if you're deploying a Kubernetes cluster into an agapt environment There are a lot of unique needs if you're working with a regulated environment There are a lot of unique needs and it's difficult for one Organization one vendor one person to meet all of those needs So for us to succeed as a community We need to really think through where are those key Extensibility points, you know, like how do we make sure that Kubernetes remains extensible and open and there's been so much great work That's been delivered by the community over the last couple of Months even in terms of extensibility, but there's a lot more work that still needs to be done, you know we need to start thinking about how to formalize a lot of the interfaces that exist and how to Make sure that our conformance frameworks allow for these lines of extensibility Because when we get to that world when we start thinking about, you know, where this is all going, you know, how to start reasoning about Kubernetes across the multi-cloud verse when we start thinking about Hey, we have Different requirements from different workloads, you know, I'm doing when I'm serving web traffic I might have some relatively gnarly requirements around ingress and traffic shaping and load balancing When I'm running certain production workloads, maybe I want to add my own, you know, custom logging frameworks or monitoring Capabilities, I might have a CICD framework that I've built out that, you know It works across potentially other environments to not just Kubernetes And then I might need some securities capabilities like the security is a great example like Look at what Kubernetes is doing for security and think about the power that that brings right like you look at the work That aqua and stack rocks and twist lock are doing in the security space when you think about that increased line of visibility that containers provide There's some really cool stuff you can do, you know, you're now in a world where you have line of sight with The container abstraction that you can see every Linux school there You have line of sight if you deploy something like Istio or a service mesh into what's talking to what you can have a very strong sense of observed security exploits rather than You know having to kind of harden at the image level and When you think about Kubernetes as a control plane, you have an immediate source of remediation where you can start to just cut things off and shut them down There's a amazing amount of innovation that we're gonna start to see and in a place just like the security domain Like and I feel safe saying this I have no horse in the security race right now like as a vendor I'm just delighted to see the work that's being done there But for those organizations to be able to bring value to the community It's critical that they can plug into the environment that users are providing Not just that on-prem environment or that you know bespoke environment or that environment that organizations are running themselves But into a KS into EKS into GKE and so the formalization of these sorts of interfaces the formalization of extensibility the introduction of that into the conformance framework itself is Going to enable You the end user to get access to all kinds of awesome wonderful things that are being delivered in this open community and it's going to enable these organizations to innovate and and not be tied into a single provider and I think you know when I look to the kind of You know the future this coming year this to me stands out as one of the key things and You know I for one am really proud to be part of this community It's been such a such an amazing journey and I think that if we just hold together There's so much more that we can do you know Kubernetes is still very in it. You know, it's very much in its infancy We're still at a point where we haven't felt the full potential of it Not just as a way to solve some long-standing issues around the deployment and Management of software, but as a way to build new classes of distributed systems where Kubernetes is the core Development environment where it effectively emerges as the kernel for this new for this new world and to do that You know, we really need to solve the operations problems like it's not about zero ops anyone who says zero ops is selling something It's about ops power tools like ops specialization getting developers out of the operational game getting the SREs into it, right? It's about conformance like we currently have less than 30% of the formal APIs Stable API's covered by the Kubernetes conformance test, right? If we want this vision to be real we as a community need to put a whole bunch more resources into formalizing that Not just the API's that you use on a day-to-day basis to run your applications but the API's that you use to actually Integrate these extensible mechanisms that are creating massive value for you in the cross-cloud world and we need to rally around that and You know, we need to formalize our extensibility and I'm so excited by some of the stuff I'm seeing you know this there's been so much work that's been announced recently and great work. That's been done And so I'd like to close this out with you know a statement. I made a couple years ago at Ozcon when we Launched cncf and we announced Kubernetes 1.0 Think about Jevons paradox and this is really a message to you know everyone like When I don't know how many of you familiar with Jevons paradox? I've even heard of it. Okay, so Jevons paradox is this kind of economic theory where When you massively decrease the cost of something Well, sorry when you massively increase the efficiency of something you expect to see them on go down Things are going to consume less of it, right? You increase the efficiency of coal engines People expected to see coal consumption go down. It actually went completely the other way The increased efficiency created new uses of it it created new ways to consume it It drove the consumption of coal considerably And when we look at what we're doing here, it feels the same to me We're at a transition point if we can unlock the developer productivity So that those 10 20 30,000 developers that are working in enterprise organizations when those startup developers can do more work It's going to create Disproportional increase in the amount the quality and the capabilities of the technology we delivered If we can rally around conformance, it's going to create a far more efficient environment where those Developers can deliver those tools into an environment of their choice without having to rework it And as a result they will be producing more and they will be consuming more and that we're driving the success of this community more effectively And if we can formalize the extensibility and make sure that Kubernetes remains an open and accessible framework where we're not moving back into the world of mainframes where IBM is now called Amazon and You know, whatever that the case may be where where they are providing, you know A lot of value and then organizations can bring more value and actually solve problems We're going to see a much more efficient community. So thank you so much. It's been great chatting to you