 So for me this is probably one of the most fun parts of the day and we will ask you all to bring your questions And we'll have some Q&A at the end, but I'm really happy to introduce stormy Peters who is the head of our open standards and software a group at at red red hat leading a lot of the community events and projects and we're going to bring in our panelists and I'll let stormy introduce them as they come on I'm gonna let them walk up and get seated and then we're gonna get started and they'll introduce themselves While they're getting seated This is the upstream panel upstream this how many people here know what upstream means Awesome here. Let's hear some answers shout them out shout out the answers. What does upstream mean? Where all the fun happens any other answers for upstream Community One more Collaboration so the upstream is where the open-source software collaboration community and fun happens So this is a panel. We're not going to be able to give you all the information about upstream in half an hour This is a panel to introduce you to some of our upstream contributors There are also others of you sitting in the audience and this is to start conversations that you can have over lunch You can have later today and you can have at the get-together You can have during this week at cube cotton. So this is a conversation starter So with that I was going to ask our panelists to introduce themselves say their name what project they work on and Then to you know how like when you're trying to describe what you work on to somebody who has no clue Maybe it's your neighbor who's a surgeon Maybe it's your kid's teacher and you try to use analogies and you try to use metaphors And you end up in this big complicated mess I'm going to ask each of our panelists to share their favorite analogy that they use When they're trying to describe some technology that they work on and Clayton's going to tell us what an analogy is just to get us started An analogy is when you compare something to something else for the purposes of explanation Thanks So with that Chris would you like to get us started your name What project you work on and then some analogy that you try to use to describe what you do Okay. Oh, oh, sorry. Hi everyone. I am Chris Nova. I work. Thank you everybody who waved back. That means a lot to me I work at Heptio, which is freaking great And then I guess My analogy like this is going to be really like everybody here probably already knows what I'm going to pick But I'm going to compare it to mountains because that's I do a lot of mountaineering And I think like there's just a lot to be said about like going one step at a time to take over Like a really monolithic task a lot of the stuff we do in Kubernetes an open source is like I'll walk up to it And be like whoa, like where do I even start working on this thing? And I think it's like sometimes just really important to just kind of like take a deep breath and just take your first step That was really good analogy So I'm Clayton Coleman architected open on open shifting Kubernetes at Red Hat. I also work in the Kubernetes community a lot so my analogy is I usually start with You don't know what I do But when it stops working you will all regret it And that's a nice icebreaker and then I usually spend a bunch of time Which is like all of the things that we all build are incredibly complicated and nobody understands it anymore And so by analogy We're sitting on a giant mountain of stuff that's built and there's like some guy at the bottom Who's like hitting the foundation piece and it's going to fall out one day And I'm the guy trying to keep the guy from knocking the foundation piece out I'm Paul I work at Red Hat Focusing on the service catalog and service broker space and multi-cluster the analogy that I use is Not impressive because I'm typically explaining the service catalog Which is basically what it sounds like If you imagine Think of you a hundred years ago, and you want to build a house So of course you look at the Sears catalog which is Approximately two feet high and you can you can order the thing out of the catalog and it comes to you That's actually a terrible analogy also because The houses that you ordered from Sears catalog, which is actually a thing did not come assembled and part of Service catalog in the concept of a broker is that you don't you don't care at all So very bad analogy But it did you didn't ask for a good one. So I Completed my task I'm I'm Brendan Burns. I work at Microsoft Azure on containers and DevOps My analogy is that when I was eight I I think it's about eight. I spent about six months building a remote control plane And took a long time and I went out to fly it and I went Right into the ground so six months of my life gone in about ten seconds and now my kids use an iPad to fly a quadcopter around our house and So we're building software that helps people who build Systems have an experience that's more like my kids have unless like what I have and never get on a plane that Brendan built Yeah, it was because it was like balsa wood and paper I mean if you get on a plane and it's balsa wood like just turn around Good thing for Brendan. No one that has ridden on a plane that he's built is here. That's true. It's exactly right. It's alright I have no complaints. I've never had a complaint never had a single complaint Okay, I'm a pernesina And I'm a product manager on the Kubernetes project my analogy is that of a I guess of rocket ship I feel like we not the interesting aspect of flying a rocket ship, but of putting it together So I think of the work that I do as being in a Environment where there's lots of moving pieces and we're trying to build this thing that's gonna that's gonna take off And it's very important not to have any unscheduled disassemblies on a rocket. That's one of the most important things When it's flying All right, so now I'm gonna like give you guys a minute to tell your neighbor what your analogy would be See I'll have one minute to tell your neighbor what your analogy would be and if there's no one sitting right next to you Turn around and talk to the person right behind you Like a float in the middle yeah, and so just like four billion dollars just smashed on the surface of Mars because they didn't do their units correctly All right, I'm gonna call everybody out now that you know Now that you all know the best and the worst ways to describe the technologies that we work on And my panel is just talking all about rockets, so I think we're gonna like now talk about rockets instead of open ship Sorry about that I'm liking this rocket idea Maybe we could shift All right, so if you have any questions to start this out at any point you can jump in wave your arms If I don't see you we don't have a mic, so you're gonna have to shout and I will do my best to listen Any questions about rockets analogies Kubernetes open shipped will take similes also not just analogies, please is it a NASA rocket or a Tesla rocket? Honestly, it's the bunch of rednecks in their backyard with beers It's the dude with a steam powered rocket actually it is most definitely an open-source rocket these guys are both wrong It's the it's the probe from Star Trek 4 It's it's still under construction, so It's gonna be the NASA rocket bit. I mean it's starting to kind of look like a rocket, so that's good. At least we got that going for us All right, is there another question start us out Right, so so this is this technology is a pretty Kubernetes and the surrounding technologies are are all open-source software They have a lot of the aspects of traditional open-source software And it's also a pretty unique place that really fosters innovation on top of it and would anybody would What what do you think is unique about it that fosters that innovation? So for me the Kubernetes community and the way that we sort of all come together to engineer the process of engineering is Super unique coming from other communities and like the open-source and Linux see Apache space To Kubernetes was a really big jump for me And I think as a software engineer like I really really thrive in this environment where I get to speak my mind and collaborate with other people and look at our Software in the same way we actually look at our process as you know through the lens of an engineer That's really really powerful for me. I Was gonna say one of the things that I really enjoy is Using I think it's somewhat unique is using what you build so a lot of open-source projects You don't necessarily use we built like Linux is a great example like most of the people who hack on Linux Actually use Linux and in Kubernetes like a lot of the things that are components of the system run on top of Kubernetes And so we're getting better not there yet, but we're getting better at hey all of these problems that we're having Our problems that most of our users have and it does help focus the mind a lot in Kubernetes I really enjoy that I think it's sort of unique also because it was built from the ground up to Help and empower users right it wasn't I think a lot of projects kind of come out of like Oh, I really want to build that or I really want to you know I had this itch the scratch or something like that I think Kubernetes really came out of a desire to Help people build software better. I think that's relatively unique in the open-source space And I think that's part of why it's developed such a great ecosystem. I think also we've been blessed with Really fantastic people throughout the the community and it really helped get the DNA right speaking of the rocket ship at some level like Little tiny bits of angle in the early trajectory make really big differences And I think that we got really lucky in the first three to six months where we just got the trajectory really right Yeah, we've got some rocket scientists I think what's unique is that you can join It's kind of rare to be able to join in building something like this But this is a community which thrives on contributors And and a lot of users join So to Clayton's point it's also That's also actually quite unique. So I would also say like I mean having been around open source a lot I'm not a huge fan of BDFL projects And so we sort of explicitly set it up from the beginning to not be that and I think that's helped Make it open expand on that to not be a what BDFL benevolent dictator for life. I don't know Everybody knows that I think everybody knows that right? Yeah, not so inclusive. Yeah, like well and just yeah I think so we sort of set it up in the beginning to be inclusive and humble and and I think that's really paid a lot of dividends And so what happens is you get this conglomeration of really smart and really friendly and Really interesting people and you can learn a lot from everyone that you meet I think that honestly There's never been a community like that at least that I've experienced before And so each of you are working in different areas of technology we got cluster API's we got service brokers What is happening in your space? What are you doing to foster innovation and how would somebody who wanted to get more involved? How would they follow along or how would they join? So I spent a lot of time working like on the infrastructure side of things in kubernetes So I'm a member of SIG cluster life cycle and we have a working group for the cluster API We're working on now Robert Bailey and I are giving a talk on it on Thursday if you guys want to come check it out But like getting involved it's it's really like join the SIG calls Like comment on things on github. This is a huge one like the first time I started commenting on kubernetes stuff I was kind of like am I allowed to do this? Does it you know is this okay and like now I'm a maintainer of a couple of repos in the kubernetes org So what kind of comment did you leave? I just like my two cents right like I agree with this or I don't agree with this or like I don't think that we needed to put an interface here or you know just kind of like whatever and even if it's not like a Super technical comment. I still think user experience is something that we really need to focus on in kubernetes So even if you're like sitting at a command line and just something feels weird or backwards like bringing that up and making That known as super important There's ways to get involved in non-technical functions One thing to do is I think just use the product and kind of understand what it is and then all of the SIGs And all of the meetings are open and everybody is invited So you can join the community meeting which is on Thursdays at 10 a.m. Pacific or you can join any of the SIG meetings Which are all published on github And just kind of start to listen in and then see if there's a role that you'd like to play One of the nice things about the kubernetes community is that I feel that very strongly that folks who make contributions in the form of like taking notes or Organizing meetings like things that are non-technical are Command just as much as just a much just as much respect as people that are primarily contributing code and that's Really awesome on a couple different levels because that's typically something that's that's overlooked But I would urge anybody in this room that wants to get involved start attending community meetings started attending SIG meetings and The the reality of the non-technical non-technical contribution type track is that those things tend to be things that engineers are like terrible at so they're incredibly valuable even just taking notes is Really valuable skill For my own little slice of the world One thing that we recently discussed in a open service broker API face-to-face in Raleigh last week Actually is adding new generic action support to that API so that you can prototype things without having to go through the process of Changing the official API which we hope will be a way for people to incubate and experiment things and maybe have some emergent Conventions in the actual spec itself yelling those lines. I would say at this point amazing three years later But kubernetes is a commodity at this point. You can get it easily off of any cloud And so I think a lot of what's exciting is building on top of those APIs Figuring out. There's just so many interesting cool tools that people have built out in the ecosystem Effectively by themselves or with a small group of people like you don't even have to be involved in the main community To make a contribution you can build a tool that helps manage configs or manage certificates or Something that is useful generically useful on top of these API's that are now available to people across the world That's also a really great way to kind of get a feed way There are also meet-ups worldwide and so as you start using kubernetes Even if you're not contributing to it you can go and share your experience and you can often give talks and it's very valuable Yeah, I was gonna Brennan totally still mine because I think the idea here is that like Cuba's gotten so big in the last Three years like there's a lot of stuff that it does it just can't keep growing forever So we need to get really really good at making sure and Brennan's let a lot of this stuff on the client side Going and using the client generators to make clients for new languages And you know, I think we need to do more and like this is something that I try to spend a lot of time on is Taking feedback from people who are building stuff and then saying like what do you need to be successful like watching? What they do and trying to tweak what we do to make that more powerful Any questions from our audience yep We had a mention of code that writes itself can somebody explain that If you're hiding this machine in your basement, I would like it are we talking about generating code from like a like the open ice spec No, so there was a talk by Telus earlier where they talked about as a as a vision I think that they're not gonna stop until the code writes itself and can't stop and I think that's a good That's a visionary statement, and I think that that's a that's a good vision And others should certainly comment where I were what I took that to mean is you know a lot of analytics and Machine learning can generate output that is useful To to the application so put so potentially I don't know if the code would write itself, but there could be Connections of existing modules that you know create an application. That's new or Result in something. That's new I think they were also talking about functions as a service and maybe maybe tying that together But I do believe it was a visionary statement I'd also refer you to a talk by Steph Walters that he gave at a conference in Berlin And he says he has a cyborg team member and he talks about the things they give the The computer to do their cyborg team member that they would typically have done before I think another thing that I've been playing around With a lot actually And I'll talk about actually in my keynote tomorrow Is this notion of how we build abstraction layers on top of Kubernetes, right? I think that it is still way too hard to build distributed systems and in Kubernetes We have maybe created an assembly language, but we have not created Higher-level programming languages, and I think that is an interesting next step It's not really code that writes itself But it's at least a higher-level language that you can compile down into these building blocks to enable people to not have to necessarily think about them I think the concepts comes up obviously because there are so many things in Kubernetes that You know over time will will manage themselves so clusters that repair themselves and scale themselves and So that leads to okay if the infrastructure takes care of itself. Can we do something like that also at the application level? Any other questions Working a platform Can you start can you start over sorry? so one fundamental dilemma that you guys on upstream to have is Creating something that you collaborate across different companies But the people on top would actually create the product is create something different Because they want to flavor create something different on market So each company has different to flavor how you guys can guarantee the freedom The user can jump from one product to another I Don't know is that to concern that guy has an upstream So the question is if you get Kubernetes from from one vendor How do you make how are we making sure as a community you could move to another vendor? I think the the Kubernetes API here is super important And if you look at like the the programming language go that a lot of it's written in you see these implicit interfaces And I think the sort of idea of defining the pattern or the API like Brendan was saying first and then having opinionated Implementations of that API and that can be either from an open-source project or a company or a product or whatever I think that pattern in general something that really shines in kubernetes and being able to lift and shift from one To the other is really taking advantage of that API abstraction another thing is that for a lot of us I don't have to differentiate in terms of product. I differentiate in terms of service Right, I differentiate it in terms of kubernetes as a service as opposed to in terms of on top So I think it's kind of like you don't really differentiate on the x86 instruction set I think there's a degree to which it's just a baseline that that cloud providers provide for you And then the product is the reliability the price point all of that sort of thing Yeah, and I would actually add to like to that the idea of API is like the kubernetes API Will not be the last API ever created in the history of mankind What'll actually happen is just like every other API like an assembly is a good metaphor because there's x86 But then there's microcode and then there's the transistors and then there's the actual modules and there's the biode Like I think we're actually gonna see a lot of that and we're seeing it today Like everybody has build systems in their company today And sometimes they want to change them sometimes they actually want to hook things in and so we're starting to see like We should be really easy and like to Brendan's point to stack layers really cleanly Not everybody's gonna choose the same layers if you can switch layers out bring pieces together That's like the writing code is what are the pieces the tools that help people build Distributed systems help people tie together build chains roll things out to production because at the end of the day That's all that actually matters right is how do you deliver software? So some of the I think some of like the opinionate ones like OpenShift is somewhat opinionated tries to tie all these together and it hits certain Optimized points, but not everybody is going to build software that way And so I think it's layering up multiple layers of very well-designed Independent pieces that can be composed is how like it is the only way that this will evolve Like you can't just design the perfect system and everybody to use it I think we would be remiss not mentioned the conformance program Which I talked about earlier and which launched. I think just before Thanksgiving Which is a set of tests that any kubernetes distribution can run and then publish results back on github That shows that it is conformant and it's it's not a complete set of tests right now But over the course of this year we're going to be expanding that set of tests And the goal is to ensure that the kubernetes API is fully exposed and that Applications that are running on kubernetes can be portable across distributions So yeah, so referring to analogies and all that so we've gone in the computer building the Normal computer there's analogies to that what's happening again today in the distributed systems, right? Yeah, has anyone mapped that journey sort of you know like you mentioned assembly and obviously things have evolved We've been doing computer for a lot further than distributed systems So and the networking has the OSI layer so we were all talking about these things Is anyone kind of tried to create an infographic or something that helps us map that journey a little bit better I don't know about any infographics. I think about it a lot. I think there's a challenge here because You know there's this really obvious analogy where you say oh the distributed system is just a computer And then you realize that it's actually not and It's kind of like a really bad new my computer and Computers are also really bad new my computer. No, and that's true And so like and then and then you forget and then because like people cared and then people stopped caring and maybe people will stop Caring again, and I think at a certain level people don't care. I do think that I kind of feel like with Kubernetes We've kind of created processes And I've and I've often said that I kind of felt like the Kubernetes API or that some API layer would be sort of the POSIX of distributed systems. I Think we're headed in that direction I Think that there's a long way to go and it's not entirely clear how much of it the analogy Is an inspiration versus a literal analogy? But it's definitely an area that that I'm interested in exploring one of my favorite quotes is the futures here It's just not evenly distributed right so the big companies have been doing this for years And so they've got lots of these patterns baked in and if you look at Kubernetes Like a lot of it is folks like Brendan and Tim and Brian saying like we have all these patterns Let's boil them down to their essences and put them out there And every day someone comes to Kubernetes and does the same thing for networking or for storage or They take the new ideas so I would actually say the really thing that we should really try to do in Kubernetes is the meta Right, it's the my the process of thinking about how you build things so that they fit well together And they solve problems really quickly in the distributed systems place like I Will cast any aspersions but like just as a random example the EC2 API was not designed as Something that was going to magically make all of building applications easier. It was designed to deliver VMs I think we're trying to be a little bit more deliberate on what are the things that applications need and design APIs for that and Think a little bit about what's above and what's below and then try to put them together I think the APIs will change but the process is what's important like can you plug stuff in and get value out of it Incremental yeah, I think there's a real challenge. I mean the one challenge I would say is every time every one of these systems that I've seen It kind of stops where Kubernetes has stopped right which is like a bunch of sort of relatively raw application-oriented infrastructure primitives and then it either jumps all the way to pass or it just kind of Huddles along at this level and I think they're what we need to do next is to figure out. How do you build? the Standard library and the compiler that lives above Kubernetes in a modular way that doesn't turn into paths and that I think is the real Challenge that I that I want to spend a lot of time that I spend a lot of time thinking about and that I want to Spend a lot of time thinking about because I think that's where we actually get to what you're talking about if If we just build verticalized passes We only the only place we unify is that this low-level assembly language if we start thinking about how do you build higher level languages? That our utility is not platforms then we may have a chance, but it's really really hard is my experience I'm gonna cut this one off because it sounds like an awesome conversation Sounds like it should be over a beer this afternoon or it could be a whole session on itself beer Yes, or it could be a book Cool, so you all know who's interested in having the conversation find them at lunch find them over beer Any other questions? All right, so I asked a lot of questions about how things work now Let's switch a little bit to technology and each of you work on different aspects If you could tell me one really cool thing that you're working on right now That you think will foster innovation in your space or innovation for those that are developing on top of it Give us a you know a one minute update of what's happening in your project Chris You want to leave us off? Sure. So like I mentioned earlier I'm doing a lot of work with folks over at Google and in the SIG cluster lifecycle group for the cluster API And I think the sort of 10,000-foot view here is we want to have a declarative way of defining infrastructure And the really exciting part of that is having a set of what we call Machines which represent virtual machine in the cloud and having a controller that sort of takes this Kubernetes Declarative first principle and applies that to infrastructure is something that's really exciting to me And I think a lot of folks are gonna get some value out of it when you start looking at things like business logic And maybe we want to autoscale based on arbitrary rules that are encapsulated in software So I just think there's a lot of modularity and flexibility And this is something I've been kind of working on for like about a year now and to see it kind of come To life is really really exciting for me. Are you talking about that this week? Yeah So we're gonna be demoing The machine API that I just talked about and we'll be talking about like the journey of how we got here and why we named things What we did and well, you know what everything represents inside of the API we're proposing One of the things that I've been working on is the container identity working group This is kind of the idea that you know You have all these like services all over the place and all these pods all over the place And you kind of want to be able to say like well Who is it that's talking to me because if you want to build an integration you want to say? Okay, well, I know that I should only give this secret out to this particular workload running on this particular Node and so we've been working with a bunch of folks in the community the spiffy effort Inspire which is a group of people working on kind of a generic Spec that works across cloud and metal We've also been looking at how we can break up Kubernetes and make this easier and trying to say like Every time we break something out of cubes, so you can say like I want to plug Kerberos in or I want to plug Pki and Doing it in a way that really makes it easier for everybody else to benefit Even if this is very specific to any making it easier to do extension at the node level, so that's been really exciting I've enjoyed it And if someone wants to talk to you about it. Do you have a talk or there is a container identity? Meetup on the calendar actually don't even know what day it is like I'm very just in time scheduling But we will it will be a topic and please come find me or Greg Castle from Google and we'd be happy to talk about it One of the things my team has been looking at recently, which is very interesting to me is there's a lot of different reasons that users want to run multiple clusters of Kubernetes or OpenShift and When you introduce the idea that like you now have n different clusters to care for The logical implication is that you have to have a record of what all those different clusters are and how do you reach them? so the SIG multi cluster in the Kubernetes community has been Bootstrapping an effort on a cluster registry, which is an API server that just has a cluster resource Which is where is this thing and how do I talk to it? and it's really exciting to me because I think this will accelerate and Unify to some degree different efforts in the community around Building tooling to handle multiple clusters at the same time, which seems like an inevitable challenge to get over So there is a SIG multi cluster deep dive that I believe this will be mentioned in Like Clayton, I do not know the day of the week that it will be but it is a thing at Kubecon, which is where we are going to be Yes It's not Wednesday So I'm really excited about a bunch of the work that that the Azure team has been doing an open source developer productivity So from things like the Kubernetes in Visual Studio code to this tool called draft which is sort of a Rapid iteration local rapid iteration experience between your cluster and your workspace on your desktop To Brigade, which is a workflow system built on top of Kubernetes that people open sourced a couple weeks ago To the work that I was was talking about the called metaparticle that I'm giving my keynote about tomorrow I'm just really excited in general about the space that lives above the Kubernetes API that enables people to build Applications more easily or even at all when they couldn't have before So I'm a product manager So I tend to bring things together in the project in the service of what users are likely to use my talk is on Friday and I will be Giving a demo of a hybrid deployment with two clusters one. That's an on-premise cluster and one. That's a GKE cluster I'll be using The multi cluster registry and demo demonstrating that I will also be using the open service broker and the service catalog to show An application that runs in a hybrid manner. So please come to that. That's at 11 on Friday all the hits in that one So I have one more question for our panelists. Um, but before I get to that Oh, go ahead. I think he's asking Paul about Federation. Yeah So the question was whether I was describing Federation, which is a project that has been in the Kubernetes code base for a while was actually recently moved out into Kubernetes Federation and Just in to answer your question the the answer is The the Federation has a cluster resource that we're talking about replacing now With the cluster resource that comes from the cluster registry. Good question and I think in general the difference would be that Federation thought a lot about maybe what API objects you might want to define at A worldwide level that would then create things in the cluster whereas I think this is merely about like I just have a bunch and I Want to organize them and I need to get at them in a bunch of different ways. And yeah, it's a much simpler use case I think the Federation use case Was always experimental and and has proven out over the course of the last couple years to be to be Experimental and so I think this is a very practical solution architecturally the multi cluster Thinking is to have State from multiple clusters in a single registry and to be able to operate on them in an iterative way from From the registry and to have that be a highly available control plane versus Federation was very much like a tree Where you had sort of a single point from which you could control all of the APIs and that that single point was to look Like any other cluster These are two different architectural approaches both meant to manage multiple clusters the cluster is not a proxy also the cluster Resource is not proxy where as Federation was Okay, so we don't have time for more questions, but it's awesome that you have questions You I have one more question that I'm going to use to close with And you can find them all at lunch or this afternoon But before I do that I think any session you go to any conference you go to at the end of every session You should think about like what did I get out of that like why did I sit there for half an hour? And it may be something you heard that was new and maybe something that sparked a thought of your own that you Want to follow up on so that you don't lose that in this You know you're going to be in a lot of sessions this week, and you've already been a lot of sessions this morning I'd like you to share with your neighbor What's the one thing you heard that you learned or the one thing that sparked another thought in you or the one? Conversation that you want to have after this so tell your neighbor the one thing that this half hour was worth to you We got rockets up here definitely rockets from up here Okay, all right, so I gave you just enough time to be a teaser Sorry about that So I encourage you to have these conversations Later if you had ideas or thoughts that it sparked or something you want to share Please tweet please blog and I'm gonna have our panelists close. They're going to tell you their name I need everybody's attention so they they can Thanks, so awesome ideas. Glad there's conversation happening. Please talk to your neighbors at lunch. Please continue the conversation Please tweet please blog. Let's let's get thoughts flowing I'm gonna ask our panelists to close by saying their name again so that if you walk to them walk up to them at lunch You don't have to like pretend like you know who they are and you can't remember their name So they'll say their name again And then I asked them to share the cube con presentation that is not their own that they are most interested in a Tenny or not most interested but interested in attending this week So Chris you want to lead us off again? Sure. So again Chris Nova We're gonna have to you The presentation I'm most excited about this week is a really close friend of mine. Locky. He works at Microsoft He's doing a presentation on Istio and that's like admittedly one of the things I don't know very much about so I'm gonna get to go and sit in this like with a pair of like New by is and learn about Istio for the first time. So I'm really pumped about that I'm Clayton Coleman work at Red Hat and I think I'm gonna go to Bernan's keynote because he piqued my interest I'm Paul Maury. I work at Red Hat and I'm most Looking forward to SIG sessions so I can talk to folks in the community About what they're interested in I'm Brendan Burns at Microsoft Azure I think I'm gonna cheat and say that I'm actually most interested in talking to people in the hallway Actually the one-on-one conversations is always really my my favorite part at the booth or in the hallway So please don't hesitate to come up and chat That's it. I'm a Pernacina Product manager work at Google. It's very hard to pick one talk. I'm looking forward to all the keynotes I'm really looking forward to Chris Nova and Robert Bailey's talk on the cluster API which allows you to consistently Deploy and manage Kubernetes on all environments Awesome. Well, thank you all these these are awesome people are our panelists. They are totally approachable. So please, you know bug them all week long I'll buy them a beer if you're bugging too much Anyway, they are all here to meet all of you and to have these conversations. So thank you very much. Thanks