 Thank you, everyone. Always wonderful to start with an applause. So that's always great. Yeah, well, anime taught me about communities, development, and tech careers. Very excited for this session, and amazing to see so many people, particularly on Friday. So really great to see so many people. So here is the Venn diagram. I think it's kind of easy to understand. But yeah, if you are an anime and communities fan and you both know both, then very much welcome. You are right there on this sweet spot. You are doing great. Thank you so much for attending. This session is for you very much, I think. If you know communities, but you don't know anime at all, then you will likely learn a lot about anime. So welcome and enjoy. If you know anime but you're new to communities, then you will definitely learn about communities. So that's really great as well. Welcome to you as well. And if you don't know either one, so if you know nothing about communities and you know nothing about anime, then you might be a tad bit confused throughout the whole session. But maybe you will learn something as well. So it's all right as well. But that's the kind of audience here, hopefully. So who am I? I'm Annie. I am a senior product marketing manager at Kamunda, as just mentioned. It's a end-to-end process orchestration and automation company, very developer friendly. But yeah, I'm also a CNCF ambassador, as well as an Azure MVP. And I am a Kubernetes and CNCF meetup co-organizer for Finland for almost five years now, as well as I coach early-stage startups. And then I also co-host a cloud gossip podcast you can find from there. So this is the usual slide that I do in conferences every time. But now I do want to obviously add that yes, I'm a huge fan of anime as well as manga and all of the kind of things that come with that. And maybe as a kind of mark there, I stopped counting how many animas, like how many different animas I've watched at the 150 mark. So after that, I was like, okay, it doesn't matter anymore. Let's just keep watching and it's all good. So I can definitely say that I have clearly over 10,000 hours that's the expert amount, I guess. And so it's all nice. Yeah. So what is this session? It's maybe a bit of a special or order session in KubeCon for sure. But we are in the 101 track. So this will be kind of basics of communities. We'll be portion of the session taking you through what's those kind of things. And then it's also relaxed, fun take on things. So it's not, this is not a very super serious session, not at all to be honest. So that's the kind of expectation management here. And as a maybe a mini morning, there's gonna be gifs. So there's gonna be a lot of flashing maybe sometimes, but none of it will be full screen. So no worries at all. It will be hopefully tasteful. Yeah. Then the agenda for today introduction going on strong right now, really nice. And then we're gonna move to battle illustrated anime fans guide to Kubernetes. And the spirit of the hippies, very well illustrated guide to Kubernetes essentially. And then we are moving to Kubernetes components in anime fashion. And then we have 10 lessons learned from anime with one bonus lesson in the end as well. So that's the agenda for today. And now done with introduction. We're doing well perfectly. And then we're gonna move to battle illustrated anime fans guide to Kubernetes. So if you are a aspiring anime hero, the main character and so forth, you are all alone in the world or maybe not alone. You're surrounded, but alone. You are starting your journey. You probably need a lot of learning. You need a lot of leveling up. You're just getting started. It's a scary world around you. There's a lot of things happening, but you're just looking for a home, a place to call your own. There might be a lot of people in the anime world who are like this. For example, Naruto started off as a very misunderstood character in his own place. There was a lot of things around him, but definitely he did not feel at home or at ease at his own place. There are other examples. For example, Sena from Eye Shield 21, bullied in his own school, trying to find his place in the world and kind of surrounded by a lot of things, but not truly at ease either. There are other examples, obviously, as well. There's Shinzi from Neon Genesis Evangelion, as well or plenty of others who might have had big turbulences in their life. They are going through a lot of different things, a lot of things surrounding them, but they still don't feel quite where they should be. So, what does this all? What does this story mean in the Kubernetes context then? If you're wondering, well, this is actually quite close to how, for example, an application would feel like if it was not in a container. So, it would be in an environment. It would be feeling a bit kind of surrounded by a lot of things, attract and so forth, and it would need a place to call its own. For example, it would be a PHP app that might include web server, readable, file system, PHP engine itself, so it has an environment and so forth, but it's not at ease in its own environment, such as the main characters here are as well. So, how do we fix this? How do we get to the next place? Well, hopefully, there's gonna be an amazing Shinobi school, ninja school that reaches out to you and gets you started on a curriculum there, or maybe you start playing American football and you really find your people there, or you find a big, big mecha to pilot and get started on that journey yourself. So, really, these are a chance of a lifetime, really great things that will improve your standing a lot. So, this is what a container would be for you if you would be in the Kubernetes world and not in the animal world itself. So, container provides an isolated context where the app and together with this environment can actually run in peace. And isolated containers often need to be, though, managed and connected to the outside world, so there's a bunch of challenges come in from there, so it is not yet the perfect location yet for our main character or our application. So, then, we got to find something else. We have got to connect to a bigger world, connect to other things, connect to a team and so forth. So, as you're eventually practicing your skills, you're moving forward, you're learning more different shinobi skills, you're learning about paleo-thingy mecha, you are going forward in the catching footballs, getting stronger, faster and so forth. You move on and you work together and you are starting to become a part of a community that helps you around there, which is when you then, your container, you become orchestrated in Kubernetes there. So, it is, Kubernetes is then a project led by CNCF, KubeCon, very much, probably a lot of you have, all of you have heard about Kubernetes by this point of the week for sure. So, it is a way to focus on building a robust platform for running thousands of containers in production. So, it is the next step in your journey and this is the new home that you will start to build for yourself while you are in your main character, anime hero journey. Then, next up, you learn more skills and you need to name them, so obviously you're gonna start having a skill, then you call it out, you might yell bankai or any of one of these things to kind of label things for sure as well. Another part of it would be that in your anime journey, you would also find a role within that team that you have found for yourself, so such as Sakura here, and part of team Kakahashi would have become, starting to become a medic, find their own role and give a label to it and so forth. So, this is obviously in the Kubernetes world, it's labels. So, Kubernetes uses labels as name tags to identify things and it can carry these based on these labels and they are labels are open-ended and you can use them to identify roles and stability and a lot of important attributes as well. So, as in anime world, with the naming of Mooms, Mooms naming of different team characters to have a role in Kubernetes, labels are very important as well. Then, as you progress further, you hone your team skills further, you get to even more together and then you find yourself in a pot essentially. And in a Kubernetes world, pot represents the runnable unit of work that you usually have. It usually has a single container inside of pot but there are cases where you might have more inside the same pot as well. So, pots are the smallest deployable units in computing and you can create and manage in Kubernetes. So, as is this little Shinobi unit here, it is a small unit that can be deployed out there, go for it, conquer the world. But there are other things obviously as well but before we get to that, we can go and discuss about, okay, so what kind of moves will you learn? What kind of moves are important for a Shinobi to learn and while they are learning about, well, obviously cloning techniques. You need to start cloning yourself very effectively to learn how to battle all of the important villains and foes that you need to take on, which is then obviously in the Kubernetes world, let replica sets. So, replica sets provide clone, you can clone yourself and you can demand any number of times on demand, which is essentially what Naruto does as well. Very interesting in my opinion. So, replica sets provide logic for scaling the pot up and down and it can be used for rolling deploys as well. And its purpose is to maintain a stable set of replica pots running at any given time. And as such, it's often used to guarantee the availability of a specified number of identical pots, as you can see in the image Naruto is doing as well. So, all throughout this journey you have now learned a lot. You have some skills, you know how to clone yourself. It's looking quite nice. You have your small team. It's all working really well. Well, what about the bigger picture? You need to connect to a lot of other things as well. So, then you need services, which would be the grander village, other teams around you. You really need to kind of, you know, identify yourself and to be able to identify other teams in your vicinity so that you can switch and information and know more about it. Which then in the Kubernetes world would be services. So, which services you can discover others and they can discover you. So, it really goes to the Kubernetes network model. So, every pod gets its own IP address as well. And this means that you do not need to explicitly create links between pods and you almost never need to deal with mapping container ports to host ports as well. So, you become part of the bigger world. So, you have now, you have a team. You're working with a team. You're connected to the bigger world as well. You know, cloning skills. It's all looking very fine for you. Then, what do you do when you start to have a lot of different things? You're getting more gear. You're getting more information. Then, you need storage. And therefore, you need volumes to store everything that you have. So, all the gear that you get, all of the other things that you encounter along your journey. Because when you become a hero, you obviously get a lot more weapons, skills, and so forth, as you can see here. So, in the Kubernetes world, this would be volume. So, containers can access and store information, application and the volume. And from the application perspective, the volume appears as part of the local file system. And volumes can be packed by a lot of different storage backends as well. Then, while you are in this journey, you're now, you have your storage. You have your skills. You have your team. You have your grander picture. Then, you will need to maybe, things start to be a bit hectic. You feel a bit lost again. Even though that you have all of these great things around you, then you obviously need namespaces to have a bit more privacy and peace in your find. You maybe start meditating. You maybe start figuring out, okay, what's my place in the world? And so forth, to continue a dialy battle and even more effectively. So, namespaces in communities function as a grouping mechanism inside communities and replicas its volumes and everything can be easily calibrated together with the namespace. So, when you have a lot of different egos in an anime team that would be clashing towards you, such as Naruto and Sasuke, for example, would be with these kind of mechanisms, you can help this and not be battling internally constantly. For example, in the animal world and in the communities world, obviously, namespaces help with that as well. So, after all of this, now your badly illustrated anime guidance guide to communities is over and you are ready to rock and roll and become the Shinobi that you have always meant to be, as you can see here as well. Yeah, then, now that we're done with the badly illustrated anime fans guide to communities, we can move to communities components, quick guide to them. So, here is a architecture image here and as you can see here, the communities cluster consists of set of worker machines called nodes and they have contrainerized applications inside of them and then you have the worker nodes that host the pots that are the components of the application workload. So, now the control plane is a lot leaner and not as bulky in a way, but then at the same time, the nodes to the most of the work but the control plane is the one that controls all of the others. So, then in the animal world, it would look something like this. You have Kakahashi controlling the team, telling the little nodes, aka Naruto Sasuke and Sakura, telling them what to do and what to do in the next step as well. So, this is one example of how this would look like in the world and there's a bonus there as well. There's a Hokka key in there in the cloud API provider point because then it's giving even higher level of instructions from there. So, this is one part of it, but if you put it into another part, we would get death notes and we have the mastermind, L, controlling all the different Japanese task force members and I think this example is particularly fitting because L itself is a very much mastermind behind everything, telling all the others to do a lot of the kind of more bulky, heavy listing for sure. Now, this analogy doesn't maybe work for all cases because I think for the straw hats, you can technically say that Luffy is in control because he is the captain, but is he really? Most of the time, probably not. So, it doesn't always hold up, that's for sure. Yeah, but those are the communities components in Anywhere World handled briefly there. So, then we get to 10 lessons learned from Anime. Lesson number one, importance of a team. So, as always, from one piece to Naruto, we've talked about the team a lot here today. There is from Naruto to one piece to the engine is Evangelion. There's always a really overarching team, the team that makes what makes you succeed and it's what will kind of get you to the next level, particularly one piece, for example, the sum of the people alone is not as strong as them together, working towards a common goal. And as a really important lesson there, everyone has a role to play within the team and it's really good that everyone has a specified role as well. And the same really apply to Kubernetes and tech world in general, if you're in an engineering team, for example, it makes sense to have your own role, but also everyone should be playing together really nicely and complimenting each other and working together to build really great applications and infrastructure. So, what's the next level from this basic team? Obviously, if you can, you could combine yourself into a one major thing that you're kind of really becoming together and taking it to the next level, becoming essentially one big mecha where you're combining everything together. Now, what would be the communities world or technology world equivalent of this? Well, it would likely be this. So, if you have this long list of things that recorders need from you, this would definitely be something that would be the combining mecha of the communities and tech world for sure. Hard to find if it was, if someone had all of these skills as a full stack developer, pretty much a unicorn for sure. Yeah. Then, next up, we have, there's always going to be characters and people around you with mysterious characters with dark past. And Sasuke here is a great example of that. He's a bit emo, maybe a bit mysterious, maybe mopes in a corner a bit, never smiled, a bit cold hearted and doesn't really say that much, but has a lot to leverage from his past as well because all of those hardship has taught them a lot and now they can kind of leverage that, but they are a bit moody and they are kind of a bit their own thing. There's probably a lot of different people in development teams with this kind of nature or depends on personalities as well, but I think one great example of people with a lot of dark mysterious past and a lot to give at the same time would be, for example, mainframe coders. They probably are back there in the room telling stories, but yeah, it's a great position to be in it. Yeah. So then, lesson three, self-development. So with any anime fights, you always have, well, even a fight or multiple fights, if you're trying to beat a big villain, you'll end up, inevitably, you need to get new skills, you need to scale up, you need to get a lot of new skills fast. Essentially, you need to go quite often to literal or metaphorical cave and just level up as fast as you can and come out of there and get moving. And really, these kind of things are really great and lead to a lot of great triumphant moments in anime, for example, but I think also there's a lot of great examples in Bleach or in Dragon Ball and so forth. And this obviously applies really well to tech careers in general and Kubernetes world as well. So, what would be the Kubernetes or technology world equivalent of going to a cave and really skilling yourself up and coming out? Well, for example, convincing your manager to get you a cube con ticket, coming here, leveling yourself up and emerging a completely new person with so many new skills and knowledge that you're gonna then bow everyone with all of your skills. Another thing would be, for example, if you get a Lean Foundation or ZNCF Foundation certification, so then you're again going somewhere, training yourself and emerging as a new person with new skills, and particularly in anime world, usually when you come out of that cave, you come out with fancy new weapons, badges, outfits. So, what would be better than having a certification badge in your LinkedIn profile, for example? It's essentially the same thing as Bunkai or any of these fancy acts, yeah. Then, next up we have, you need to take time to relax. And this image here is a bit too giving it away because there's the very infamous beach episode, always that comes up at some point. So, it's, I think, a great lesson to learn to take time for yourself, have holiday, have breaks, because it's the world conquering anime heroes of unparalleled scale and skills. They need to take a time off, go to the beach, play some volleyball, do some errands. Then you definitely need to as well. So, it's always good to remember. And I think another great comparison here would be a feature freeze. So, you have to pay back technical debt and then you can't advance the plot line, aka develop new features during that time. So, it's all connected there. Then, after you have taken that vacation, you're taking the holiday, you're ready to get back to work, either as an anime hero or as a developer, then you always need to remember to be prepared to get ready to take action and obviously monitor your surrounding as well, which then might lead you to jumping out of your school window to take action immediately when the monsters get near your high school or in the other area that you have. And obviously, in the tech world, this would particularly be on the importance of monitoring as well as having visibility into your cluster, for example. And most importantly, in the terms of this image, is reacting to that action as well. So, it's not that you just get information that, okay, there's an issue as a anime hero would get, that you know there's a monster nearby, you also have to take action, fast action, you have to jump out and you have to get going. Then, next up, we have the importance of decimation. This is a bit connected to the labels part as well in the anime world because I think what would be better documentation? You know, what's the priorities for documentation? You need to tell your team members what you're doing and you need to provide a historical context of what you're doing. Well, what would be better than yelling every single move that you do out loud? Everyone knows exactly what you're doing. There's no questions about what's happening and why. It's maybe a bit of a weird thing that the villains don't realize this, but luckily there's no villains in the engineering team rooms and so forth. So, yelling your moves out loud is only beneficial for everyone. So, importance of documentation is really highlighted in anime world for sure. And I think in the development world and the communities world, we are no stranger to enduring in long fights and neither is any Dragon Ball Z character either. So, you really need to brace yourself for longer fights and have the marathon endurance to really continue working together as well as fighting all of the villains or creating your clusters and so forth. And actually, I think interestingly, replica sets really apply here as well because you might need to have new people coming into the fights as well occasionally. So, you need to switch people between fights as well if they are very long. Yeah, and after you have now, you have everything working really nicely and you have attended the KubeCon and you're like, okay, there's a lot of things that I can take home and then you start piling up more and more and more different CNCF projects into your environment then you might accidentally become the monster that you despise if you end up having way too much complexity. It becomes hard to manage. You become overcome with everything, for example, if you end up with multiple service meshes running and it all becomes just a tad bit too much as far as confusion and complexity goes. So, all of the times when a lot of characters were sure from Dragon Ball Z to Bleach to Naruto have been taken over by their dark side, this is something that we should divide. There's obviously, luckily, you can add more complexity by adding more projects that help you with that size, such as Mechery and so forth, yeah. Then, next up we have the fundamental, I think, principle of cloud native as well as fundamental principle of communities that's very well-present in classical animas as well, which is ridiculous power scaling because you have these scenes where it's over 9,000, it's getting crazy, so for sure, I think we've all had our moments of these when we are thinking about our infinite scaling and all of the tropes that come with that, yeah. Then, we have one lesson left and one bonus lesson left and the next one is, I think, very important at least to me personally, which is always have a snack at hand. I get very hangry and I think all the anime characters are very hangry as well or very, very weak if they don't eat, so remember to eat, remember to keep your energy up, drink water and so forth and I think this is another great lesson that one can take away from the anime world as well, to life as well as to development and Kubernetes and all of that both. But there's one bonus lesson left, which is the most important one out of them all, which I think is a very much an overarching theme across all of these anime series, which is believe in yourself, so if you can do it, go ahead, brace yourself, get stronger, get faster and really kind of live up to your potential and expectations. And if that fails and you feel like you're hopeless and everything's kind of really going badly and you're fighting a villain that you cannot beat, just start flashing, grow your hair along, it's all gonna work out after that, there will be no issues that you cannot beat if you get to this stage. But if you yell out a bit too hard, your hair gets frayed, it's all going a bit badly after that, no worries because you will just end up being the most powerful person in the whole universe, so it's all right even if it goes a bit too far. You might go bald, but that's all right, that's the sign of your true power and your conquering of the world of power, for sure. Yeah, thank you everyone, this was the session. If you have any questions, just handle it, I'm gonna pass Michael yours. Any questions? I think it's great. Yeah, yeah, yeah, it's all completely clear. Okay, thanks for attending. Oh yeah. What's your favorite anime then? That's the most difficult question, for sure. Well, for me, I started with Dragon Ball and Dragon Ball Z, so that's kind of like super close to my heart, but then I think I really like Bleach when going further, but from other genders, I really like Nana and other things as well, but I think one of my favorites is Darker Than Black as well, which is a bit less well known, but there's a lot, there's too many. One piece is a classic as well. Yeah. All right, thanks for attending and have a good rest of the day. Thank you, Annie. Thank you.