We do not have oil or carbon or steel or any other natural resources, but the good part is our most important resource is people, and we need to invest in people. And given having an educated population is the best way to trigger not only economic growth but development and well-being and peace as well. Investing in human development has been one of the best investments of Costa Rica. We are aiming to decarbonize our economy, and what's the goal? It's reduced emissions and the usage of fossil fuels while at the same time we keep growing. And we plan to do that by plugging our clean electric matrix to mostly transportation. From all the energy we use in Costa Rica, 70% is on transport. So if we plug that 30% that's electricity and it's clean to transportation, we can rapidly reduce the usage of fossil fuels, be more competitive, more clean, and not dependent on petrol or oil or fossil fuels. So that's our plan to use to come.


Oh, excellent. Nice. All right, welcome to the TV, Mando episode two of season three. Episode three, season two, the Mandalorian Disney round.  Yeah, it is. One Star Wars dot com. It's like ebombs world. Get your friend today. Here's a fun little fact about this episode. IGN gave it a five out of ten. This one. Now, that is that is an interesting because IGN scores stuff way higher than we do. That means it's like a one out of ten. They are beautiful disciples of the mouse. So I'm going to throw a wrench in there. That might mean it's good because our version of like Terrible Mando is other people's versions of like Good Mando and vice versa. Well, so one of one of the. Oh, I don't think I want to know.  Am I right? Ah, and keep it a nine and keeping the IGN traditions, though. Like one of the things that they appeal to is that the lighting is bad, like a very hyper specific thing.  Yeah, exactly. It's just these weird sort of like. Luckily for them, we were born surrounded by water.  How's that? Just like because we're so poorly lit. We are in the process of making sure everything is running perfectly in terms of releases. We have unfortunately not been able to release the first episode coverage before recording this one, thus no comment showcase. However, no, hopefully by the time we hit episode three, we'll have a double comment showcase going over the past two wonderful episodes. That's incredible. But my endo is much more than just no double comment showcase. We got another showcase as a drug. Stop is greedy. It's no is heroin in my veins. No, OK, the first episode, hyper, hyper generic, but probably hit all of the boxes it was supposed to. And thus people are like, well, Mando is back and it's better than all the other shows. Well, I've seen Mucho sentiment a that it's better than Andor already. And it's like, hey, how? Oh, yeah, I got another word of one of his bricks. That's it's not that. That's so I wonder if this guy is loaded. Why would you even say that? We had battle at the start, but. Just just show the clip. I wonder if it's loaded. No. Oh, so that's what you guys mean. I got you.  There's no Star Wars, because I just I guess I find it. I didn't see lights. Sabers. I find Mandalorian incredibly boring. Yes. It's pretty. I find it exciting in like how bad it is. Oh, yeah. If I wanted to go into earnestly to try and like learn about the characters in the world and gross some kind of theme, I'd be incredibly. Oh, you'd be miserable. It's only entertaining because it's funny that it's bad. But like, if you were trying to watch it earnestly, I don't know what you're like. Where's the character? Like, there is no character. Feels like a cutscene you're sitting through so you can get to some gameplay that is the real reason you're there, but then you just watch the fights. The devs. Well, the devs think that the cutscenes are way cooler. So they really insist on having these cutscenes play out for a long time. And he was like, yeah, that's a good season for is actually going to be the gameplay and it's going to be amazing. Oh, yeah. We just had to have three seasons of setup because of the complex characters and their emotional journeys and the world building. But season four, man, go, though. Jay, welcome. And what is your take on episode one of Mando Laureans? Season three, episode one, one. You want to know my opinion of the episode one of Mandalorian? Episode one, season three of season three. Well, I can tell you, but first I'm going to need to go to the planet Klempton, where there's a guy that I'm going to need you to meet. And he's got he's got like a little thing that he needs you to find for him. And once you do that, I can tell you he's going to unlock a chest that has my opinion in there. And you're like, wait, there's no opinion in here. And it's like, ah, it's in a different box. It's well, you know, I need to I can't explain yet, but I'm going to need that to tell you my opinion. Yes, you see, I built a robot that gives opinions, but one of its circuit breakers fried, but only a very specific manufacturer on planet Glorothomp has the part. So you're going to have to go over there. But you might want to find yourself a bodyguard to go there because it's a dangerous planet full of gleams and slur bags. So you definitely want to go to Pro Joe gum for to get yourself a particularly good bounty hunter. And that bounty hunter is someone that I could tell you about because he and I used to go to high school. We were on the varsity space ball team and he's really cool. But I don't know where he is. So you'll have to talk to him necessarily. And he might be. Oh, no, I definitely can't trust him. And I know where he is. So you have to go and talk to Jim, who's another friend. He actually lives down the street and he might know a clue that you could find to find the bodyguard to find the part you're going to have to find his front door keys get into his house. That's true. And legend has it that he keeps it and you must decide. Well, yes, but there's a riddle that you'll have to decipher that will tell you which one of the rocks has the key. But the key you see is separated into four segments and each segment is on four different planets. He lives a very complex life. It takes a long time for him to open his door. Well, my favorite part about these things is always that I know that there's someone in the live premiere chat really, really annoyed that we've not started the episode yet.  We're still talking. You see, in order for us to start the episode, we have to acquire a Disney Plus subscription. And those can only be given to people with special passes. And so we have to complete, which is tough for all five of us to do. That's true. We've got to go to a different planet where the subscriptions are because the factory that produces them is being attacked by a group of. The scorpions are scorpions. Scorpions, female scorpion, female. Yeah, they have a little boast. But really, you might think that they're bad, but they're misunderstood. So over the next episode, we'll get to understand the scorpions and we'll get to really empathize with them. Yeah, I think even if they enslave us, when does that even happen in Mando? Understanding a person. And also the other thing I think that you're you're overestimating is like almost multi-episode quests. It's not an impossibility, but it's usually that a lot of the side quests self-contained within the episodes anyway.  OK, like sounds kind of grand and then it's just gone. It's not called a quest. Let's call it an errand. Yeah, they're errands and they're very low. Well, like an errand. Yeah, because we know that errand boy. Well, I mean, that would be more suitable. But I guess I'll get a man and errand boy because we're going to get pirate master back at some point. Greenman, right? Yeah, I believe his name is pirate Lord God. Pirate. What was my name? Pirate Lord Elon Musk. I think shot is like, oh, my God, shot. And it's like, no, Mel, stop. Yes, sir. It was one detail I really liked in the in the whole episode. I was like, it's a shame that that detail is here. I liked how the little Babou Frick place that they went into was very small. It was a little house built for small people and looked massive in it. And something that I said was I would have just preferred to see a show about those guys repairing like just being mechanics, a sitcom about all of the crazy little love triangle and the coffee machine breaks. And they got to get that so in tune in next Tuesday for three little engineers in a big, big world. It's the thing I've been saying for years is like, I would just like it if they made like, I'd like one about a decommissioned battle droid, like just trying to figure out what his purpose is in life, like after being decommissioned after the Clone Wars. I imagine they have a relatively limited capacity for thought, but they'd still have some things that they do think. I want some high concept stuff going on. But yeah, she needs it so that they're learning and the critical thinking can be unlocked, so to speak. Yeah, necessarily that they just have like a limited capacity for critical thinking, and that's what they have to use to get by.  What about the super battle droid and a battle droid? And the super battle droid is of the lesser thinking abilities while the battle and hard. Yeah, and the battle and, you know, we can have funny, but we could also have pretty dramatic in terms of like, you battle droids kind of an idiot, but got a good heart. What's he say in terms of what's what's you actually think? Oh, oh, the episode where they get shocked and their brains like swap. And so they're but their body switch. That could be really it feels like we're making a really funny comedy now. I feel like I feel like the way they're written is that they're like they seem relatively stoic almost. They seem pretty like quiet and efficient, right? But it would be a good example of your comedy. You are like the straight man and well, it's an inversion, right? Because usually the straight man is the is the smart one. Well, yeah, I mean, you don't have to be intelligent to point out wacky antics.  I'm just a third compared it is the droideka and it's like shields are busted and it's got like lots of bumps and maybe you're missing a gun. Oh, and maybe maybe he's he feels very vulnerable. It's like he used to be able to protect himself from the world, shield himself from pain, and he has to learn to accept pain as a part of life. Guys, come on. What's what's weird about the battle? Do I move around anymore?  Yeah, like it's like maybe you can roll, but it's like a really awkward role and only he can only turn left. The Disney Star Wars people, they've they've spent so much time trying to do nostalgia and everything. Remember this? Remember that? But there's legitimately an insane amount of real world reasons or in law reasons why you would see battle droids all over the place. Yeah, I mean, after the after the Clone Wars, all the battle droids are just like decommissioned. They're turned off. They're not destroyed. They turn off curious what they did to the one. So every we would have every mercenary and personal part. They'd be used as bodyguards and protection. And a lot of companies would scoop up with the ones that they can. How come we don't see just all the blasters everywhere, they would flood the market of Star Wars after the. Yeah, everybody would have destroyed. But we don't ever see that stuff on time. But they were like a trillion battle droids manufactured. It should be like it's like like AKs are everywhere in the world now because there's so many of them and they're so cheap and they just get made by everybody. That's what that's what the battle droids and their little blasters should be. Like every criminal organization and every mercenary group, they should have battle droid blasters. They should have like battle droids and maybe they've got like three hooked up to a little control module or whatever or a guy who's on the outer rim and he's got like like a palace. What was the episode where Ahsoka Tano was in the last season? Like, how come the the barren of that little estate didn't have like dozens of battle droids that they just purchased and inside their place they have the control unit?  Yeah, I remember reading in some something it was I think it was one of those like cross section books when the Phantom Menace came out and I had one. It was super cool. And they had one on like the battle droids and they say, yeah, the blasters are kind of crap, but like there's a bajillion of them. They're not battle droids aren't meant to be good and their equipment isn't meant to be good. But you know, enough of them and it gets the job done. So all this cheap stuff would flood the market after the Clone Wars ends. You don't see anyone, you don't see anybody wearing like pieces of Clone War or Clone Armor. They don't have shoulder pads or gauntlets or greaves or chest pieces. You never see all of that stuff anymore. And it's such a missed opportunity. You don't even really see people with the what are they called the E-11 blasters that the Stormtroopers have.  But you just don't see that stuff. There's no like all the chances they have to flesh out the world and have references to old things. They just don't have a lot of work. Yeah, that would be girl girl, which is why we don't have it. I suppose so. Yeah. Instead, we have to watch Mandalorians being eaten by a crocodile, because that's cool. And then that was the moment where I was like, oh, I remembered exactly the way we're back. Everyone's awful. Aren't they cool? It was a great starting scene to bring us back to Mando. It really was. I I already am thinking about at the end of season two, they encounter a fourth member of this droid. It's the Magna Droid.  He's like in pristine condition and he's the fastest and strongest out of all of them.  And if you guys see Bone Tomahawk. No, no.  But he's like, he had a job to do and he did it sort of point of view. And he's quite intelligent and good at his job. Sort of like a character that I want to see this droid show. Well, the Magna Guard is there to have again the reference to old stuff and to have a melee fight. You have the, oh, I got it. I got to stop you. And he's like, oh, yeah, well, you have to get past this. And then he's like, I bought this Magna Droid, but go get him.  And that's your excuse to have multiple things that you want. And that would be cool to see something isn't a Jedi fighting them. You wonder how much thought goes into like what they're going to do and give an episode of Mandalorian if it is as simple as who do we want to show up in this one? It's like, oh, Bo-Katan. Yeah. All right, we'll have a couple action scenes. Yeah. Yeah. Bo-Katan is really cool. Yeah. Yeah. Yeah.  What? Yeah. Well, I mean, what else is going to happen? They'll interest these people in this show. I don't blame them. It would be more interesting than the story at the show. Oh, dream. Oh, God. It's the Star Wars.  I was going to say, is he going to take a selfie? That is the most that's probably a reasonable way to get proof. Have you ever heard of Bo-Katan Crees? Bo-Katan Crees. Why did one of you say Bo-Katan and the other say Bo-Katan? I don't know. It's the better way. Well, we're going to get the mandos in trouble and then Bo-Katan goes, we, I followed you. Here I am. What is your hairband? Glow. Why doesn't it go in space? Yeah. I actually am wearing one right now and it's purely analogue.  It was a few to be poor. It's cringe. It's kind of comfortable because there's no like metal bits or light sticking out of it.  The metal bits on the outside and you would have padding on the inside. No, tattooing. Oh, it's the ladies.   People probably die every time this race happens. It's the flimby fingers. Welcome, cameo.   The robots can live. I don't know what to tell you, pal. Fine, I'll push it back out in the street. Petroids. Why do people like this character? Don't know. It feels the same as Carl Weathers' character where it's just... You remember her? She's been in Bethel. He's got a cool little outfit there. He looks like he's dressed up and going to a party. Yeah. See, this is what happens when I watch the show. I'm like, why can't I follow the story of that alien? Or why can't I follow the story of that droid? Yeah, he looks like he's going to a wedding. That is what Andor is. And we do anything else about this. Andor is that with other human characters, for sure. Which is totally fine in terms of POV. I just want to see more aliens and droids in Star Wars. Yeah, look at it. He goes home, all depressed. Andor was actually very minimal on the aliens and droids. It was very minimal on the aliens. I would like for them to have an alien POV character at some stage in that show. I agree. More aliens. Also, they didn't show him taking out the wallet with those flimpy fingers because they knew he couldn't do it. Aww. Again. So she hires the Jawas to steal ship parts and then she puts them back on for a price?  This is exactly what happened to Mando, by the way, that pissed him off. Mando should have killed them. He should have vaporized them.  I thought that she... I don't remember her... Why did they need them to do the sticks? Being a hoxster. Yeah. That's lame. I'll keep bringing it up. But you'd think that in all the years Mando was doing bounty hunter work and making a name for himself, he'd have like contacts and people he could go to instead of random assholes he just bumps into. Well, they're only ever people that we've ever seen during these seasons, you know, like it's not. Except for Bill Burr. I think Bill Burr was one of our... Bill Burr's like the only person I would like to see. That's something he can do. Luke taught him how. Remember when Luke shot at him with a phone? Yeah, that was fun. When he would have learned about jumping. That was the AI Luke. That was Skinwalker Luke, don't count. You know how much I used to get during Boonja Week? Oh, Boonja Week. That's when the pod race happens. Woohoohoo. References. They're gonna show the pod race. Hopefully they show Anakin. It wouldn't make any sense, but that's not important. I'm looking for a replacement IG memory circuit. They haven't made those for a while. They don't have a net, they don't have... The Jawas have a word for memory circuit.  I was gonna say. They don't have a word for memory. I need my droid fixed now. I think you should buy this beauty here. I need a droid that's rated for spelunking. Spelunk? Droid that's rated for spelunking. Spelunking? Is an IG unit a spelunker? I need a droid that can explore ahead of me and test the atmosphere. Surely your ship can test the atmosphere when you get there. No, you can access the galaxy. Why do you keep coming back to this shithole to buy these important pieces of equipment? I feel like that's worth emphasizing. You need an IG-11 unit to test if like Mandalore is safe to breathe. We humans with not IG-88s, because we don't have those, can figure out if other planets have a breathable... I don't see why your ship can't do it. ...land and then detect. Yeah, but no one actually knows. Has no one ever been there? No, no one has ever been there. That's one of our problems, is that apparently Mandalore is just an inaccessible fantasy land and you can't like take a starship and just physically go there.  I mean, we actual humans have landed probes on Venus. No. What I'm gonna do is I'm gonna give you this for half the price and throw in a free oil bath. Oh, I guess he's going with it, sure. Wait, does that mean we're dropping the IG side quest? Maybe for now, but we'll return to it later, I guess. Oh, but now there's no place for Grogu.  Wow, why did you have a bigger ship, man? I know we're all really happy in the way, I stopped blowing up. We were thrilled, but like, got a new ship. Yeah, we were... Why were we thrilled? Is it because we just... It was just the same thing over and over again. Was I happy? I don't know if I was happy. Maybe, I don't know. I think that's pretty much happy. Yeah!  God, somebody uses their ship to blow up his ship. I'm happy about this.  That's a tragedy. Bye.  The point is, he needs a better ship than this. This ship is terrible for long distance, like, just for his line of work. What if he has to bring, like, anything with him? We saw it in the first episode. He freezes the bounties in carbonite. He can't do that. There's a lot he can't do. Oh, God, is this Mandalore? Was it that same Mandalore? Yeah. Why? Why does it look scary? You could have gone here at any time of the entire sitting show. Every Mandalorian can trace their roots back to this planet and the Bascar mines deep within. You can't trace your roots back here. Wait, there are Bascar mines there? Then how come it isn't full of people mining it? It's dangerous. Oh. Remember, he's not Mandalorian. He won't be poisonous. They don't know. He's not Mandalorian, officially all by blood. That is home. His home is the moon. I grew up there on that moon. Concordia. So here's Mandalorian, right? Because this is the Mandalore system. No, officially not a Mandalorian. And by blood, he's not a Mandalorian. He's got to go in the waters. Then he can be Mandalorian again. Well, that's about the atmosphere. What kind of ship just analyze things? Yeah, just buy a sensor, buy a probe. Do some bounties, make some money, buy a probe. Or hire someone to do the probing for you. Your sensors don't want to be crashing or something. It should be a great time to do a like, hey, remember the probe droids? Probe droid cameo? Yeah, after the empire collapses, all those probe droids, I bet people are going to buy those. No. Oh, it looks bad. Doesn't seem that bad at all. No, it looks pretty cool. It's going to be really funny if there actually is no dangers. Looks like the fusion bombs from the purge disrupted the magnetic field around the planet. From the surface, we won't be able to communicate with anyone out of atmosphere. How communicate with anyone off planet? I wonder if there's a reason they've just said that. This is why you should go here alone, I guess, instead of hiring someone to go with you. Yeah, like it looks kind of bad, but it's still tangible as a place. Yes, landable as we could land here. Working atmosphere movement again. They're right here, yeah. Oh, yeah, shields. The magnetic bombs from the other fusion bombs from the purge disrupting the magnetic whole planet. I'm going to need you to scout ahead and analyze the atmosphere. How can you not analyze the atmosphere from there? Yeah, there is atmosphere all around just bad. I'm glad that I bought the cowardly robot. I'm glad that I bought a robot who had a sense of courage, you know? Like, it's a good thing we go around. Well, so that's the funny thing, right? Like, R2-D2, I would probably describe as quite a courageous boy. Is asking him to take a sample of the ruins below from like a crack in the ground is the only reason why. Any of these, just take it from here. Yeah, I don't know. Why can't you just ask him what the results are right now? Go over to that split in the rock and take an air sample of the ruins below. Why do you need to know what's in the rocks as opposed to what's in the air? I don't know. We can even walk here first. Or is it a foregone conclusion that you can just walk around here? Well, but that doesn't cancel out all the worries we've had across the entire series. I'm not defending that.  What's he going? I'm just trying to figure out what they said. I thought that they said that the poisonous stuff was about like just being able to walk around it all. Here, look, you can watch him on the scope. You don't have a camera that shows what it's seeing or something? No, no. Okay. Oh, the red light. Oh no, of death. Of course. What did they do to R5 to make him disappear? Contain his combustible. Or it could be something else, bounty hunter, Mandalorian man. Normally, this is droid work. I was hoping to avoid going out there. I'll pressurize my helmet. Seal yourself in your pod. No, that's not how that works. You can't just... Oh, but how does Grogu... But you opened up Grogu... Wait, where is Grogu? Grogu is gone. That's fine. Grogu is dead. He's dead. Grogu is dead. Hey, hang on, hang on. Didn't Grogu crawl through the ship from the backside to the front side? There's no window on there anymore. He depressurized the ship. And also, do you have an oxygen tank? Apparently, yeah. Apparently, there's oxygen in the helmet. I don't know, okay. How are you alive? So is it safe? I don't know. Who knows? Maybe. Yeah, why does Mando not have any scanner like on his wrist or something? Why does he not just fly the ship over there and see what happened? Ooh, a spooky cave. Oh my goodness, it's a spooky cave.  I don't think the droid had time to go this deep. Unless they montage cut it. I was about to say, you're not familiar with the concept of montage. Oh no, it's a... The Vista. It's a place. Or something.  Oh my gosh, they were just waiting. Just waiting for someone to show up. Playing for somebody to show up. How often do people show up here? Well, you know, they're always ready for you. Bro, why use that? It's so heavy. He's still kind of wielded properly. Do you see that? It's still like it's heavy. He's still calm. It's going to be part of his arc is leaning on a wielded. Is he going to pull off?  Here, use your other gun. Oh, you only brought the one. Oh, your flamethrower. Oh, my leg. Literally any other kind of knife in the scenario would be better than the heavy one. Oh, you killed this man. Yep. They're just defending their homes. His armor is so boring. From an armed intruder. He literally just took, like, 11 hits and none of them mattered. That thing is clearly intact, and it's alive and working. Why did it disappear from the radar? Because it was locked over. It only works if it's the right way up. Sure, it's like an Xbox 360 where if it's running and you change its orientation, you lose the CD because it gets scratched. Damn. Yeah. Oh, well, I guess some of you guys in chat, you'll remember the old days. I was just thinking about how if he died here, Baby Yoda would just be stuck here and would die. Like, why is he bringing Baby Yoda on these missions? That seems pretty irresponsible. You got an analysis on the atmosphere yet? The charts were wrong. The atmosphere is breathable. Why did you not just check? Why did you not just check first? Why did you need to go down there to find that out?  The atmosphere is everywhere. And he's the first person to realize Mandalore is not cursed and nobody else is good at this. Outside of Bo-Katad, she said that there was a poisonous. Again, Mandalore is filled with Beskar, which means that the Empire would have an interest in figuring out what's on Mandalore. So would every mining corporation across the galaxy.  Insane when it's worth this much. Hey, there was some random chick with a spear. That's true, and then he melted it down and made whistling birds and chainmail. What about the people who were killed by a big crocodile? Remember he turned that spear into chainmail for Baby Yoda? I wonder if that'll pale. This is where Bo-Katad said to go. You're not concerned about there being people here? Who live here? Well, I guess not, Rags. Nobody comes here. It's poisonous. Oh, except for those people, I guess. Except for these weird cavemen people. I guess they live here all the time because they don't live here. I'm pretty sure this place is in the Clone Wars. The mines should be further down. I guess we're on our own from here. This isn't the mines. This place isn't the mines. No, I guess it's on our own. Yeah, I was about to ask. You were alone the whole time. Does it mean they're not going with our full? But our full is back on the ship, isn't it? That's what I mean. When he said I guess we're on our own, I'm not sure what he means. What about the samples that you needed? Oh, you got them. No toxic. Oh, we're fine. Wait, that would just be the air. That wouldn't be... What?  Yeah, because the air is breathable, but is there radiation?  It's fine. It's beautiful. It's wonderful. And it's fine. Oh, look. Lizard. Oh, look at my face. Lizard Isle. I mean, I don't feel like that's helping you much at all, but OK. I'll accept it. Why would you even need a light? Doesn't your visor have, like, infrared night vision stuff like that? Yeah, you used that in an episode. You used one, right? I think it was a scope. Oh, OK. You don't remember that incredible gun that lets him see through walls? Yeah, we just... What happened to that gun? I don't know. We don't talk about it. You didn't get another one either. He doesn't have a rifle. He just has one pistol. Bo Katana has two pistols, right? He should upgrade. Yeah, he should get, like, an EMP gun or an ION cannon or a sniper rifle. Well, don't forget whistling birds. They're pretty OP. He's got them, too. Look, that passage heads down. Yeah, I can see that.  Oh, my God, Mando. That's a helmet. Do the sound. Has Mando ever been to Mandalay? Or is this the first time he's been to Mandalay? I think this is the first time. I feel like we could be doing a lot more with him in terms of character if we were actually OK. Why would we do that? Let's just find a helmet. Yeah, I don't care about the Mandalorians. This doesn't mean anything. Just don't ask if he loses. Oh, what? Nice. Wait, was that a trap? Except for people that want to pick up Mandalorian helmets, I guess so. I guess they are really valuable. But, like, how often do they get people coming down here? Wow, this could be the first time he's actually in trouble. Oh, there's an eye. Oh, there's an eye. Oh, there's an eye. Well, bye. And now Baby Yoda's got to go on a quest to save Mando. So this is only happening just because Baby Yoda wasn't right next to him, as he usually is.  No, that's good writing.  Oh, it's like the tripods from World of the Worlds.  Can you not move at all? No, it injected him, I think, with something on the neck. Yeah, it did inject something into Mando. Give me a little stabaruni in the neckie hole.  I like this guy. Yeah, I like the design. He's kind of cool. He looks oddly not really like Star Wars, which is why I like it. Oh, it's a cool design. Yeah, I like it. This looks nice. It's like a grimy Star Wars. And I'm kind of digging it. Like it's dark sort of. And considering the music, he's probably not friendly at all. He also looks kind of evil. He'll still be a little total twist, where he actually knows Mando very well. And he's like, oh, nice to see you. Oh, yeah, this is my friend. Are they pretend to like want to kill each other? Then they go, Mando, hey! Yeah, I love that. And then they hug. Yeah, it's great. I think we just want to test to see if guns are loaded. I'm sure that'll be picked up later. Wait, just he can still move. So whistling bids, do it. Oh, yeah. Why doesn't he give that a try? Now, remember, as we learned in the book above, if that Grogu can like pull like a bolt straight out of a mega battle droid assault strider, which it takes insane amount of force, no doubt. So there's really nothing that should be able to stop from doing anything. I saw an episode two, like even for a beginning. The thing is, even if maybe it opens this cage, it's not going to help shit, right? Because Mando's Mando seems to be, yeah. Get to Boca-Tan. What? How? How? He has to leave the whole, he has to leave the mines, get back in, go the way that he's been. Maybe you're going to get to Boca-Tan. It could take weeks. Are we actually going to do that? This is actually going to be what happens. How can an infant, how can the infant work the starship? Oh, he's got wings. You know, he could just seal up the pod.  Oh, he's OK. But then they can't see him and it wouldn't be as cute. Oh, so how does the droid know what to do? Yeah, how does the baby communicate? Speaks grogu. I guess he's leaving his. Oh, do you see how he pointed to, like, all over the place? Go there. Does the droid speak baby grogu? Is the droid just like, oh, the infant is giving me instructions. I guess I'll go. I guess I'll leave. I hope the other guy's all right.  Like, come on. Is this all Boca-Tan does? She sits around moping. She puts a piece on Ethan's fence. Does she have any schedule? Yeah, I was about to say, robot, you know that we don't have any schedules here. I just sit around and mope. Why did you buy me? I used to live in a nice place. I used to be a bartender. Let's get rid of him. Maybe I didn't make myself clear. There's clearly no one in there. Who's she talking to? What happened to him? Got beaten up by a big droid. Why do you care? Do we just want to be the dark saver? He is probably very dead by now. It's been, like, days? Well, this is in the Mandalore system. Oh, it's in the same system, I guess. But still, it's a while, all right? Like a couple hours at least. No, it's like 20 seconds screen time. So it's like an hour. Well, hopefully the droid creature has done nothing to him in this time. And I guess Bo-Katan just never came back here. But she is now, because Mando came here. Well, she said it wasn't poisoned, but she never actually checked. No, she said it was plundered and poisoned. She said that the planet surface has been, like, poisoned. That planet has been ravaged, plundered, and poisoned. Well, then she really didn't know. Why didn't you never went here? Really? Just didn't bother. Especially with how important this is to you or whatever. It's like your next door neighbor. Didn't always look like this. Oh, I don't care. Thank you. Yeah, they didn't build it with a style of apocalypse chic. That's surprising. It's all the rage on Mandalore. Yeah. See if you build it and it looks like it's destroyed. If it actually gets destroyed, it's really no big deal. How did baby Yoda communicate exactly where they landed on the planet? Droids. Oh, wait, they downloaded the thing, yeah. All right, well, I'll cut that out. No, that was funny. You have to leave it in there. No, I'm cutting it out. What's droid doing? No one ever, like, plans or prepares for anything, you know? Just watch it. Why did you even show us that? Don't worry, guys. The droid is watching them. You're like, OK, you can only watch them for as long as they don't go in the cave, right? Which they will do immediately. Yeah. Oh, man, I can't wait for them to get attacked by those. Well, that would be another action. Oh, yeah, we've got. So we're going to have three this episode then.  I can't believe this is how we got Boca time into it, literally the longest way around possible. Yeah, why couldn't it just be that she wants that? I would have had to follow him. I would have had to follow him. Or what you're taking.  I told you whatever. And then he's like, well, why are you here? And you can do character things. There was plenty of reason for it to come here without having to do this. Just to set a distress signal and then have her show up.  All right, gosh, pay attention, even though they could just not have that be the case. Yeah, that was plus significant because it makes the episode more boring. I still think it would have been you have a show, zero interest. And it turns out she's actually very interested and she did follow him here.  Now it's a tomb. Everything was around this place. I've seen this two minutes ago. Yeah, we're doing this again. Nice and slow. I know that you're frightened, but I need you to guide me to him. Maybe you should pay attention to the fact that the child is suddenly indicating danger. It looked like a growl from the line. I knew quite a few Jedi, you know, I don't know what they taught you about us, but there was a time we actually got along quite well. We've discovered so much about that across the three seasons.  How did you know that shit? Well, now she's got other moves. Rags are so much more cool. What is combat?  You have to just show different things whereas the audience gets bored. Man, that shield was so small. That shield was tiny. Did you think your dad was the only Mandalorian? No. Why would he think that? No, I...  Why would she say that? They used to live in the world with him. Also, I thought Baby Yoda met Bo Katan in season two. Yeah, he definitely did. He was them. He met him many times, actually.  So he's just been chilling in here with that thing doing, I don't know, having a wank or something?  Because then the show would be able to come to that. I didn't even know what this thing is up to. I need your blood. Ooh, that'd be interesting if his suit like needed blood to be put into it. The tubes, like they start filling with blood and he drains Mando's blood and then we don't have to have Mando be a character. How do you stop his draining Mando once he'd got him? He'd be dead by now. Yo, give me your blood. Yum, yum, yum, yum, yum. Oh, well. Hey, that's my blood pump. Miss, miss, miss, miss. Hit, miss. Nice. Wow.  Wow, she's way better at it than Mando is. Yeah, she's pretty good with it. Yeah, look at her. She's awesome with it. Oh. I mean, I'm glad that she's better than Mando at something because Mando is better than everybody at everything. Oh, that was nothing. Wow. That was a half-action scene. Has she wielded it before? Oh, no, he's OK.  Yeah, there he is. Oh, that's cool. Yeah, scurry away. Are you trying to say something? Get this needle out of me. They're still in me. You could tell that they're in me. Wait, how did it? How did it get into the... How did it make no noise getting to it?  Oh, well, it's the dark saver, so whatever. Well, that really was two halves of an action scene almost. Yeah, they both sucked. That's three action scenes right there. Yeah, we got three. That's crazy. I wonder if you could, like, trick the Disney mandate people into thinking it was more action scenes by putting a little brave breather in the middle of it. Yeah, it's like it's actually four, really. How did you find me?  He's tougher than he looks. Then he's quite the navigator. Quite the navigator. Quite the navigator. Everything interesting in this episode is dead now. You're right. Mandalore is not cursed. Was I? Look around. There's nothing left. That doesn't mean it's cursed. That means it's empty. In a symbolic way, Rags. So she's right still. I once ruled here for a brief time. Yeah, you did a bang-up job then. Nothing to cling to, but ashes. I mean, there's clearly a lot here. Who's best are minds? You've never eaten Pog's soup. Pog's soup. Pog's soup. I'm made of Pogs. You can check at home. I'm gonna be at the... Let's dump in the Pogs site. Yeah, it's definitely in your mouth. I think he just dropped that all over his chid. I don't think that was enough. You should rest. I'll get you back to my ship soon enough. I'm not going with you. Well, you kind of have to. Your ship is not here. I must continue to the minds of Mandalore so that I can... No, come back next week.  I honestly think that it's adorable that you actually believe these children's stories. It's not really whether he believes it. It's what he has to do. I thought it was symbolic. It's not actual magic. Also, I feel like there's good reason to believe it. Dude, this is a Star Wars universe. It's not reasonable to believe in crazy magic stuff in this universe. Without the Creed, what are we? The Creed is how we survived. You survived despite the Creed. Not because of it. The Creed is nothing but counterproductive. He did just make the argument, though. I gotta do it because what else is there? Which is like, oh my God, character? Well, it's only season three, Mahler. We gotta start at some point. You rescued me and I'll always be in your debt but I can't go with you until I fulfill my obligation. I will take you to the Living Waters. Yes. It's no one gonna point out that your ship is not here, Mando. Like, they got here with her ship, whatever. Oh, yeah, that's right. He needs to go with her. Yeah. She'll get this back on the castle. You'll do it later, it's fine. Are you within walking distance of the location you need to get to? This is a planet just so we're clear. Hey, remember? Remember, she gave him directions. It was underneath the Civic Center. That's where they went. We must pain you to see it like this after witnessing its beauty. What pains me, seeing our own kind fight one another time and time again, killing each other for reasons too confusing to explain. Which makes it easier to write. There, the entrance to the Mines of Mandalore. Whoa, we're here. Oh, wow, it's right there. It's right there. There's only one. There's one Mines of Mandalore. I'm not a Mandalorian. I was part of the royal family but the rituals were all just theater for our subjects. They loved watching the princess recite the Mandalorian tenants as her father looked on proudly. Maybe he was proud. I know he was. Your father sounds like an interesting man. He died defending Mandalore. This is the way.  Hot take, that's probably the most meaningful that's ever been. Is that even a hot take? Every other time it's just like nothing at all. It's more meaningful than you can and knuckles me. This is the way. Do you know the way? Because yeah, it was like top ear meme. That feels more suitable than I've ever heard it before. Like the fact that you'd say that to her when she said her dad died defending Mandalore. These Mines date back to the age of the first Mandalore. According to ancient folklore, the Mines were once a mythosaur lair. Ooh, dinosaur. Mandalore agreed to set your dreams a mythical being. If you want people to believe it exists, don't call it a mythosaur.  It's the symbol of our planet. Jump in, Mando.  And then I'm your king. Let's see Pedro Pascal or is he not in this season at all? This is very meaningful. Yeah, are they going to treat this like this is a very solemn and incredibly important moment? I swear on my name that I shall walk the way of the Mandalore and the words of the creed shall be forever forged in my heart. Bye. Thank God, let's go home. That's good to say at least something. Oh, I guess something very wrong is happening. I thought he just like went into the deep end or something. Belly flop. Jesus Christ, how far did he go? Oh, my God. We grabbed by one of those dinosaurs. Quite a drop. Well, luckily, his helmet has oxygen capabilities or whatever. Or a pressurized, right? Yeah, well, it makes that sound. It was some serious. He's like, sorry, I tripped. Is this kind of an action scene? Wait, what? Is this how he tripped? How did he get you so fast? Something must have grabbed him. Yeah, because she was like thrust in downwards. He's like knocked out, too. That's the only reason why this happened, because he fell like Homer Simpson fell off the gorge. I assume it's the monster that did it. I'm all where it is. Where is it? Where is it? Yeah, well, the eye ball. Let's just hope it started. Oh, is this a myth or so? Is that the meme? Oh, my God, it's the myth or. Oh, I get OK. What does it eat? Did he legit just fall? I guess so.  How embarrassing. I think he did just fall. I thought it'd be like a tentacle. How are you coughing and wheezing? So you have the how? How is that? Really? What was all of that? What? Written by John Pavarois. Why? John, why? A terribly bad episode. Oh, my God. He fell. I guess he did just trip. Watch out. And then he couldn't swim. He just drowned. He just sunk like a rock. Yeah, because the album is so heavy and he didn't have his jet pack, I guess. So you just that's so embarrassing. That was the main thing that happened in the episode. He's like an actual infant. He fell. You can't you can't let Dan Jarin like play around empty plastic bags or he'll suffocate himself. You know, I'm just I'm just imagining him going back to blacksmith ladies. Like, did you go to the water? It's like, yeah, I was super that I did. Molly, you're the most likely person to get this reference. You know, the bit in little Britain where the guy is in the tree. Yes, it's like the greatest joke in the show. How did you get out there? I fell.  It's like watching a geriatric old man like slip his bathtub. I'm going to try to happen. Like you wish upon rags. Do you remember? Yeah, that's right. Like, no, this is. Oh, no.  We went through the same cave entrance like three times.  Yeah. So slowly. I'm just considering how lofty this one is supposed to be. This is the Mandalorian going to Mandalore, the forbidden destroyer. I thought it'd be the end of the season. I was about to say that, too. I thought it was like the big quest we do over the season was just like, no, here we are. Also, we are getting another end. And he slips. I was right before Mando fell down and tripped. I was like, wow, he's redeemed himself an episode, too. That's that's pretty interesting. You think the first episode, he was like, I need this robot because I can trust him. Then the second episode just gets another one. Like you said, first one that was suggested to it by the lady. Yeah, but then he goes to Tatooine again because we need more sand. Well, that's the cameo. That is literally the cameo. Never been happier to see a traffic cone. She mentioned Bound to Eve. We saw a rodent like that. That's the these are all amazing references that I love, Star Wars.  It makes you wonder if in the writer's room they specifically have a whiteboard dedicated to the cameos and references. Like, what are we going to reference? Who are we going to ask for? Yes, they do. Although I'm not sure if it's a whiteboard as much as it is like an AI. Yeah. But you need to have a whiteboard with other people who have to set up the costumes in CG. It's like, do it. Yeah, because it's something that I was thinking again is like, man, the visual effects, the production. It's like, damn, like there was clearly a lot of money and effort that goes into that side of this production. We saw an RB1 and Book of Barbuffet. Those ones were definitely more lacking in that regard. It's just a shame that there's no story here. I just can't believe we are two for two with the white grief cargo. Then Amy's keep forgetting her surname. Sadaqus? Sadaqus, I think? Okay. Sadares. Sadares. Yeah, who's episode three going to be? It's like, well, we still got to get Boba Fett done. Ahsoka time is probably going to have an episode. I wouldn't be surprised if we see Ahsoka again. In fact, I feel like that's a certainty that she'll show up again and maybe we'll get somebody that we haven't had before in Mando. But we'll build beer as well. We might expect him. He'll probably be in. Yeah, at some point. And that'll be the most interesting episode of the season. So, you know how we have the costume we talked about a bunch of times, the and then storyline where it's just yes, there's no connection to something else happens, right? There's a series of those. What I think is interesting about this is that I wouldn't give it that criticism.  And you're like, oh, so I chased him. And then we found there's some bad guys. We killed him. And then we went further and I got captured. And you're like, okay, that follows, I guess. It's not what I expect. Like I sent the baby back to go get my friend. And then he did. And then she came and then she saved me. It's like, I guess all of those things that happened and that they all happened because of the thing before them.  Like I never would have expected you to tell this story.  But it does like follow along. This episode's like mundane. It was pretty boring that they always forego any opportunity that's available to them and to build character that the one thing that we can compliment is like, oh, Mando kind of used their little mantra appropriately in a way that was kind of unexpected. That's the best you're gonna get. Well, yeah. And we got a little bit of Boca Town's history that it sounded like she wasn't really 100% on board with doing all of the Mandalorian Creed stuff, but she did it anyway and that people were happy to see it. And she said she didn't want to embarrass her father. It's so interesting that we have, because I mean, the dialogue itself is all just her telling you like what she thought and believed. None of it is very subtle. That's the best this has to offer. Yeah, it's a really lame story, isn't it? There's nothing here. There's just nothing. Yeah, what does it look like to sit down and talk about an episode of Mandalorian meaningfully? Like if you like it, you know, and you enjoy it. Like how do you sit down in it? Whoa, the city was, oh, wow. I guess I want to give it a little bit more credit. I'd like to know meaningfully, you know, if you wanted to sit down and do it. All right, let's try and do it.   I think they nailed it. I think that Mando as a character is like a very, very easy, almost completely blank self-insert for people who watch the show. Oh, we're talking about. I can imagine doing this. I can imagine going into the mines and stabbing the guys and shooting the droids. And it's really easy for someone watching this to imagine that they're sort of doing it. The reason why we make so many comparisons to side quests and NPCs and stuff like that and cameos and just these encounters. This show is very much structured like a sort of like an RPG where you've got like the blank slate protagonist who goes to all of these different places. He meets somebody, it's like, this is the quest for you. And it's like, yep, I'll complete it. And that's the quest for the episode. And then, you know, he goes off and does the next thing. And he is a blank slate. I mentioned this last episode and I conveyed him to, that was like the plan with Ray, was to make her a vessel for everybody to see themselves in Star Wars as. That's why she's so blank. But that one didn't work. It failed miserably. This one's working better.  And he's awesome at everything. Like, he doesn't have any problem.  Well, again, this is how desperate I am to grasp at anything. It's like, wow, it's nice that Bokeh time is like better than him, but something, like, she's really good with the dark side. And it's nice that he fails at some stuff, I guess. But like, it's very superfluous. Like those things can be indicated to something, but there's nothing actually happening here. Cause what is the main thrust of his arc for this season? You need to redeem yourself. Why?  Oh, wow. And then it's like, what does that entail? Like, is there something ritualistic? Do I need another Mandalorian?  And it's like, what? And then just go in the water and then you go. And then it's like, oh, it's not like. It does exist.  And it's like, no, it's not, though. It's like, no, it's not. It's not this. Really, the greatest threat is that you step off and fall down, like, into the gorge. Well, how important is this to tell his Mandalorian cult to be like, by the way, it is accessible and it's non-poisonous? Yeah. Yeah, it's like, we could maybe, it would be really hard, but we could go back there and try to rebuild something.  You don't have a spaceship, so no one's checking that. Nope. You should have brought your cell phone. You think that you could have a story of people who've made pilgrimages back to Mandalore and their quest didn't go so well, but it seems like nobody's been here. Yeah, no one tried. And it really seems like if a couple people went, you could kind of just be just fine because the only threat there seems to be, and as you come across this random robot, just some tribal people in caves with some sticks. Yeah, well those tribe people were even there already. She's like, oh, those are these creatures. We've known them.   There's just this guy who goes around setting up traps and we talk about the fact that guy was just living under a hat. That he's waiting for someone to, I guess, come along and pick it up so he can trap them and steal their blood. That was just his life. That was his life. Yeah, he was just waiting. We're not getting any more on that. No, he's just sitting there waiting and he looks like, that looks like a cool, interesting cyborg creature that's been there a long time and he's trying to take blood. Like, that's interesting. Does he need blood to sustain itself? Like in his own tubes and everything and what's he doing? How long has he been there? Was that like, was he a Mandalorian once and they were experiments or like, no, he's just got stabbed and he died? That's Mandalorian for you. It's like, you don't get to do anything interesting. You just get the surface level interesting and that's it. I'm sure the Wikipedia entry potentially might say something approaching interesting about this character and everyone will say, wow, isn't that cool? Even though none of it was in the show whatsoever. He's already gone, gone.  He died. Well, my favorite character. Now he's making me think about that Troy show I was pitching.  You should be continuing it or something.  And they realize and want to watch that show. Maybe I'll make it. You genuinely may have a moment there. You said that little spider thing was your favorite Mando character. And I was like, oh, that's genuinely true. Cause all the others I just like, hey. I guess Bill Burs the only one that could maybe be him. But I haven't seen his episode.  I just call him Bill Burs. Of the episodes I've seen and I've seen like plenty of Mando content, right? I mean, you know, like not, not like most of the show, but like, cause I watched, I watched all of BookabooFet which has like a lot of Mando characters in it. And I watched the NFC's in two and I've seen this. Do you watch Kenobi? You did, right? Yeah, that was a great one. So that would be like enough content to form like, you know, some kind of fondness for a particular character. Maybe, I mean, I've watched them for what? Like probably more time than is in the original trilogy. Remember the modders? They were cool, right? They did a flip. To be fair, that guy was pretty cool. I can't believe how much it pisses me off to see Tatooine. What have they done? I just don't want to see it ever. There it is again. It's sort of bright gloss in case of lack of nostalgia. I could see someone being like, well, that's where she is and he's visiting here because he needs help with droid stuff. And I'm like, I don't care how much you justify it anymore. I just don't. Because I know what the real reason is that they don't want to show you Tatooine because you remember Tatooine, you like Tatooine. And I was like, yeah, there's like pod racing.  You see, if we reference the thing that's happening in the world, that's world building. Well, he couldn't buy a droid on Navarro where he actually was. Yeah, it's like, why of all, you need a droid that kind of, it's really important. You need it to do like essentially scientific work. It needs to take samples. You need to scan the atmosphere. You need to make sure, like this is one of those things in an actual show, like a proper show that would be like, all right, I got to go through like my checklist of things I need for this mission. And then we could see him doing all those things. And we see how efficient he is and the decisions behind which droid he picks and the ship that he buys and things of that nature.  Yeah. And I'll go back to you because- After he was extremely particular about it.  I think we're just done with the droid. We think we just dropped it. Maybe, well, when he goes back to Navarro in episode six, the droid will be perfectly fixed. It's okay though. It's not like the only thing really we established on Navarro while we were there in that episode is that there are loads of really good droidsmiths there. So it's fine.  They were cute. Yeah. It's fun. Is it just because it looks like Babu Frick and that's it? That is literally it, yes. One of them probably is like canonically Babu Frick. That's probably the point we're at. Yeah. Yeah, this is where he was, you know, all those years ago. Frick is the gloveshitter of actual Star Wars though, by the way.  Yeah, what else is there to say? Yeah, we're done. Thank you everybody. One more thing, one more thing. Go for it. So, Frank, you guys remember Assassin's Creed one? What was the general idea there?   You need to go through all the stuff that someone needs to learn for being an assassin. You have to go through all of that again to show that, you know, you can do it. Well, fundamentally, you need to reconstruct your principles in doing this. You need to re-familiarize yourself and understand what the Assassin's Creed is and what you need to embody.   You just go there, you do it.  If you wanna be a Mandalorian, then you need to relive all of your training. You have to do it all again and you need to go through all the steps of the Creed. And that would be like, oh, okay, this gives him a wide variety of things to do. Like you have to hunt a beast. You have to tackle this. You have to do that. You have to do this. And it's like this big, long list of things he could do. And we can learn more about what the Mandalorian training actually entails. You'll probably have to go to all kinds of different places and things and do a wide variety of actual tasks in order to complete it. And we could see him, you know, relearning the Creed and we could learn it along with him. And that would be so much better and instead of go to this place and take a bath. That would be true. That would be very nice. The way he redeems himself is pointless because the rule he broke is also pointless. Yeah, and then it's like, it didn't even take a bath.  It's so embarrassing. Why would you do this? He's got the water. No Baxies, no Baxies. I was in, I was in. You saw it, you saw it. We saw the cool mythosaur, so that's cool. Yeah. Is that why that happened? Just so they have a reason to show the mythosaur, that's it? Yeah. What does it eat? What is anything we saw on that planet eat rags? Other mythosaur.  Yeah, but then what do they eat? They clearly, they clearly like. They eat the plant life, the glands. Oh, I love glands. It's delicious. Okay, it's called a Mando season three episode two. And we're done. This is probably the best one in getting this short of the longer. How do you think I feel? Thank you all so much for watching. We'll see you next time, folks. Kisses. Yeah, goodbye. See you later. Bye. Forged in my heart. Ah! What'd you bring me?


