Hello everyone and welcome back to Ultimate Epic Battle Simulator 2! Now not too long ago we did this exact same battle, but there's more new units, I've downloaded more mods, I've customized some of them to make them more realistic to the movies. We also have, of course, a massive wall that is supposed to simulate Gondor, of course. So up here we have the Arches. Look at them there. Glorious, the Gondorian Arches. Also we've got Gandalf up here. Gandalf is... Gandalf? How much desire to speak with you? There he is! Look at him just hiding away there. Beautiful, beautiful. Okay, so what's great about this is that they can run up and down. So what we're going to see at the start is the Gondor Arches are going to fire at the orcs, and then when they get too close, then they're going to start running down here. And then they're going to enter through this bit. And this is where the orcs are going to sort of charge into them. But meeting them face on is, of course, some Gondorian swordsmen. But, and only do we have those, they're treading off into the trees over there. We have these guys over here. These are like royal Gondor soldiers. They're a lot stronger, and I don't know. I was like, you know what, we're going to put some new units into this game. Hell yeah, this will look awesome. Just sort of flesh out and make them more realistic. So let's go on to the bad guys over here. So we have some trebuchets. We actually have some orcs now. I mean, I think they're just orc eyes with the helmets removed basically. You've got arches. You've got regular swords. You've got some Mordor trolls. Yes, they look glorious. And somewhere in here is the Witch King themselves. I don't know whereabouts they are, but they are hiding in here somewhere. And they are incredibly strong, so when they get into the battle, it'll be pretty tough. We have the Rohirrim, a mix of cavalry, and of course, foot soldiers. Now, there is Theoden, or at least there was Theoden. I decided to switch him out because he kind of just looked like a regular soldier, and I never found him when I did some tests. And I was like, well, I could have like either Theoden or Catapults for the good guys. I'll take the Catapults for the good guys. And of course, we have the army of the east over here. With some elephants and some spearmen. These guys, I didn't realize automatically, they're on like 95 or 99% arrow projectile deflection. So that's why when we did these last time, the arrows were just absolutely bouncing off them. So that no longer will happen, but I did bump up the amount of foot soldiers that they have as well. Ah, there they are. So here's Gimli. We have a newly updated Gimli. He doesn't have the thousand-yard stare that the last one had. Aragon and Legolas. Now when the battle starts, they should get into the fray quicker, because they run faster than the ghosts of what the good guys see. As soon as we click, start the battle, these guys are going to start firing. Are you ready? Let's go! Oh, let it out folly after folly. Zoom, zoom. Oh, it's so good, man. It's so good. Look at that, they're charging towards. The Catapults are firing.  I did increase the hit points of these guys. They are set to hold. So there's only a couple. There are some actually in the building, but they are able to fire through the building. So that is interesting, too. Right, how we doing? How we doing? Oh, they're getting closer, guys. They are getting very close. It looks so cool, man. I love this. It's brilliant. Alright, there's some trolls you can see. They look like stick men from here. Oh, no! You've got the Catapults from the bad dudes from Mordor. Oh, they're moving in. They're moving in. They're running down. Where is Gandalf? Gandalf? Where is he? He's somewhere here. Well, they're all trying to run down. Look at this. This is so cool. Just put some, like, All the Rings music on this. And there you go. You've got a whole scene ready to go.  Oh, how are we doing? Have they reached it? Oh, yes. Oh, my God. Oh, hello. The trolls in the front. Kind of not what you want to see. And there is just massive amounts of rocks being hurled at the entrance. Just absolutely sending them flying. Oh, and sending me flying, too. I think we've got some of the Royal Guard coming in. You can tell because they've got banners. I don't know if it's the best tactic to be coming out, but, hey, we'll see. Oh, is there someone there? Looks like they were hitting somebody inside of the hole. Right, but is Gandalf here? Gandalf should be filtering in somewhere. I'm reading out to Shuhou's the wall, holding up. A majority of people have decided to leave. Oh, no! No! Oh, my God, what a way to go. Falling all the way down. Oh, these guys are stuck. Oh, because there's a catapult in the way. Oh, no. Oh, no. The catapults are set to hold, so, of course, boom, these guys, even if they want to go down, they can't. Oh, the elephants are on the horizon. But where is Rohan? They have left them. Oh, God. Oh, God. They are just falling. How many dudes? How many kills? I'm assuming it's like 2,000. Yeah, 400 kills for the bad guys and 1,700 kills for the good guys. Not looking good. They're really going to need the armies of the undead and Rohan to come help. Oh, the orcs have turned around. They're actually facing down, Rohan. Oh, okay, that's what's taking them so long. Whoa! Half the forces turned around. It's just stopping them completely. Oh, no. Oh, this is not good. This is not good at all. I mean, there's a lot of them. I think they'll get through them, but this is putting a major scupper in the works. Oh, the infantry's coming through, clearing out the arches that made their way around the orcs. And they should really help them. They're down the DPS. Yes, well done. Well done. They were doing their lads. They're trying to get in, but they seem to... Whoa! Whoa! So many people have died to you! What's going on? Are they being crushed by the elephants? I'm really not too sure. They're still firing rocks up here. Oh, there's... Whoa! Are you scaled it? Oh, they're sort of glitching it to get up here on this weird barricade fence thing. Anyway, how's the battle over here going? Oh, God. Oh, they're actually getting in now. Um... Oh, no. This is not so good. There's still no Santa Gandalf. He's in here somewhere. Oh, God. Just the amount of projectiles that are coming in. Will there be anybody left by the time Rohan comes to the raid? There's like a single archer or maybe a couple of archers just at the back to get some help. But with the big trolls here? Yeah! Not gonna be too helpful. Now, supposedly Legolas and Aragon... Oh, here we go! Yes, there's Aragon! But where's Gimli? Is Gimli not here? Or is he in there too? I can't see him. No, it's just Aragon. Just taking on everything. Oh, there's Gimli! There's Legolas! He's got the arrows on the go. There we go. I mean, he's basically a powerhouse in himself. Wow. I think I set him to 100% accuracy so he is just rattling. Oh, the kills! The damage, like, kill, kill, kill, kill. And the undead are coming and firing their explosive, glowy green skulls. Helping out those guys. But where's Gandalf? Oh, they're kind of moving back. Oh, there's a lot of dead dudes here. Is that the catapults? Oh, my God! The elephants are dying as well. I don't even know how that's happening. But how long can they hold out? Oh, God, there's not really that many of them. There's even, like, a little hill in here. Oh, I think I see them. I think I see them. I see Rohan now. Yes! Slowly coming to the aid. The undead are already here, though. And they're laying down the smackdown on the elephants. Oh, wait, what? Did they...? No one's dead, are they? I don't think they're dead. I hope Aragon's not dead. Oh, hold on. There's a huge pile of bodies here. I feel like... Is he in here somewhere? He might be in here somewhere. I think he is. Or he was. Oh, wow. Oh, you cannot even tell what's going on in there. You really can't. Oh, there he is! There's the red gimbals. They're gonna go. They're still there. They're still kicking. They're sort of splintering up the faction now. People are turning around to take on the army of the undead. How about Gondor? How's Gondor doing? Oh, no. I saw that rock go all the way through there. Not having the best of times. How is the wall doing? How's the wall doing? Oh! Oh, there's bad guys on the wall. There's an orc on the wall.  Oh, these guys are still stuck because the cannonball can't seem to work it out. Why is there so many feet here? Yes! Finally! Lay down to support the cavalry's com... They have just not been stopping this whole time. Where is Gondor? We'll do cinematic camera and hopefully we'll find Gandalf. Oh! Oh, there's the witch king! There he is! See, he does exist. He is there. I would never have found him. We need to rely on these cameras because without them, I don't know what I would do. There's the battle there of Rohan versus the orcs just running in. But there is still so many that are going to get through. Oh, the cannonballs for Mordor are still working. Oh, put the army of the undead.  That concentration fire there. I think this is going to be the witch king. It's going to be the witch king somewhere. He's in here somewhere. Oh, yep! He's slowly killing them, but he is there. He is taking an absolute pounding. Oh, just killing the cavalry. Can we see him? Can we even... There he is! Look at that! You can just make out the figure of the now school king. Tell you what, he's distracting. He's distracting the army of the undead. Slowly killing them. My God! Yeah, even all of Rohan's here trying to... They all want to slay him. They want the glory. Rohan's still coming through. There is still a lot. And there's loads of these dudes. Oh, loads of the inventory. Inventory, inventory! The inventory's coming. The backpacks are here. Yep, they're just waiting for their turn. Oh, they're finally getting around the side. Yeah, there you go! Making good use of the maneuverability that cavalry offers. And now they have the crows surrounded absolutely. Yep, there you go. Just taking the flags. Oh, he must be dead! He must have fallen! And finally, will there be relief for Gondo? There is still some dudes here. Just a few. Okay. 15,000 kills for 44,000 kills for the good guys. Only 4,000 of the bad dudes left. And now the army of the undead is just absolutely mowing down the bad guys. Have they done it? Have they done it? Oh, there's some orcs here. There's still some orcs coming from the side who don't know what they're doing. What are they doing? They're trying to attack something. Oh, it's Gondo! He was in the corner leading the way!  Oh, there you go. Look at him go. Yes! Brilliant. Oh, and Gondo comes to his aid. Oh, my God. That's it! They did it! Oh, mago! How many? There were so many 5. Whoa! Hello, that was a little bit unfair then on the bad guys. Even though the bad guys kind of stopped Rohan coming to the aid quicker. Okay, hold on guys. Let me adjust the numbers. See if we can make it any more even. Okay, guys. Here we are. There is now 100,000 orcs. That's an increase of 30,000. Also, I've taken 5,000 away of the undead. So now there's only 5,000 undead. So technically that's 35,000 extra troops. Hold the bad guys. You know what? I want to keep an eye on Gandalf. Let's do it. Let's keep an eye on Gandalf when you can barely see. Oh, God. Oh, I also I started them a little bit closer. So they should all be running down instead of running backwards for Rohan. I'm really not too sure. It looks like that's what they're doing. So that's good. Oh, there he is. Go on, Gandalf. Yes! We need to see where he goes. So come on, guys. I need to do the fighting.  That's not exactly how Sir Ian McKellen taught me. You know what I mean. Okay, yep. That's looking good. They're not running back for Rohan. They're going perfectly forward. Oh, someone got shot here. Gandalf, you know, he's a polite man. He's not going to just shove you out of the way. He's going to, oh, whoa. Hopefully there he goes. Look at him run. Come on, Gandalf. You got this. Yes, yes. Run down. He's going to join the queue. The queue for fighting. That's brilliant. Off he goes. Oh my god, there's already so many people. And there you go. That'll be Gandalf for the next 10 minutes. Just waiting to get into the fight. Are they already here? Of course they're already here. It looks like, are they attacking? What's happening here? It's like they're after something. Oh, there's a condo dude over here. Oh, it's just being annihilated. Oh, you know what it is? It's because of these. They're being thrown in. Dudes aren't dying. And then they're just getting, like, laid into. They're not dead when they get flung into the air by the catapult shots. Oh, maybe they are. Oh, no. It's absolutely not. Niko, did he die? Oh, bugger. You really just look at the old feet and you'll be able to find a few gondor soldiers of the unfortunate few that are being hit. And yeah, they just run straight through the horde and get absolutely obliterated. Okay, so I don't think anyone's ran off. I could be wrong. No, the horses, they're just straight going. Okay, this is good. Rohan's going to get there before the army of the undead. That's the tactic. Okay, horses are coming through. How's the wall doing? Who's manning the wall? Okay, we've still got some blocks. So that's good. We've got a dead dude there. The catapults. Oh, they are firing. Oh, that's good. I was hoping that they still would. There's no reason for them to stop. But they apparently are only firing when they choose to. You know, you can't fight all the time. Hold on. Hold on. Well, what's going on over here? What's going on over here? Wait a minute. Oh. Oh, hold up. Did they use the other entrance? Did they came through here? They did. Oh, my God. They've used the little goat path to get through. I didn't even know you could do that. Okay. Okay, because they were so big. They actually kind of went and climbed around there. I've never seen that happen before. Oh, the few brave cavalry soldiers kind of went in by themselves. That was not the best of strategy, we'll admit. But here, oh, look at them go. Oh, yes. This is it. Somebody was in Calvary's not the best in this game. But because for some reason Ultimate Epic Battle Simulator 1 had way better cavalry mechanics. They would charge in, they would run things over. But this one can't seem to do it, but the elephants are coming in. Oh, this is not looking good for the cavalry. Oh, oh well. There you go. Oh, is he dead? Oh, he's skating for a little bit. There you go. That's not what you want to see. These elephants are very, very good against Rohan. I mean, you've seen the movie or you haven't. Spoilers, I'm sorry. But Rohan. Rohan is big. Rohan is vast. Look at this army. There is so much to come. The army of the undead has not arrived yet. So Rohan's going to just have to try and take on these elephants. I think, hold on, hold on. We might be able to take control of one of these guys. Look how cool this looks, dude. And look at this. This looks amazing. Rawr! Yes! Rawr! There we go. You know, I've only got one kill so far. Rawr! Yes! Come on, ponies! I mean, I'm kind of helping them, I suppose. Because then they can all hit me. But damn, I only have two kills. I have nothing. I have no kills. All right, we'll even be. Go on then. Off you pop.  You see that? He went, eh, with his leg. It's not good. It's not good for the horses. But there is a lot of them. There is an absolute ton of ponies coming. As well as infantry. There is so many infantry as well. Okay. Okay, we've got the archers here who are, you know, they don't either way they're firing at Rohan or they're turning the other way and they're firing at Gondor. But, up until this point, the elephants have just been having a great time just smashing everything. Now, army of undead is here. Yeah. Yeah. And they just annihilate everything.  I don't see Legolas and I don't see Aragon yet. Okay, how is the battle of Gondor going? How we're doing? Okay, okay.  There were so many of them. Jesus. Was that all from here? Did they go and like charge from here? I don't even know, man. Nah, it's crazy. Anyway, anyway, we still got this battle going. I'm trying to see if I can pick out Gandalf. He's in here somewhere. He's in the crowd. If he's at the front he would probably stay at the front. Oh, oh, is that Gandalf? Nope, definitely not. Okay, here we go. Oh, there they are. Oh, the elephants is absolutely going down there. Beautiful, beautiful. Is that all the elephant? Oh, no, no, hold on. Oh, look at it. I don't know where the witch king is. He could be over there. How about we do cinematic camera? Look at this. Look at this. Oh, just a green haze in front of the elephant. Just taking hit after hit. There's so many of them as well. Yep, there we go. They're just sliding. Okay, what's this? What's this army? Oh, these are more orcs. They left that side completely open. Although Rohan's coming back over here. Oh, no, Rohan's being sandwiched. Oh, my God. Where's Rohan? Rohan has fallen. These are the last remaining fighters. Oh, I think that's it. I think that's it. They completely annihilate all of Rohan. No. Yeah, they're all dead. All dead. Oh, wait, hold on, no. No, no, no, no. You got these guys being supported by the army of the undead. Never mind, never mind. Oh, saying that though. These Rohan soldiers are also falling pretty damn fast. Oh, he fought violently. I think all of Rohan is dead now. Yep. That's a... That's worrying. Unless there's more Rohan over here. But I don't think there is. No. I think Rohan's all gone. Okay, okay. Maybe having 35,000 difference. It's definitely made the difference. Oh, the Witch King. He's in there. Oh, that's bad. Oh, hey, who's this? Oh, it's Legolas. Look at him go. Another catapult for the bad guys. They're pulling more forces away from Gondor, so that's good. There's still so much going on there. I don't know, man. Maybe they could win. Random dude. Go, random dude. And catapult with... Okay. Is that all the ghosts? Oh, no. Oh, no. They've got completely preoccupied with the Witch King. Oh, this isn't good. Oh, I don't know where those guys are. Uh-oh. Uh-oh. We still have Giminy. We still have Legolas. We still have Aragon. We still have three soldiers left for Rohan. There is hope yet. Oh, hold on. What's going on over here? Legolas! Oh, who's this? Oh, it's just Legolas. Oh, my God. He had a whole pile of himself. He's dodging the arrows. Oh, it's Giminy as well. There we go. Just killing the orcs one by one. Legolas. I don't know where Legolas is going. He was trying to help them. And now he's just running into a flurry of archers. What's going on? Are these more archers? Oh, they are. They're all just taking potshots at them. Oh, they're dodging rocks. Oh, the rock hit everybody's road. It's okay. Legolas is alive. He's alive. Oh, look at them. They came out. Yes, they're able to run out now. Is Gandalf there? Is Gandalf giving support? Is that how they're able to do it? I don't see him. I think he's still at the back somewhere here. Oh, my God. The arrows. The amount of arrows. Which are just being flung over here to Giminy. Giminy. Is that Aragon?  I feel like the bad guys are going to win because there's just so many of them, but we do have more heroes. The Witch King is dead than the normal dudes. However, the ghosts are also falling. Because there's like half the number and there's just so many of these orcs. Yeah, look at them go. Kind of being overwhelmed there. And then some of the archers are turning around and firing at the ghosts too. So there's only a handful of these ghosties. Giminy slowly killing them one by one and so is Legolas. Just shooting them and he's like, Hey, Surely has good rate. I don't even know what's going on, man. There you go. You can fire. You can do it. Just, you know, maybe it just gets a bit bored. So many arrows. Oh, oh, no. Oh, no. Oh, ghosts are gone. Ghosts are completely gone. Okay. Yeah, that's it. That's the end of the ghosts. They're figuring out where they want to go. Yep, they're going back to Gondor. Yes. Look at this. There's so many though. You can't just stretch your arms. Now that you've got one arrow, two arrow. Come on, there's so many down there. What are you doing? Oh, yep. They're about to break through. They're about to break through. Oh, no, no, no. Some swordsmen. Some swordsmen are coming through. They're trickling. They're trickling. Oh, they really need this. Oh, it got up. There he is. Damn it. Yes. He's doing it. He's got his own little pile of bodies here. Oh, God, how many left now? 164 for 20,000. He's doing brilliant. He's doing brilliant. He's just... He's a ball of red rage at this point. Oh, God, they're through. I knew that was going to happen. Yeah, as soon as those soldiers fell, the arches were going to be no match. Oh, oh, and now the last stragglers. Who's your boss? Oh, they're trying to get the Gandalf in the corner. That's what they're doing. Now Gandalf's being absolutely into...  No, give me! No, he just died! Oh, now it's Legolas. There's only two left. Yep. Six ag, six ag strats. Six ag. I got 287 kills. Whoa, whoa, whoa, whoa. Slow down, slow down, son. Slow down, son. Oh, God. Oh, no. Uh-oh. Oh, hold on. I made a terrible mistake. Maybe I can glitch up. Maybe I can get up. Maybe I can get up. It's somewhere here. Oh, no, no, this is not good. I can't play runaways. Ah! Oh, I got shot by an arrow there. Okay, here we go. Just move a little bit. And off they come. And they're about to come around the corner. Get ready. I just want to get round. I just want to kite them. I just want to kite them. That's all. Oh, God. Oh, they are good. They're good runners. Oh, no. Oh, no. Oh, God, no. Oh, no. Who did we got? Uh-oh. Can't help. But luckily we're in a bit where we can't... I don't think we can be attacked by the arrows, so that's good. Because there's a crud ton of arrows up there, Gandalf. But I've got Gandalf with me. Hopefully we can scale the wall with a body of orcs. Oh, there we go. Back down. It's been clever. Oh, has he? I don't know. He's a bit like me. Is it Gandalf time? Is it legit just me? The archers can't get me here. And they're just... Oh, they seem to be just running off now. Oh, yeah. No damage. Oh, oh, there's some...  Like, oh, okay. I guess I've been shot. I'll die. It must be part of the AI. Oh, God, Troll. Troll, no. Oh, bad Troll. Oh, Troll's dead. Troll's gone. Troll also did it. There we go. Go on. Up you get. Up you get, lads. Go on. It's just like that scene in Helm's Deep. There is so many of them. Where are all... Oh, they're coming from the other way. Okay, go, go, go, go, go. Oh, these guys don't run off at this point, though. That's interesting. Oh, oh, they came from the other way. I didn't see that coming. Oh, no. Oh, no. Oh, God. Oh, God. Oh, God, I should have just stuck to the stairs. Should have stuck to the stairs. Anyway, guys. What do you have left for us to, you know, come to his demise? And hopefully you'll enjoy that video. There's a lot more going on that time. We'll always want, if we do it again, make it more interesting and more things in a new scenario or something like that. But if you've enjoyed this video, guys, leave a like and until next time, I'll see you guys later. Oh, bye-bye.


