 Well, thank you everyone for being here and thank you for making it an amazing cube con. So Before we jump into the topic is something really short. I want to jump into and first This really is about the community everything you see here like everyone that is working on all these projects It's at the bottom. We have people that are here So like first round of applause for everyone who is here who is part of the community and for everyone who is not here it was unable to attend and and and one other thing as well is that You'll see a photo of this actually make a point of it's pretty pretty soon But if you are also in need of like if you're not if you're feeling burnt out if you need help like please reach out to somebody Please look after yourself like we don't this is not a sprint It's a marathon and it's something that we want to make sure everyone is doing things They can not only for the best of the projects but also for the best of yourselves So make sure that you are also looking after yourself Drink lots of water get lots of sleep make sure that you're enjoying yourself and help make it a safe space Not only for yourself, but for others. So again, thank you So let's jump into it There's this concept that we have called the emergence and it's my merchant system. So it's when you have a System where the individual components that make up the system do not actually have the properties of the system as a whole They have unique behaviors that arise as part of that system The first example is is you have this and so you have a flood that comes along the ants all clustered together and now they Float and last I check ants don't tend to float very well and survive But in this scenario they gather together You also have all the pheromones that they put out so like the individual like how do they go off and gather and Act as a whole like they have entire behaviors. They're not actually encoded into the ants But when they get together they actually have a set of behaviors that they act like like in unison Also, I mentioned about self-care remember There's some ants at the bottom of these of these things that are actually latching on to the grass And so if you're feeling burnt out, you're probably one of those ants Pop up for air and ask for help and ask for somebody to help you with with that task. So You also have another famous example, which are the which are the cathedrals that you that you see here where you end up with a bunch of termites coming together and they build up these really amazing structure But specifically there's a few properties that an emergency system has Which is there's no global control There's not a single entity in the center that's like guiding everything and saying you're gonna do this and you're gonna do this And you're gonna do this and like mapping everything out There's also you couldn't even do it anyway because there's no global observability. You don't have the ability to see everything There are things going on in projects like I got a lot of visibility compared to many others And I can tell you I have just I can only see the tip of the iceberg I cannot see everything that is going on and so since there is no global observability Yet despite that we still have a convergence where that convergence occurs There's a given the structure that that arises out of it And so the system that has that structure behavior is not present in the individual individual components And yet we still have this amazing beautiful thing that comes up There's also an emergent structure. So those are major behaviors But you also have emergent structures where things get put together and welded and so in this scenario you have these These ice crystals that are formed and if you look at how water ends up working and how they all combine like you can have these type of structures arise and I also put this is a previous kubecon. I believe it was 2019 Europe and I want to say Barcelona but In this scenario we have a whole Economy of people like you are in here. You're part of a you're part of an economy You're part of a you're part of a organization of people who every group is acting in in different ways And yet we still have all of these amazing things that come out that has Priyanka that's right before affects seven million other people that people are depending upon and This is one of the central places where you can come together and be a part of that story and help Influence the direction again not control, but to influence And so how do we influence them? We start with open standards So open standards drive commoditization and we want to make it Make sure we have the definition here. So when we say commoditization, we don't mean commodification so commodification is where you're taking something that was like not sellable and you make it sellable in Terms of commoditization what we're looking at from this definition is Something that anyone can use that it's easy to access that you can just pick up and start using and so we want to focus specifically on open standards and Specifically on the word open so I know there's a lot of definitions that people tend to have I tend to use the OSI Definition of open and in terms of open source. It's something that is Accessible to everyone something that is approachable that like if I go in decide hey, I want to go in use HTTP There's no one there saying no you can't use HTTP Because it's a closed standard and this is super important because without these open standards are what drive The ability for people to consume But it also represents a place where we can where we can influence and And so as we move forward that open standards ends up enabling emergence like we have IP and how much stuff is built on top of IP We have HTTP how much stuff is built on top of HTTP in the in cloud native community We have things like the cube API. How does the cube API end up affecting your ability to to deploy or to or to build products on top of so with the So with open standards Like we part of what we should be looking at is how do we can we how can we make sure that we're putting into the properties that We're influencing the structure and then making structure Predictable on what the outcomes are likely to be knowing that we're not going to control everything It's that we shouldn't even try to control everything But we should try to put things in a way that are that are flexible enough so that people can go and do interesting things But we all converge back to a central to a central location so in And so in this scenario we're saying cloud native embraces open standards and if you want to know what it means to be cloud native I know we have the official term cloud native and all they talking about like tight loops and in feedback loops and similar But I would also argue that if the standards were not open if people were not free to come and use it We would not be here We'd be having a very small trade show at the most if we were lucky So the reason why we are so successful is because we have been working on building new and even though They're not technically standards by the official definition like there's no there's no board there and some of them and actually some of them do have boards now, but generally we start off with like well, let's go in and find something we can work on that we can all come together and Put a stake in the ground and say this is where we're going to start doesn't mean it gets ossified but but it's something that in time we can continue to build and and rally around so And so that means that if we were embracing open standards and we're thinking about how do we set things up so that everyone can access We get that diversity of people like diversity of ideas at that point We are embracing the concept of emergence and embracing the concept that we can actually come together We don't have to control everything So I can mention we are building standards like if you look at every single one of these things Even if you don't technically call it standards like there are protocols like you have a Kubernetes API This is like how can I go and deploy things? I have like the OCI that describes a variety of different things on how do I actually run in an image or how do I package a container image Things like C&I the control networking gRPC so like you have all of these different things that people are rallying around and They're all also opportunities that if they're not going to be perfect So part of it is these are some of the plays not the only ones This is a very small list of everything that we're doing but part of the challenge is Is learning what's out there so that you can then learn not only just what you're doing But you can learn from others who you're working with and you can tie it back into What you're doing for those for those standards and a really good example that I like to use in a scenario is with like I do a lot of work with spiffy and spiffy represents a path for how do we get identity where I've sped up my spiffy Identities for my workloads and another company might set up theirs. It gives the opportunity that I can Consume their identities and I don't have to know anything about their internal infrastructure We have something on the top in the same way that I don't have to know anything about your infrastructure if I'm using HTTP I can do a get to call on it and it'll act in the way It's supposed to which might be give me something or maybe it tells me you're not authorized But I'm gonna get something that's predictable so with things like spiffy, I'm able to get that identity Across across boundaries and I can start reasoning about other other entities and that has massive implications There's another thing to consider as well. It's not just about the technology like said it's about the people and How many people here used to run infrastructure before you adopt the Kubernetes like you're the person who has to run No, you're like a person is part of the runbook and they say okay John it's your turn to go and set up the script John Amy it's your turn to go in and set up the firewall and something goes wrong And so you have these really complex systems and again Thank you for Duffy for having this conversation with me because this is helped me set this up And so we part of what we have to look at is what are the human processes that we have? What are we changing it so everything that we put on our API's has an implication on What happens to in terms of our human processes both positive and negative because like I mentioned a lot of people have burnt themselves out Trying to manage the system because there's not enough of us here But at the same time it also provides a path towards like I can build an image and I can give you an image And if you want to run it, you there's There's nothing special you have to do in order to Understand how my image works at least from the infrastructure side like sure you from the application side You have to learn something about how my image works, but that doesn't say anything about I don't have to give you very much information because it's all in the specs It's all in the standards and we continue to improve on those so that everyone gains those those capabilities So many of these processes have been standardized through the through the Kubernetes API So please like whenever you're thinking about standards or you're thinking about like what how do I build the protocol out? Always think of the people I think about how people are going to consume it How how is this going to affect the people who are going to be up late at night? deploying deploying your code out I want to also make a prediction as well so today we now that we've covered emergence and how the how the entire Space is an immersion system and we're an emergent community We can also think about where are we going next and so if we take this as a as an initial standard one of the things one of the patterns that I'm saying is is We have a really clear definition on what an application is and that continues to become more generic and Kubernetes is an orchestrator. It is definitely one of the most popular ones. It is becoming commoditized We have turnkey solutions for it, but at the same time the applications themselves They have different places where you may want to run So there's a there are teams over here who I've been working with who have been working on 5g edge computing And they're trying to work out. How do I deploy my application? so that actually lives close to you like maybe you're working in Manufacturing and you're trying to control a robot the latency to your cloud is too much And so you have something close by or self-driving cars are often Another example you want something that's close by so that if you lose the link to your cloud environment You're you still have something operational that's close by so So we have these applications that eventually we will start to schedule have a manifest We'll have something we can describe What are the what are the requirements of the application then be able to deploy that application anywhere in the world based upon the Properties are there if you need a GPU you land you into an environment that has a GPU if you need if you're a wasm Base system then we have to make sure you we land you into into that correct area And there's a numerous places that today you can start to deploy against so not only when Kubernetes and Clouds and edge systems We're also seeing CDNs actually start starting to run workloads in their actual environments that land literally like Within some scenarios within the kilometer of where you're at depending on again depending on your location and so We have a whole set of protocols that have been serving us well here in the cloud native and I believe that we're able if we are careful as a community and thoughtful with how this is how this works I believe that we can take it to the next level and set it so that instead of just being bound Primarily to Kubernetes we can actually make this so that is something that is useful globally that when I then my infrastructure Things that I'm working on connects into your to your systems that we have those top-level APIs those top-level systems Of course an escape hatch because you sometimes need things that are not provided by those systems But if we can get most of our environments to think in that specific way with Uniform approaches or close uniform approaches to this and get down to better standardization. I think we can have something that's much bigger than just Kubernetes and cloud native and just what's within this community so With that This is the main point I want to make is that these standards that that we have they will continue to evolve and they Will allow us to to schedule Anywhere to to have that to have that interaction where we can then predict like we can then deploy to anywhere or any particular group Based upon the needs of the application rather than Rather than what was the system what infrastructure was that system designed for so with that? I want to thank everyone for for your time and Have have an amazing cube con