These slides may be familiar to you if you have been in the keynote this morning. I can go through them in two and a half minutes, but I think you are all here to get more information about dynamic resource allocation. So we will do a lot more talking, go more into details when we could in the keynote. My name is Patrick Oli. I work for Intel. I'm one of the key architects behind this new feature that you have been hearing about. This is Kevin Kries from NVIDIA. He's one of our biggest users of it and also contributing to a lot of the content, the example drivers. So he will talk about how to use this feature with GPUs, which is what you all care about if you're running AI workloads. So let's talk a little bit about what DRA does, how it's designed. It started out as an attempt to overcome the limitations of the device plugin interface. It took inspirations from the volume management. If you're familiar with the volume handling in Kubernetes, this new API is very similar. We have something called a resource class that can be created by an administrator. Users create resource claims. These resource claims get matched to specific hardware. And then in a pod and in a container, we reference this resource instance to give a container access to that allocated hardware. We designed it so that a resource can be local to a node. That was what you could be doing with the device plugin interface, but it can also be network attached. Then I mentioned the API allows flexible sharing between pods and containers, just because it does have a standalone concept of something that you're referencing. And then we also added a new concept for defining parameters for your resource claim. These parameters are affecting the scheduling. You may request something of a certain size, but you can also, in the same object, define parameters that configure your hardware. And that becomes relevant when we have a complex piece of hardware that needs to be initialized in a certain way in a vendor-specific format. So I've already mentioned vendors once now. The key point really is that DRA in Kubernetes is just a framework. And it enables hardware vendors to extend Kubernetes by writing DRA drivers. And these DRA drivers are then responsible for the hardware, and also for the user-facing interface. How to specify parameters depends on the hardware that you are asking for. It has been an alpha for a while, and we've been trying to get it to be there. I got some feedback from the community and to clarify why that has been controversial. We look at a little bit of the background, how it works at the moment, or how it was originally meant to work. The original idea was that we wanted to keep logic and knowledge about the resources out of Kubernetes. It seemed like a daunting task to teach Kubernetes how to handle arbitrary hardware. So we tried to hide that behind that interface that the vendors implement. The DRA driver controller basically takes those parameters that it gets from the user, and it has its own way of tracking its own resource availability on a node, and it has all the matching. And the Kubernetes scheduler gets involved. They both need to coordinate between it among themselves because the scheduler is the part that knows about CPU and RAM, the traditional resources, and the DRA vendor or driver knows about resource availability for the more complex hardware. That was the idea originally. The problem with that is that we have to have some kind of communication protocol between the scheduler and the driver. That is this pod scheduling context in the middle. It is a built-in type where currently the Kubernetes scheduler stores some information. I think we have, no, I think we may have to, I'll explain it just based on these slides here. The idea is that the Kubernetes scheduler basically lists some suitable nodes, stores that in the pod scheduling, two slides down, okay, well, then I'll get to that later. This concept is what we've been talking about at previous Kubecons. There is a talk from Kevin and Alexei, a colleague of mine, about building such a driver. We have a repository available that gives you a skeleton framework of an example driver that's actually functional. You can run it on your local development machine, runs in kind.  So you can all see this in action on your local machine. We do have a resource class, the resource claims that are already mentioned. So you can see how it works with this approach. This is a more complete picture of the communication between the Kubernetes scheduler. It goes through the API server, but it was one other idea that we had, but deploying the array driver should be fairly simple. You just need to connect it to the API server, and that's all. No need to configure webpokes or anything that may be cluster specific. It could have been standardized like that and run on any arbitrary Kubernetes distribution. The drawback is that there is a lot of back and forth when scheduler and driver need to coordinate. It starts with a Kubernetes scheduler identifying a port that needs to run. It looks at nodes that it finds suitable. It dumps that information into the port scheduling context. Then the array resource driver looks at that. It replies back, okay, well, these nodes here don't work for me, try something else. There are some back and forth, and that's kind of where the name of this dynamic resource allocation comes from. Eventually, the Kubernetes scheduler can be relatively sure that it has identified a suitable node. It tells all the drivers, it could be more than one. More than one driver can be listening to this port scheduling context if you have multiple resources from different vendors. That also works. They all just need to agree on a node, then allocate the resource that gets recorded in the resource claim status, and then eventually the Kubernetes scheduler knows, okay, now I can run my port. The advantage is that the port never gets scheduled unless it's fairly certain that it really can run on a node. You don't get into a situation where it gets scheduled and is stuck on a node and blocks resources, which is often sometimes that has happened in the past with the device plugin interface where people just try to extend it and then found at runtime on the node but the setup wasn't quite right. The problem with this approach is that the communication between scheduler and DRA driver is not something that works for other Kubernetes components, most notably the cluster autoscaler. The cluster autoscaler operates purely in read-only mode. It sees what the current cluster state is, which ports are not running, and it tries to determine through simulation whether adding a node may help to get the port running. But it can't ask the DRA driver, we don't have an interface for that yet. Not in the virtual design, there were some ideas about plugging vendor logic into the cluster autoscaler binary, but it would have implied recompiling that binary, which is often not an option, or doing remote procedure calls, which are also difficult from a performance perspective. So in the end, after discussions with the maintainers and the community, we came up with this idea of built-in parameters. This takes the same ideas. We have resource claim parameters, but they now have a built-in type in a format defined by Kubernetes. The corresponding resource information uses the same format, the same model, and now we have code in the Kubernetes scheduler itself, which does the matching and tracks a resource allocation and assigns resources from nodes to a resource claim. There's no difference for the user. We still allow a vendor to define his own CRD for the parameters. They just then need to convert those parameters into the built-in resource claim parameter type, and the rest is handled by Kubernetes. So the writing a DRA driver actually becomes simpler with this model with a caveat that it needs to fit into what is supported by Kubernetes in terms of things that you can do with a built-in model. We have some things defined right now in 130, but it's literally just getting started, and we know that more work is needed in that area. And yeah, that's a recap of the old approach, and here's how it works with a new approach. It's basically just the task of a DRA resource driver to produce these resource claim parameters. The scheduler reads all of that information, doesn't need to communicate with anything. It can also do rapid pod scheduling now. It can basically look at one pod, assign resources, keep track of what resources it claimed, look at the next pod and do rapid pod scheduling like it does before with a built-in and native resources. So that is another advantage. Yeah, and the named resource model, that is what we got into 130 as a starting point. And Kevin, I think you will take over and explain more. Yeah, so before I jump into the details of some of this, I just wanna kind of set some expectations about this talk, which, you know, this is a maintainer track talk, and so we're not going through all of the details about how this whole mechanism works. And so if I just back up to this slide right here real quick, if you're very new to DRA and don't know anything about it, we're kind of glossing over a lot of the details, but if you watch this talk from last year in Amsterdam, it gives a very good overview of what DRA is, how it works, and what these different abstractions that we're talking about are resource class, resource claim, class parameters, claim parameters and so on. And so, you know, this is really kind of, the purpose of this talk is to highlight, you know, the state of the project and where we see it going in the future. And so, I just wanted to set expectations on that in case you feel a little bit lost, that's... It's my fault. That's where this is coming from. So yeah, so as Patrick mentioned, you know, the world of DRA, the way it looked in the original incarnation of it, looked something like this, where you have, you know, the Kubernetes scheduler talking with the DRA resource driver and the DRA resource driver is in full control of how these resources get allocated. And in fact, the API between these two is a very simple API. It's Kubernetes scheduler looks at the constraints that it knows how to resolve. How much CPU do you need? How much memory do you need? You know, some of these built in and even the extended resource types that it would need to use to figure out what node a pod could land on. And if it sees a claim, a resource claim, referenced in that pod, it looks up what resource driver that's associated with and just says, I don't know how to deal with resource claims. Hey driver, you figure out how to narrow down this list of nodes that I've come up with with the constraints that I know about and tell me what nodes from that set you might be able to allocate resources for this claim on. And then this process goes back and forth until an actual node is found where you can allocate those resources. And that's where this long loop comes where, you know, scheduling might be slowed down. The interfaces to doing cluster auto scaling don't exist because all this logic is custom inside this resource driver and the built in scheduler knows nothing about this. And so as Patrick mentioned, this move towards a model where we have built in parameters basically allows these in tree types to exist that your driver can advertise its resources to and any vendor specific logic around how you might select a specific resource or configure that resource at the end of the day once it lands on the node can be encoded in these in tree types that the scheduler can actually look at and make decisions on. And so in this picture here, everything that's in green is a vendor specific component and everything that's in blue is an in tree type. And so you can see how, you know, the Kubla plugin will advertise something to the Kubla so it can write this in tree type called a resource slice that the Kubernetes scheduler can now pick up to figure out what resources are available so that it can make this node selection decision without having this back and forth with the custom driver. And so as Patrick mentioned, you know, in 130 for this built in model, we came up with this reference implementation of something called named resources. And if you're familiar with the existing device plugin API, basically what the device plugin API allows you to do is advertise a list of opaque strings back to the Kublet which represent the resources that you might be able to allocate. So in the world of GPUs, you might advertise that I have eight GPUs and the opaque strings that represent them are GPU zero, one, two, up through seven, right? That's the only information you pass back to the Kublet. The Kublet then tracks that as the set of resources that it's able to allocate and then it writes into the API server just a simple count of how many it has back into the node object. So you know, you've passed back these eight strings, Kublet has recorded those eight strings and said that there's eight of this resource type available on this node. And then the scheduler makes all of its scheduling decisions based on that. In this built in resource models for DRA, we're basically doing the same thing except instead of passing back just a string, we're able to pass back a name of a resource and then a set of attributes that are attached to that. So in the example I'm showing here, the instance that I'm passing back is called GPU zero. That's similar to this opaque string that I would have passed back in the traditional device plugin but now I've got all these attributes on it. So I've got an index of zero associated with this device. I've got a UUID with this long string. I've got a product name of NVIDIA A100SXM4. I say that there's 40 gigabytes of memory on this and so on. And so you can kind of imagine how this is gonna be used by the schedulers that instead of just having the ability to say, okay, I'm gonna allocate some arbitrary GPU, you can actually do very precise selection on the type of GPU that you want, right? You can match against these attributes based on some selection criteria for what type of resource that you're actually trying to get access to. And so people have worked around this today by using some combination of node attributes and other mechanisms where you basically have to have a homogenous set of devices on a node. And if you have that, then you can use labels on the nodes to try and get access to a specific type of GPU because you know that if you land on that node, that's the only type of GPUs that are available there, right? But with this model, we can actually do precise device selection which will kind of automatically enable you to have different types of GPUs on the same node at the same time. And again, using this analogy of what the existing device plugin API looks like, if you're familiar with that existing device plugin API, you'll know that there's a list and watch API call that exists in the drivers that are written for that which allow you to stream this list of devices, as I mentioned before, as opaque strings back to the cooblets so that it can update the node with how many are available. And in this new structure parameters model, it's a very similar thing except instead of streaming back this opaque list, you're streaming back an entire model that looks like what I had on this last slide. You're streaming all of this back and instead of just account being made available to the scheduler, this entire object is being made available to the scheduler so that it can do this precise device selection based on that information. And yeah, if you send this once when the node starts up and then if something goes wrong, like some resource goes unhealthy or whatnot, you can update, you can send an update of the stream of things that might have fallen off the bus or gone unhealthy for some other reason. And so if we go back to this picture that I had before, the cooblet plugin of the DRA driver basically satisfies this part of the picture, right? So you've got your DRA resource driver, cooblet plugin advertises its resources through the streaming API to the cooblet. Cooblet uses that to write a resource slice into the API server and now the scheduler has the ability to look at this information when it's trying to make scheduling decisions for your pod. On the other side of that is this notion that Patrick also mentioned of introducing this entry abstraction called the resource claim parameter object. In both original DRA for opaque parameters and our built-in parameters model, we do have the notion of allowing you as a vendor that's writing your device driver to introduce vendor specific claim parameters. And that's what you're seeing here on the left. This is the claim parameters object that our GPU driver for DRA implements. And it allows you to specify both selection criteria, meaning how can I get access to a specific type of GPU as well as configuration criteria, meaning once this GPU has been allocated to a pod and it lands on a node, how do I want that GPU configured for use on that node? And so you can see it's divided into two sections for that. So at the top, you can see that you have, in this spec, I want account of one GPU that follows the selector expression, saying that I want the, basically I want a GPU that has A100 in its product name and it must have less than or equal to 40 gigabytes of memory. And once it lands on the node, I want it configured for anyone that shares access to this GPU. I want it to use time slicing with a long time slice configured, as opposed to a short time slice or a medium time slice. And so the only job then of the controller piece of a DRA driver that you need to implement, as opposed to the opaque parameters model where the controller had to do all of the logic for actually allocating, because the scheduler didn't know how to do that. Now all your controller needs to know how to do is to take this vendor specific claim parameters object and translate it into this entry generic representation so that the scheduler knows how to actually operate on that. And the way that it does this is that it generates that claim, the resource claim parameters object and then it puts a back reference in that to your original resource claim object so that the scheduler knows how to find this to attach other pieces of information to the resource claim parameters object. And so there's an explicit generated from section that refers back to your vendor specific claim parameters object. There's also a generated cell expression for selection. So the scheduler knows how to interpret this cell expression. So if you're not familiar with cell, it's a, I don't know how you would, how do you describe cell? A simple expression language that can be evaluated in constant time, it's strongly typed in this case. So it evaluates always to a Boolean and there's some validation going on that you are not calling something that is not defined in this particular context. So it can be extended. These attributes.string, this is something that comes that we are adding in this particular cell environment to grant this expression access to the resource attributes. So basically what we have expressed over here can be translated into a cell expression. And what Patrick mentioned with the attributes is that in the resource slice that I showed an example for before, there was a set of attributes attached to the resource and you can basically match on those here. And that allows you to do this precise selection of the GPU that happens to be available for what you're asking for. And then any vendor specific things that the resource claim parameters object itself doesn't actually care about but you need available on the node when you go to actually allocate these resources, you can tack those onto the end in this specific vendor parameter section. And then from the perspective of the resource claim parameters object, this is just an unstructured type that's tacked on there and then you have to reinterpret this once the node itself starts to allocate resources for this. And so yeah, if we go back to this picture now, this is kind of the top half of the picture where the vendor specific controller sees one of these vendor specific claim parameters objects created, it generates an entry resource claim parameters object that the scheduler that knows about and then putting this all back together. Now the scheduler has all the information it needs to select the node containing the requested resources alongside all of the other constraints that's resolved for any other types of resources that it has. One of the earlier slides we pointed out that we have an example DRA driver repo where you can go in and play around with some of this stuff. We haven't updated that for structured parameters yet but we plan to once kind has an image that's been released for 130. So I mean, 130 is not even out yet, right? If you wanted to start trying to play around with this you'd have to compile it against master of Kubernetes but once kind has an image that's released for 130 we will also coincide that with having structured parameters implemented in this. That said, I have already implemented structured parameters for our NVIDIA GPU driver so if that's what you're interested in potentially playing around with and seeing how it works you can go to this branch and see what changes were made from the opaque version of this implementation. And speaking of which, even with this very, very simple model for named resources, I have this document that I put together a few months ago which called NVIDIA GPU use cases for dynamic resource allocation where I outlined 12 use cases that DRA is able to solve for GPUs that you can't do with the existing device plugin API. And even with this very simple named resources model we already cover six of those 12 use cases which is actually a pretty good number given how simple this model is. And these are the, if you watch my talk from KubeCon last November these are the same use cases that I identify there where I go into lots of details about how DRA works and how specifically it maps to the different problems we're trying to solve with GPUs. So I encourage you to check out that talk if you're interested in that. And so these are those six, actually the full 12 use cases of what's supported and what's unsupported. So I just wanna really quickly name each of them so that you see the difference between what is supported and what isn't. So the things that named resources actually gives us the ability to do is control GPU sharing, right? So I can create a claim, I can have two different containers point to that claim and now they get shared access to that in a very controlled way because the claim is where this resource is bound to. I can also get GPU selection via complex constraints. That's this whole selection mechanism that eventually gets translated into a cell expression. I can still do that with this resource model. You can have multiple GPU types per node. I can have an A100 and a T4 sitting next to each other. And as long as I put my selection criteria together appropriately, I can pick one versus the other. You can still do user-driven time slicing support across a subset of GPUs. That's this vendor specific information that you tack on the end. At the node level, you can still interpret that the same way you would have in the opaque parameters model. And so there's no changes there. Same thing with MPS. MPS is the, I mentioned this this morning in the keynote, but it's a way of doing space partitioning instead of time partitioning. And you can still take advantage of the MPS support because again, this is a node level thing. We just tack on to the vendor parameters at the end of our resource claim and they just get passed along to the node to actualize them. And then the last one is dynamic swapping of an NVIDIA driver with a VFIO driver depending on intended use case of the GPU. So this is for being able to support virtual machines like Kubevert or Cata need this kind of capability so that you can on a GPU by GPU basis say, hey, this GPU is gonna be injected into a virtual machine? Cool, I want that governed by the VFIO driver rather than the native NVIDIA GPU driver that's sitting on the host. And these other six are unsupported at the moment. But that said, by 131s, one release later, we already have plans to support the majority of these just within the next release cycle. So we'll be able to support 10 out of these 12 where we can do some of the dynamic allocation of MIG devices, we can do MIG device alignment, subdivide MIG devices, basically support partitioning of devices rather than allocating out just full GPUs. Which is still unsupported, but we do have plans to support fairly soon. We have designs in place, but we're still trying to wiggle out the details of that is the ability to do custom policies to align multiple resources such as GPUs and NICs or even between two different GPUs, making sure that you have the optimal connection with in terms of NVLinks and NUMA alignment and things like this. The last one though, where you can do very, very custom application specific policies for how GPUs are allocated across containers and pods. I don't see how we'll ever really be able to do this with structured parameters. This is, it's possible with the opaque parameters model, but I really don't see how we're ever really gonna be able to do this with structured parameters because this is the type of thing where you might have an application that says, I have two pods, if those can both fit on the same GPU on one node, give them access to that same GPU. If there's no single GPU where these could run, but there's two GPUs on a node where they could each get one of them, give them each one. If that doesn't exist, but there's two nodes that have a GPU that could satisfy one of the two of them, great. Run them on those separate nodes, but also allocate an RDMA device that can allow them to communicate very quickly between each other, right? And with opaque parameters, you can actually write a controller that encodes all of this logic and does what I just said, but there's no way we're gonna be able to do this in a generic way. And so we need to think hard about whether we wanna be able to support those use cases that they just described or not if we ever wanna try and get rid of the opaque parameters model going forward. And one thing to point out that at least in this move from opaque parameters to the built-in parameters model that we have today, from a GPU's perspective, from the user of the GPU driver's perspective, there are no changes needed to migrate from DRA with opaque parameters to structure parameters. So if you've already started playing around with this a little bit and have been experimenting with it, if you decide to try and play around with the built-in model and you're only doing things with one of those first six out of the 12 use cases, nothing should have to change from your perspective in this migrating to 130 from 129. And I'll let Patrick then finish up with this last slide. Yeah, so the question that we discussed at the Copioletti's Contributor Summit really was, can we promote something to beta in this year? Which is fairly aggressive. So for 131, yeah, we kind of at the end decided, yes, we can. We just need to figure out exactly what it is. What's the scope limit that we can achieve in 131? So many of these enhancement that we still need for some additional use cases that needs to go in. Then we can finalize the API structure parameters, will be the default mode. And then we kind of keep the rest of the functionality, the core or traditional, the DRA, depending on how you want to call it, hidden behind the second feature gate. In Kubernetes 132, then ideally we have some more feedback, we know that it works. And then we just flip the feature gate for structured parameters. That becomes beta in 132, hopefully. The rest will still be there because we still see cases where it's useful, exploring additional controller logic that is where we need for pod scheduling context. So this will still be available. And then going beyond that, we need to really think hard about whether we can still support it or whether we arrive at a structured parameter model that is so sufficiently capable that it works well enough for the majority of use cases and then we might drop the rest of the code because the concern of the maintainers is clearly the complexity that we are now adding to Kubernetes, that this is not maintainable in the long run because there are a lot of if check, if else cases now in the scheduler to support both of these models. And that just may be too complex for the future. But we are going to discuss that when we get to that point. Right now, the focus is 132. There's a lot of support in the community because we all agree that Kubernetes needs to do something that makes AI training and inference work better natively without any hacks that you might have to use with device plugins. So there's a strong support from the community for the structured parameters. And I'm hopeful that we can do it. And that's it. So I think we do have time for questions. Five minutes. There's a microphone over there I see. So I have a question about how will this work with network devices where you can have, say, a device that can only take one connection at the time? So will the scheduler be able to know that it's the same device that it exposed on different nodes and ensure that it isn't used at the same time by different nodes? So that would be a network attached device that gets connected to a node. This is one of the use cases where we are currently still exploring how to use structured parameters. There's no concept for publishing that such a resource exists in the cluster in the first place. That's one of the missing pieces. And then the logic of, okay, so how do we allocate it and when do we enact any kind of cluster reconfiguration? Does that happen when a pod starts to run? That may work with a current model. So you would have to have a demon set that knows how to reconfigure that network attached device. That might work. But yeah, it is a use case that currently has taken slightly the backseat to just get node local resources to beta. Okay. But the core of the traditional DRA is still there. So if people want to explore such use cases, you can, you just have to use the traditional DRA with your own controller. And then it, yeah, that's your limitation. You don't get cluster auto scaling because we don't have a solution for that. But you can explore. You can do prototyping. You can come back with your use cases to the community and say, okay, this works perfectly for my network attached device. Let's figure out how to do the same thing with structured parameters. That's ideally the result of all these discussions. Have this been designed with multi-tensi in mind so that you can use resource quotas? We have some very simplistic idea of doing quotas at the moment. It's like volumes, you get both, you just count the resource claims per name space. That would be fairly simple to support. I do have a PR pending for that. We didn't merge it yet because it wasn't sure whether it's sufficient. It probably isn't because one claim can be for some very cheap hardware or it can be a big GPU. We need these structured parameters to make the quota mechanism more capable and more specific. It is probably something that can be added but for the sake of, yeah, having a reasonable scope feature set, we are not currently planning that for 132, to be honest. It's also worth pointing out that with the opaque parameters model, you could bring along your own custom way of doing quotas because you have full control of if you want to allow the allocation to happen or not from within your controller. And we were planning, until the whole structured parameters discussion started, we were planning on shipping our own custom quota mechanism along with the Helm chart that deploys our driver. But we just never bothered doing that because we've kind of pushed things more towards our efforts towards the structured parameters model now. All right, thank you. I have a quick one if there's time. What about scheduling? Once you have scheduled the part and you have the resource slice, do you optimize like we do with persistent volumes where it was scheduled, perhaps with some labels and the nodes? I like topology. Not sure whether I get the questions though, you. So if a deployment gets some resources, GPU, and you need to reschedule it, do we optimize so that we don't need to provide the whole list of nodes and do the evaluation again so that we perhaps put it in the resource slice resource which node it had previously? So there is no rescheduling at the moment. That is not supported by Kubernetes itself. So we are bound by what is supported here by Kubernetes. Once a part has been scheduled, it's bound to that node. It can only be deleted if it cannot run and then we rely on an app controller to recreate the part and that part will get scheduled again. There is a cap in flight where someone is proposing to allow rescheduling. Basically, Kupelet can mark that part as not suitable for this node. Try again elsewhere. But this is a new concept in Kubernetes. We don't have that yet. All right. Last question. I'm afraid we are at the end of the session. Yeah. You mentioned that the resources you define with the dynamic resource allocation will be used for scheduling only. But is there a plan to use them also for setting a hard limit for the resources like the memory and the CPU count and to evict the ports if they overpass their limit, for example, in the user of GPUs or network? So we don't really plan to touch anything with CPU or RAM at the moment. There are some experimental DRA drivers that add additional constraints about which CPUs may be usable for a port. But it's only really piggybacking on this whole effort of having a custom API and then doing something special in their DRA driver on the node, but it's not a main feature that we are trying to support. Okay. Well, thank you.