Yeah, thank you. So I'm just going to do a three-minute intro on why we created the program and how it's going so far, and then hand it off to do a lot more details. CNCF is 3 and 1 half years old. In that time, I think the most impactful program that CNCF has created for the cloud native community is certified Kubernetes. And so this is a way of certifying that every implementation of Kubernetes out there supports all of the necessary APIs. And so if you have a workload that runs on one version, it really should run correctly on another. Now, in the real world, our conformance tests do not yet support 100% or cover 100% of APIs, and even on covering 100%, there's then a lot of subtleties about how we're exercising and such. And so it is a program that continues to improve and that we make significant investments into. But I would actually compare us against some of the most successful certification programs ever, say Wi-Fi or Bluetooth or Android applications as being three, and the fact that we've gotten the entire industry. So all of the biggest public clouds and smallest public clouds, all of the distributions that we're not just getting a part of it has really exceeded our kind of wildest dreams when we launched this program just a year and a half ago. So we're up to something like 89 or 90 certified Kubernetes implementations. It's all on our website. We have this logo that you get to use. One of the big carrots that we offer is that if you want to use the term Kubernetes in your product name, like Google Kubernetes Engine or I think it's like canonical distribution of Kubernetes, you need to be certified Kubernetes. So the fact that we own the trademark and are then able to offer that usage of it has encouraged a lot of people to make use of it. We divide the certified Kubernetes implementations into three groups. It's the distributions up top, meaning that you can install it yourself. And you can see all the different vendors that we have here. And then we have the hosted. And so these are the clouds. And you can see Baidu there and Huawei and Alibaba and others. And then finally, we have the installers. And we just defined this as saying that they're not really adding any other software. It's all about just taking vanilla Kubernetes and as a way of building it in. One nice thing here you can see in the latest Kubernetes just released this week. CubeADM has a logo now, which it didn't have before. Interestingly, there's five different installers built into Kubernetes that are cops, CubeSpray, CubeADM, Minicube, and Kind. And it just speaks to the fact that this is a very big project. People have different approaches to doing it. But we're really pleased that all five of those are certified Kubernetes, that it speaks to that level of interoperability and compatibility. So we continue to make significant investments in the underlying conformance tests. The program itself for certified Kubernetes really runs quite smoothly. And we can talk through that. But it's all public on GitHub. It is free for members and for nonprofit organizations. And we've had a huge uptake of it here in China. Over 25% of all of our certified Kubernetes implementations are from China. So I will hand it off there. Thanks. Thanks, Dan. Dan has kindly found some time to come and give us a brief update on this. I will walk through what Kubernetes Confluence Program is from the certification point of view. And also, this is an intro and deep dive together in 35 minutes. So it's going to be a little bit of what, from the community perspective, work from the community side of things, so on the development of the ETE tests and approaches. So certified Kubernetes is a software conformance program, like we all know. Vendors can choose to certify their offering with CNCF. And this program has started in 2017. And now, like Dan said, there are more than 80 vendors who are certified on the program. So what does it mean? I mean, CNCF, of course, runs the Kubernetes certified program. But the importance is that most of the world's leading enterprise software companies are now providing Kubernetes on their offerings, and they are certified. That's the great part about this program. Any vendor is invited to have certification. And they just have to follow certain ways to submit the results by running tools. I'll talk about these tools. And coverage-wise, we are trying to make sure that enough of coverage is done so that it makes real value to the offering. So actual software conformance on the vendor version requires them to exercise certain APIs, the APIs that are exercised by the free version of Kubernetes, the community version of the Kubernetes. So that way, we'll ensure that there is consistency and the portability.  So in order to not have vendor lock-in, it's important that you run your workloads on certified Kubernetes platforms. And from the point of view, they have to have timely updates on the conformance program. They have to certify the latest versions of Kubernetes. And I'll talk about how that works. So like Dan mentioned, certified Kubernetes marks and Kubernetes mark are trademarks of Linux Foundation. So Linux established this for a reason. Number one, it provides a quality of the service that is offered by the vendor so that it ensures that the community members are able to accurately describe that offering. It is very easy to actually participate in the program. By self-testing on the qualifying offering. And the CNCF has a participation form, which is a set of questions that you, general questions that you answer. And then with the self-tested results and this form, you submit as a PR to their GitHub report. That way, CNCF will be able to verify your results and validate those results and certify you. And the program is not free for the CNCF members, as well as nonprofit organizations. There is some VSOs here with it. And all the terms and conditions of the program are listed on the CNCF website. I'll show that to you. In order to be eligible certified Kubernetes, you need to be certified on one of the latest to minor releases. For example, 1.13 or 1.14. I know that 1.15 is released last week. Say, for example, the certification is valid for 12 months. And then if you're, for example, you're certified on 1.7 on June 30, 2017. And a year later, on June 30, 2018, there are two more versions available for you, 1.11 and 1.10. You need to be certified on 1.10 or 1.11 to remain certified. And the terms and conditions here actually are part of the CNCF website that we browsed before. So you can actually, if you have access to my slides, you should be able to get to those. In the interest of time, I'm not going to go through that. So there are two ways to run the test. Either you use CubeTest to run the test or use the Sunabai, which is a tool available. And I'll walk through Sunabai in detail. But if you're using CubeTest locally, you're building the ETE test on your cluster. Oh, sorry. And then you set the access path to your cluster and run the test with Ginkgo Focus onto Confirmance. So there are lots of ETE tests, like about 2,000 ETE tests in the KK, right?  We're constantly adding new tests to the Confirmance program, but it takes a long time to add tests to the Confirmance program. I'll explain also why it takes a long time. But generally, it's a small subtest, which is hitting the core API of Kubernetes. So the other option is to run Sunabai. For this, use Standupay cluster on any platform, any offering you have. You need a CubeControl installed, the client. And access to the cluster by proper Cube config. And you need to download the Sunabai program written in Go. And originally, this tool was available from Heteo. Now it's managed by the community. So actually, I ran this a while ago. If you can, can you see my screen? So on IBM Cloud, so essentially, IBM Cloud, I created a cluster of three nodes. And I exported Cube config so I can reach to the cluster. And I did a Go get on Sunabai. I think I did it somewhere here, but I assume that I got it. And then, just as Sunabai ran, and then you monitor, the tests are run. After a while, you will notice that Sunabai ran has completed, and then you would do a, sorry, I think I'm on the wrong window here. So it's run, if you see, Sunabai runs a set of parts on your cluster and running inside these parts, the ETE tests. And eventually, when it finishes by checking the Sunabai status, it's complete. You can go ahead and do a Sunabai retrieve. What it does is it captures all the test output from your cluster and dumps it into a tar file. Using that tar file, you can, these are all the contents of the tar file, which probably have not much interest for us. I expanded the tar file into a directory, and then you can do tail minus 20F on the cluster itself. And you can see all the tests passed. So you submit this result back to CNCF, along with other forms. It's clearly indicated on the CNCF website as a PR. So as you can see, a lot of vendors submitting PRs to the GitHub repo. If you look at any other PRs, for example, IBM has submitted this PR here. It has all the artifacts required by the CNCF. And once the CNCF verifies this, the form and the version that you're testing against in this case is 110. And then the version of the keep control, which gives you the version of the client as well as the server. All the artifacts are submitted along with the ETA log. That can be used to certify the, I'm not sure what's good. So that is briefly about the CNCF side of things, how you certify your version of Kubernetes so that you can use one of these cool logos like certified Kubernetes. From the community point of view, I want to give a brief update what we are doing. Could you just make that distinction of? Yeah. Well, from the CNCF side, they are managing the conformance program from the certification point of view on the vendors on the client side. On the community side, what we are trying to do is how can we build the conformance program itself? How do we make sure that all the vendors have the same quality of service? Essentially, the role is, CIG architecture is the umbrella for governing this from the community point of view. They decide what all the required tests that should be run as part of the conformance. And we have a conformance of project where we have development activity that we'll go through and communicate with other CIGs in Kubernetes. There are lots of CIGs that are involved into the ETE tests. And define the behaviors of the test. And the CIGs are responsible for writing the ETE tests. I mean, we, our conformance program, we do not have the necessary skills for all the associated CIG related work. So CIGs will write the ETE tests, and the ETE tests will become part of the ETE suite. And from the conformance point of view, we will then go ahead and promote an existing ETE test into conformance test suite. So this is always happening. So from every release to the next release, there will be more conformance tests that gets added to the test suite. So it's not as static as we think. So once you pass the conformance, it doesn't mean that you will pass the conformance for the next release and so on and so forth, because there are more tests and more tests right now. I think we have about over 210 right now. The one I showed you was for version 113, where we had about 190 tests. So there are like 20, 25 tests added between 139 and 115. So there are several approaches we take from the community point of view. First we decided that we will concentrate on POTSPEC, because that's a general thing that should work consistently for all the workloads. We have exercised most part of the POTSPEC, but there are still, there are some areas of the POTSPEC that are not exercised yet. So we are working on it. Like I said, the promotion process itself takes several cycles. So we decide that this particular feature is not tested, like POT to POT communication within a cluster is not tested. We write a U2U test in this quarter, in this release. We add that to the U2U test suite. We make sure that that test is not flaky and not slow and so on and so forth. The test has been consistent on our CI. In the next release, that test will be slated to promotion to the conformance test. So what is promoted to the conformance test are guaranteed to work well. That's a couple of ideas for us. So at this point, we're not 100% covered, right? I mean, it's impossible. So we have only 200 tests, and we want to improve the coverage. So of the core features of Kubernetes. So there are several approaches we are taking. A couple of approaches I mentioned here is behavioral driven conformance testing. What in this case we are trying to do is we're trying to look at the API and the fields and see how they can be used in user scenarios and define the behaviors. And then we go ahead and write new U2U tests. The other approach that there is a tool called API SNP, which basically analyzes the audit logs every time you run some tests or workload, whatever, you run on the cluster and sees what all the API endpoints you're hitting. So if you are not hitting some API endpoints during the conformance tests that are run on the cluster, we know these APIs, which are the core APIs, that needs to be hit. So that means we need to write more tests in those areas. So these are the two approaches we are following. And then there is also validation suites proposal right now that's in the works. This is more not towards the conformance program itself, but it is for things that are outside of the conformance program. Like for example, you have functionality like CSI drivers and storage. That's not part of the core features. So we need some kind of a suite that can only test that particular module or networking CNI or not. So that's the idea in there. So these are, again, very public information. So if you want to see this is a cap that is outstanding, you can actually participate and discuss on this cap the idea behind how we are going to do behavioral testing. Similarly, API Snoop is also something that you can see what all the APIs that are running right now on the CI and see the coverage there. So about the conformance test, E2E test itself, like I mentioned briefly here and there, but the merging process of any E2E test is a SIG responsible. Like for example, if it's a networking test, SIG networking. If it's a node test, it's SIG node. And eventually, we analyze that and say, oh, this can be promoted to conformance. It takes two releases. The main idea, the criteria that the conformance test has to meet is it should be a GA feature. It cannot be an alpha or beta feature. And it should work on all providers and on all architectures. It cannot rely on network or special binaries. So what we are expecting is any Kubernetes vendor should not have to do additional steps to run this. And it has to be stable and consistent. That's why we have two release cycles associated with it. So there are two PRs. One is to add the E2E. And the second PR would be to add that test to the conformance test suite. So a promotion PR has to be done to get that test into the suite. Oh, I'm sorry. Did I? Wow. So that's what I talked about here. So essentially, that's the criteria for the conformance test suites. So eventually, if you are promoting an E2E, you should submit PR to the SIG architecture. There are areas that we want to cover in the conformance test suite. Those are the areas that needs to be covered, especially node pod. We are covering pod right now. Volumes, there are tests already existing, but there are more tests needs to be written. So we are monitoring how much percentage of coverage we have. And there is a lot of work needs to be done still. And while promoting the conformance test, you also have to document the test properly. And each test will have a documentation header on top of the test, which lists when the test is added to a release and when the test is modified. And very high-level description of the test, which will help us to identify what area is covered and what the test actually does. So vendors who are running the conformance test, they need not have to know the technical details of the test. They don't have to go through the code, but they will know exactly what the test is doing. It helps us to actually analyze ways of the metadata that we are adding at the top of the test, what the coverage is, and also debug, if something goes wrong, fails in a vendor environment. So the documentation looks something like this. So you'll have test description, and then on the link, the blue part is the link to actual source code of the test. From the community point of view, the Kubernetes Conformance Program, we have a Kubernetes Conformance Workgroup. It's not a sig, it's a workgroup. And there's a mailing list. If you have any questions about the Conformance Program, you can use that. Actively, all our development is public. So if you have any interest in joining the development part of the Kubernetes, there is office servers that run bi-weekly on Tuesday noon PST, Pacific Standard Time. You're more than welcome to join this program. Oops, that's Google Docs. So the link I posted here should work. Or you participate in the Slack channel, kits-conformance. There is one more thing I wanted to show you is guidelines for Conformance Test Development. I think I'll have to switch to my, OK. Yeah, all the links are posted on the slides, so you can use it. And I briefly want to also mention the work that's being done right now with Conformance. We have a GitHub project board where we track all the issues that are Conformance related. If you see here, all the issues that come through triage, well, we have umbrella issues on tests we want to write. And then when the tests are written, they will go through the standard progress from the test set in the backlog. And if somebody reviews the test, it goes into the progress. Once the test is reviewed by the SIG as well as Conformance Techlates, eventually the Conformance program Techlates will review the test. And that will become part of the Conformance test suite. You can follow this. This is also a publicly available project board. And you can see what tests are going to come in your next release. If you are interested in running your tests on 1.16, probably this board will give you some indication of what's coming in for the future. So with that, also I want to thank the people who have contributed to Conformance. Some of the slides I have used from Aaron Krikenberger from LastQCon. That's pretty much it from me. So any questions? No questions? I covered a lot. Yeah. These tests, we've got a use case, not for Conformance, but to do canary testing of the clusters. Is there, this seems like it tests everything. Would that be viable? You mean, ETA tests or all the ETA tests? We want to know if there's anything wrong in the cluster before our clients have problems. So we want to run canary tests on the clusters themselves. Sure. I don't see why not. Actually, we were also thinking about see if we can run the upcoming Conformance tests upfront on the clusters to see if there could be any problems. There was a discussion in the previous meeting, the World Group meeting. Any other questions? All right, thanks for joining.


First what we're going to actually find is the density of your dead oil So I don't know if this is covered in the notes or not But if you define a density of a dead oil what you do so your row So are you like standard? conditions Is going to equal it's sixty two point four, but if you want to like be more specific it'll be sixty two point three six eight Times specific gravity of your oil So in this case like our specific gravity of our oil is 0.81556 which will give us a density of 50.86 And that should be pounds per cube Using this we can find what BO is Formation volume factor above bubble point. So we're going to be using this equation right here so for BO It's going to equal your BO at your bubble point So it can be BOB and then it's going to be When it's simplified you're gonna have it to be one minus CO P minus PB so you can use this equation to find your Formation volume factor of your oil above bubble point and So for below bubble point you're going to be using Equations three point four four and three point four five And you can also use this equation to find your BO at bubble point as well So for these equations you're going to have So this is going to be Above PB and for below PB you're going to have the equations BO is going to equal to 0.9 759 Plus 12 Times 10 to negative fifth And then times C BO to the 1.2 power and to find CBO CBO is going to equal RSO so your RSO at your pressure of interest times Gamma G over gamma O So this is 0.5 power plus 1.2 5 times your temperature which in this case 120 degrees Fahrenheit and So for this we already know what our RSO is at bubble point like I said because you can use this And below Bubble point so RSO in this case was is going to be 900 our gamma G is going to be 0.7 our gamma O is going to be 0.81 And our temperature is 120 so we can calculate with CBO is real quick. So that's gonna be so our CBO is going to equal 983 point 803 and now plugging that in to the equation right here so we're going to have 0.9 759 plus 12 Times 10 to the negative fifth Times your CBO, which we just calculated is 983 point eight zero three to the one point two power And we get that BO at bubble point is going to equal So BO at PB so all point is going to equal 1.44 For BBL For STB if you think about it it makes sense your BO should never be less than one because you can't have a volume of barrel of oil in which is going to be of Greater volume than what your stock tank barrel of Volume of oil would be and so your stock tank barrel is going to be like your oil at standard conditions So it's going to be expanded as much as possible to where your Reservoir barrel of oil is going to be a lot smaller. It's going to be compressed. So And so to find the BO At above bubble point. I said we're going to be using this equation right here And now that we have our BO PB we can use that equation to find that so our BO 4,000 psi It's going to equal 444 That was one of my eyes and the compressibility of the oil for because we're doing this at 4,000 psi I Have it on my notes Presently the oil is going to be 1.208 times 10 negative 5 which we found earlier. So Great to put that in real quick and then the P in this case is going to be 4,000 And PB is just gonna be a bubble point pressure which we found was 2,634 And so our BO above bubble point is going to equal 1.420 179 this is good because your BO above bubble point should always be below what your BO is at bubble point So if you actually look at a graph for BO with respect to pressure So you can have pressure here be over here. It's gonna look something similar to this So like similar to that and so this right here Is going to be your PB and this right here will be your BO B and so as your pressure increases toward bubble point gas will dissolve in solution which allows The oil to take the place of the gas in the reservoir So your volume of your oil is going to be increasing in the reservoir and once you reach bubble point There's no more gas to dissolve and so it's as much volume as you can possibly have but as your pressure increases even more The forces because of your pressure is increasing your actual fluid is going to actually be decreasing in size Which causes your BO to actually drop at pressures above your bubble point pressure and so once we have that we can also find what our BO is at 2000 psi and like according to this graph as you can see our BO Should still be less than what our BO is at bubble point because like our BO bubble point should be your maximum Formation volume factor. So your BO at 2000 psi is going to equal so we're going to be using this equation again for Below bubble point and so the only thing that's going to be changing and this equation is your RS value And so as you can see over here our S value for 2000 psi 648 point 145 Which will give us a different CB value CBO value, and so let's do that real quick. So you're 648 So our new CBO value is going to be 750.47 and then we're just going to plug that back into this equation up here for CBO So we're going to get a zero point So our BO value is going to be 1.3 1.4 BBL per STB and Like I said, like you expected a lower value just because you're not at the bubble point yet So there's still free gas in the reservoir where oil has not taken up that volume yet So once you get to that point where it will then like I said, you'll have your maximum BO value So once we have these three BO values the next thing we can do is define the density of our oil At bubble point or above bubble point below bubble point, which is where we're going to be actually using this relationship at and So I'll just I'm going to erase this real quick and then have some new workspace So now to find the density of your oil at bubble point below bubble point We're going to be using equation 3.51 to do this, which is going to be equals Which is just this that right there which the RSO is going to be your pressure of interest for your density and so as I said earlier, so the BO for 2000 psi was 1.3144 so that's what's going to be used here. So And like our RSO since this is going to be below bubble point or at bubble point So first one will do below bubble point So our BLB 1.3144 BBL per STB our RS will be 648.145 in a row ST will be 50.865 So this will give us a value So this will give us a density of 43.3 6 Pounds per foot cubed. This is for 2000 psi Now to do it at bubble point same equation the only thing that's going to be changing is your RS value and your BO value So your RS value at bubble point is going to be 900 and your BO value at both points can be 1.44 So doing that we'll get we'll get a density of 41.114 pound per foot cubed at bubble point now to find the density of Your oil above bubble point You're going to be using an equation similar to what it was for BO So it's going to be ROW equals ROWB Which is just going to be This right here One plus Your compressibility of your oil at bubble point. I'm sorry the compressibility of your oil at your pressure of interest So it's going to be P minus PB and so like I said we're going to do this for 4,000 PSI because it's for above bubble point So this will turn into 41.114 One plus which are CO at 4,000 PSI was 1.208 times 10 to the negative 5 and Times our pressure, which is going to be 4,000 that's the pressure. We're doing it for Minus our bubble point pressure, which is going to be 2,634.4 and this will give us our density of our oil at 4,000 PSI Which is going to be 41.7 9 pounds per foot cubed Once we find our density of our oil We can then move on to the viscosity of our oil, which is going to be using Few equations going to be using equation 3.53, 3.54 and 3.55 and so Our viscosity of our oil so the main equation Is going to be going to be a times The viscosity of the oil It's going to be to the B power This is going to be valid for Below bubble point pressure and at bubble point pressure and so What we can do is Our a constant Is going to equal 10.7 15 Times RSO Plus 100 to the negative 0.515 power and B is going to equal 5.44 Times RSO Plus 150 to negative 0.338 power Okay, so for solving this equation You're going to need a B and also mu o d to solve mu o d. You're going to be using equation 3.52 in the notes Which? write it out here It's going to be log base 10 of log base 10 of mu o d plus 1 It's going to equal to one point eight six five three minus zero point zero two five zero eight six Times your API of your oil, which is forty two minus zero point five six four four Times log base ten Of your temperature in Fahrenheit, which is going to be 120 so just During that calculation beforehand your viscosity of your dead oil It's going to be 1.512 Center poise so that's going to be plugged in right here so then we can finish calculating what a and b is and Yeah, so a is going to equal This is going to be for pressures below bubble point, so I'm going to be doing this for 2000 psi at first So at 2000 psi we see our solution gas solar ratio is 648. So 10.715 times So we get the a is equal to 0.354 7 and when we solve for B we get we get B Is equal to 0.5 684 So then using this equation we can solve for the viscosity of oil at 2000 psi So our viscosity of our oil will be So our viscosity of our oil is going to be 2000 psi a it's going to equal 0.4 486 Center poise and then we can also find what the viscosity of the oil is above bubble point Which is going to be using equation 3.56 I'll just re-erase this and do that then And we're going to calculate the viscosity of the oil bubble point We also need to find what the viscosity of the oil is at bubble point So using these equations I'll just find what the viscosity of the oil is at bubble point So I'll just do that up in this workspace up here because it's pretty crammed around here So your viscosity of your oil at bubble point It's you're still going to be using like your a B in your dead oil viscosity the only thing that's changing here is your RSO value which RSO and I'll be 900 So our a is going to Equal So a will equals zero point three zero five B will equal you will equal zero point five one eight and so Mu o d will still be one point five one two and so plugging that in we get zero point three zero five Times their viscosity of dead oil, which is one point five one two to the power of B Which is power of B just zero point five one eight So we get that our viscosity of our oil Just want to check Yeah, viscosity of our oil at bubble point is going to be zero point 3778 Which I'm going to read over here So viscosity of the oil at bubble point You go this is a center poise zero point three seven seven eight center poise and Then for our next calculation, we're just going to find with the viscosity of the oil is above bubble point So we'll do four thousand psi


from San Francisco, California. Extracting the signal from the noise. It's theCUBE, covering DockerCon 2015. Brought to you by SiliconANGLE Media. With special thanks to Docker. Now your hosts, John Furrier and Jeff Frick. Okay, welcome back everyone. We're here live in San Francisco for DockerCon 2015. This is the center of the universe, this is for DevOps. This is SiliconANGLE's theCUBE, our flagship program. We go out to the events and extract the signal noise. I'm John Furrier, the founder of SiliconANGLE. I'm Mike Goz, Jeff Frick, general manager of our CUBE business here in Palo Alto. Our next guest is entrepreneur, Patrick Riley, co-founder, CEO of Kismatic, hot startup. Great to see you again. We had an interview at OpenStack. Great, welcome back. Yeah, it's great to be here. So DockerCon, a Stu Miniman at Wikibon, said it's the center of the universe for DevOps. Indeed. And so, you know, certainly growing community small, but it has a Linux feel to me. Like I was talking to Alex Conrad from Forbes just before, and I said, yes, what's standardization? I said, you know, this is a forcing function right now because Amazon's numbers are out, Oracle's now putting out numbers, Amazon's going to do maybe, they say seven, I think 10, or Dave Vellante thinks 10. Oracle just announced last quarter in cloud, over 300 plus million in one quarter. That's big business. The shift is here, it's here. So if the community doesn't rally around open standards, that's what happened with Linux. They were forced to come together because if they didn't come together at a certain time, into she's toast. So I'm very excited about the Open Container Foundation, kind of our Kumbaya moment, like everyone's coming back together. We don't have to make choices. One of my big frustrations were with some of our clients, they didn't know what to bet on.  It's like the VHS Betamax kind of argument. You don't want to end up with both players and no matter which one you chose, you do have to have that kind of contingency of, what do we do in case the other one wins? So having this happen, having it come back together, be one core thing and having the Linux Foundation behind it, it's really powerful. Yeah, and then what you're really getting at is, if this continues, it would have been an absolute screeching halt from a customer standpoint. Yeah, and it would have opened up the market potentially to some other tertiary approach that- Yeah, some whale pun intended coming into the Docker ecosystem. We think ocean theme here. But Patrick, I want to get your thoughts, right? So on OpenStack, we see that DevOps is cloud is hot. We want everyone, no brainer was going there. Software methodologies have changed. The now cloud era is upon us. Agile, new name is all happening. What's the challenges right now? I mean, you guys and your businesses about orchestration, Kubernetes, what's going on at that, the value is part of the stack? Yeah, I think the most difficult part for us is the education and just getting people comfortable with how they do things, making sure that they're doing it the right way. We start simply by trying to get them to look at their CI CD approach, like how are they actually building the software? How are they testing it? And ultimately, how can we get them to get things to production quicker? In the keynote the other day, we saw where people are saying, oh, well, we pushed to production three times last month. Now it's more like we pushed to production 3,000 times last month. So once they have the tooling in place, much more comfortable to getting developers new fangled ideas like to production quicker. So we find a big part of that is education, making people feel comfortable about the tooling and able to kind of go full bore. Give the background on Kismatic for the folks out there. Your company started, young company, entrepreneurial base right now. What's the status, where are you guys growing? What's the, give us the update on Kismatic, products, shipping, customers. Yeah, so Kismatic is our mission is to be enterprise support for Kubernetes. So we're all former Mesosphere. We come from distributed systems background. We know how to do this stuff. We're a small team. We're only seven people right now. We haven't disclosed our funding as of yet, but we're in good shape there. And the customers that we're going after are the people that we think are the most likely to get to production. We won't even do our paid POCs with customers now until they sign an LOI that they have an intent to go to production with Kubernetes. And just everyone- Is that because there's so much demand for POCs? There's so much demand. Or that you guys are being selective with your time? No, it's both basically. There's so much demand. We actually have what I thought was a fairly high price for our paid POCs. And that was not enough of a gate. So putting the LOI's- Raise prices. Raise prices. Keep raising prices so people say no, then you know where the line is. Yeah, exactly. Exactly. But with the POCs, we're really trying to drive towards what is the executive summary at the end? What is the architecture review that's going to get them to production? How can we help them get there? And I don't want to just be a training shop. So I'm not in a good place to do that. You don't want to be just services. But services are a good business to prime the pump while the market's developing. Correct. So you learn a lot from your customers. Yeah. So one of the approaches we've taken with our POCs is that we actually, each one's better than the previous. So we use a Git repo. We use that same Git repo for the next group with a different name. And all the lessons we learned in the previous one aid the next one to be even better. And we use a Slack channel for the customer to talk with us. And the thing we find is that even though the POC is a few weeks back, a month back, they're still in that Slack channel. They're still talking. They're still putting in their POC repo. They're still asking questions. And they ultimately make it better for every single customer that comes after them, which is kind of exciting. So I got to ask you, what are the lessons that you've learned that can be magnified from your experience? You saying the POCs you're learning from each one, what are some of the things that you've learned over the past few months that have changed your mind on how the market's going? Well, I'll say. It's validated your approach. I'll step back. We're just now to the V1 of Kubernetes. So we're doing the V1 launch event on the 21st at Oskon. And now we finally have a stable API. So one of the most difficult things about doing the POCs to date has been that the API has, there's been so much churn. So when I'm doing a POC and I'm telling them to do this and this is the way we show them with a beta-free API, it when it changes two weeks later and has different things that they have to do or we change flags on the command line, it becomes really difficult and they think things are broken. So a big lesson I've learned is to make sure that we communicate those changes in the same way to users so that they know the upgrade path to keep things working. And now that we have V1, I'm excited that we have a solid API. We're not going to have that. And I think back to the open container comment, a very unfortunate thing has kind of happened in this space this year with the fracturing of the container format because it put so many people that were really gone home, ready to go all in, decide, okay, I've got to step back because there's this war now going on between two formats. So I'm glad that we've gotten that behind us. What do you, as an entrepreneur who has an interest in the future of the ecosystem, cloud in particular, just a moneymaker, what's your take on DockerCon this year? Are you happy with what you're seeing? What areas do you think is missing or should be added? Just general commentary, what's your take? So I'm really excited about DockerCon. I mean, to see this many people here, everyone's very exuberant. They want to go home. They want to experiment with the things they've learned. I just want to keep this energy in pace, moving forward. I think experimentation, that kind of mindset is what really drives the industry forward. So all of these people now have this tooling. They can go and try new things. I hope that this time next year, next year's DockerCon, it's even bigger and more exciting. As an entrepreneur, what's the biggest thing that you've learned about yourself in this startup versus others? Well, that I actually need sleep. I mean, how do you get to work then?  I mean, you got to wear a lot of hats, right? Yeah, we definitely wear a lot of hats. I mean, my team's all people that I trust that helps quite a bit. And to be fair, the boundaries between companies are pretty blurry at this point. I would definitely say we are a container community. I get a lot of support from Solomon at Docker. I get a lot of support from the folks at Google Cloud Platform. I mean, in a lot of ways, even though I'm a seven-person company, I have upwards of 45 engineers at Google able to help and drive things forward. And it definitely feels like an extended family. It doesn't feel like I'm a walled garden. So I'm a skeptic, pretend I'm, my name's Bob. And I'm a skeptic, Bob the skeptic.  How do you compete? I don't see you winning. What's your answer to that? So- You say Bob? I say Bob?  You'll bounce in. And we'll set the F word again, but we don't get censored anyway. We're at theCUBE. My prices are not high enough. Yes. So I think the thing for me is if we look at Google Cloud Platform and what they're trying to do with Kubernetes, it's coming from a company that has two billion containers a week launched. Almost all their payloads are running inside of containers. It works for them. They're giving it to the community. We're trying to provide enterprise support for that and allow you to do it on systems you already have. So I'm not asking you to throw out Red Hat. I'm not asking you to throw out Ubuntu. Just install Kubernetes on top of those things. So you could win no matter what scenario, in your mind. In my mind, we are actually covering the bases pretty well. Short of Google deciding, you know what? We're done with Kubernetes. You don't want to do this anymore. That's the only fear I have. That's a fatal flaw. That's the fatal flaw. So I think if we can grant, and Kubernetes in particular, if we can grant the IP to a foundation, much like we've done now with the Open Container Foundation and not have Google necessarily be the gatekeeper of that, that would be the next level of success for Kubernetes. I mean, every business has a fatal flaw.  I mean, I just tend to trust Google's opinion of how to do things when they are all in. It's not like they're dabbling in containers. They've been doing this for years. Google's definitely all in on Kubernetes. I talked to the guys over there, Craig McLucky and everyone else. They are cloud businesses booming. Yes. All right, so talk about the foundation. There was a thread I read on GitHub that you were actually mentioned on February 13th, some sort of haymaker. I wouldn't call it a haymaker. Comment on GitHub. There was a thread that Solomon was talking about, squabbling over namespaces, DNS namespaces. Yeah, I forget what context it was. Something small, trivial. But the point was, he was like, hey guys, stop the charades, let's get back down to business. And you just said, hey, we should start a foundation. You got the seed that started it all? Yeah, I mean, I just personally felt that we need to have this kind of more of a consortium effort. Let's not have these company lines. Let's not play politics. Let's get to where we're actually servicing the user in the correct way. It's very frustrating to me when a customer comes to me and they want to hit the pause button because they're uncomfortable with which direction to choose when it's just unnecessary. I would say to Dave, you know, it's like nailing Jell-O to a wall. But now the other Jell-O analogy is when you put Jell-O in the fridge, it comes together at some point, it just forms Jell-O. Is this the moment where everything comes together for Docker in your opinion? Do you think OCP is that moment? Or is there more things that have to happen on the community side? So I think from my standpoint, I look at Docker as being like big D Docker and little D Docker, right? There's the Docker community and there's the Docker company. And for me, I want to make sure that, you know, Docker, the company set up for success to provide tooling and products, you know, for people to actually move to containers and away from, you know, legacy approaches. And I want things to be done in a governed way that's open and inclusive, not exclusive. All right, well, thanks for coming on theCUBE. Really appreciate it. We've been following your success. We saw you at OpenStack. Again, perfect storm for developers. It's an application-centric, programmable infrastructure. It needs orchestration, it needs Kubernetes. Thanks so much for coming on theCUBE. Really appreciate it. Thanks for having me. See you out of chismatic here. Patrick Riley on theCUBE. We'll be back more wall-to-wall day two coverage. Kind of coming to an end. A lot of people are strolling out now, the keynotes. This is theCUBE. We'll be back more from live in San Francisco where all the action's happening in cloud, in DevOps after this short break.