>>Live from Barcelona, Spain, execute covering CubeCon cloud native con Europe, 2019 onto you by red hat, the cloud native computing foundation and ecosystem partners. >>Welcome back. We're here in Barcelona, Spain where 7,700 attendees are here for Q con cloud native con. I'm Stu Miniman and this is the cubes live two day coverage having to have on the program to returning guests to talk about five years of Kubernetes. To my right is Tim Hawkin wearing the Barna contributors shirt. Uh, and uh, sitting to his right is gay Bon Roy. So, uh, I didn't introduce their titles and companies, but you know, so Tim's and Google gives it Microsoft, uh, but you know, heavily involvement in uh, you know, Coobernetti's since the very early days. I mean, you know, Tim, you're, you're on the Wikipedia page game, you know, I think we have to do some re editing to make sure we get the community expanded in some of the major contributors and get you on there. But gentlemen, thanks so much for joining us. Thanks for having us. >>Alright. Uh, so, you know, Tim just spoke to Joe Beda and we talked about, you know, the, the, the idea of, you know, Craig and Brendan and him sitting in the room and, you know, open source and, you know, really bringing this out there to community. But let's start with you. Cause he, you know, uh, I remember back many times in my career like, Oh, I read this phenomenal paper about Google. You know, we're going to spend the next decade, you know, figuring out the ripple effect of this technology. Um, you know, Coobernetti's has in five years had a major impact on, on what we're doing. Uh, it gives a little bit of your insight is to, you know, what you've seen from those early days, you know. >>Yeah. You know, um, in the early days we had the same conversations we produced. These papers are, you know, seminal in the industry. Um, and then we sort of don't follow up on them sometimes as Google. Um, we didn't want this to be that, right. We wanted this to be alive living thing with a real community. Uh, that took root in a different way than MapReduce, Hadoop sort of situation. Um, so that was very much front of mind as we work through what are we going to build, how are we going to build and how are we going to manage it? How are we going to build a community? How, how do you get people involved? How do you find folks like Gaiman and Deus and get them to say we're in, we want to be a part of this. >>All right, so Gabe, it was actually Joe corrected me when I said, well, Google started it and they pulled in some other like-minded vendors. Like he said, no, no stew. We didn't pull vendors in. We pulled in people and people that believed in the project and the vision, you were one of those people that got pulled in early. He were, you know, so help give us a little context in your, your viewpoint. I did. And, and, and you know, at the time I was working for a company, uh, called, uh, that I had started and we were out there trying to make developers more productive in industry using modern technology like containers. And you know, it was through the process of trying to solve problems for customers, sort of the lens that I was bringing, uh, to this where, um, I was introduced to some really novel technology approaches first through Docker. >>Uh, and you know, I was close with Solomon hikes, the, the founder over there. Uh, and then, you know, started to work closely with folks at Google, uh, namely Brendon burns, who I now work with at Microsoft. Um, you know, part of the, the founding Kubernetes team. Uh, and I, I agree with that statement that it is really about people. It's really about individual connections at the end of the day. Um, I think we do these things that at these coupons, uh, events called the contributor summits. And it's very interesting because when folks land at one of these summits, it's not about who you work for, what Jersey you're wearing, that sort of thing. It's people talking to people, trying to solve technical problems, trying to solve organizational challenges. Uh, and I think, you know, the, the phenomenon that's happened there and the scale with which that's happened is part of the reason why there's 8,000 people here in Barcelona today. >>Yeah. It's interesting to him cause you know, I used to be involved in some standards work and I've been, you know, working with the open source community for about 20 years. It used to be ah, you know, it was the side project that people did at nights and everything like that. Today a lot of the people that are contributing, well they do have a full time job and their job will either let them or asking them to do that. So I do talk to people here that when they're involved in the working groups, when they're doing these things, yes. You think about who their paycheck comes for, but that's secondary to what they're doing as part of the community. And it is, you know, some of the people what, what >>absolutely. It's part of the ethos of the project that the project comes first and if company comes second or maybe even third. Uh, and for the most part, this has been wildly successful. Uh, there's this huge base of trust among, uh, among the leadership and among the contributors. Um, and you know, it's, it's a big enough project now that I don't know every one of the contributors, but we have this web of trust. And, you know, I, I have this, this army of people that I know and I trust very well and they know people and they know people and it works out that the project has been wildly successful and we've never yet had a major conflict or strife that centered on company this or company that. >>Yeah. And I don't, I'd also add that it's an important development has happened in the wake of Kubernetes where, you know, for example, in my teams at Microsoft, I actually have dedicated PM and engineering staff where their only job is to focus on community engagements, right? Running the release team for communities one 15 or working on IPV six support or windows container support. Uh, and, and that work, that upstream work, uh, puts folks in contact with people from all different companies, Google, uh, uh, you know, Microsoft working closely together on countless initiatives. Uh, and the same is true really for the entire community. So I think it's really great to see that you can get not just sort of the interpersonal interactions. We can also get sort of corporate sponsorship of that model. Cause I do think at the end of the day people need to get their paychecks. Uh, and oftentimes that's going to come from a big company. Uh, and, and seeing that level of investment is, I think, uh, pretty encouraging. Okay. Well, you know, luckily five years in we've solved all the problems and everything works perfectly. Um, if that's not maybe the case, where do we need people involved? What things should we be looking at? Kind of the, the, the next year or two in this space, you know, a project >>of this size, a community of this size, a system of this scope has infinite work to do, right? The, the, the barrel is never going to be empty. Um, and in some cases it's filling faster than it's draining. Um, every special interest group, every SIG, it has a backlog of issues of things that they would like to see fixed of features that they have some user pounding the table saying, I need this thing to work. Uh, IPV six is a great example, right? And, and we have people now stepping up to take on these big issues because they have customers who need it or they see it as important foundational work for building future stuff. Um, so, you know, there's, there's no shortage of work to do. That's not just engineering work though, right? It's not just product definition or API. We have a, what we call a contributor experience. People who work with our community to entre online, uh, new contributors and um, and, and streamline how to get them in and involved in documentation and testing and release engineering. And there's so much sort of non-core work. Uh, I could go on on this for. >>Yeah, you're just reminding me of the session this morning is I don't manage clusters. I manage fleets. And you have the same challenge with the people. Yeah. And I also had another dimension to this about just the breadth of contribution. We were just talking before the show that, um, you know, outside at the logo there is this, uh, you know, characters, book characters, and such. And really that came from a children's book that was created to demonstrate core concepts, uh, to developers who were new to Kubernetes. And it ended up taking off and it was eventually donated to the CNCF. Um, but things like that, you can't underestimate the importance and impact that that can have on making sure that Kubernetes is accessible to a really broad audience. Okay. Uh, yeah, look, I want to give you both a, just the, the, the final word as to w what you shout out, you one for the community and uh, yeah. And any special things that have surprised you or exciting you? Uh, you know, here in 2019, >>uh, you know, exciting is being here. If you rewind five years and tell me I'm going to in Barcelona with with 7,500 of my best friends, uh, I would think you are crazy or are from Mars. Um, this is amazing. And uh, I thank everybody who's here, who's made this thing possible. We have a ton of work to do. Uh, and if you feel like you can't figure out what you need to work on, come talk to me and we'll, we'll figure it out. >>Yeah. And for me, I just want to give a big thank you to all the maintainers folks like Tim, but also, you know, some other folks who, you know, may, you may not know their name but they're the ones slogging it out and to get hub PRQ you know, trying to just make the project work and function day to day and were it not for their ongoing efforts, we wouldn't have any of this. So thank you to that. Well and look, thank you. Of course, to the community and thank you both for sharing with our community. We're always happy to be a small piece of a, you know, helping to spread the word and uh, give some voice to everything that's going on here. Thank you so much. All right, so we will be back with more coverage here from coupon cloud native con 2019 on Stu Miniman and thank you for watching the cube.

>> Announcer: Live, from Austin, Texas, it's theCube, covering KubeCon and Cloud Native Con 2017. Brought to you by Red Hat, The Linux Foundation, and theCube's ecosystem partners. >> Welcome back everyone, live here. This is theCube's exclusive coverage, live in Austin, Texas for Cloud Native Con and KubeCon with The Linux Foundation. I'm John Furrier, the founder. Silicon Angle Media, my cohost Stu Miniman, and next to us Joe Beda, who's the co-founder, co-founder and CTO of Heptio With Craig McLuckie, the famous startup that came out of the Google team, really one of the principal founders of Kubernetes with Craig and the team Brendon Burns and the like. Great to have you on theCube, thanks for coming on. >> Thank you very much for having me, it's exciting. >> Good time, first time on theCube, glad to have you, we've been trying to get your perspective because obviously we're fans of the Kubernetes, I just had Lou Tucker on, we were talking interclouding and some orchestration opportunity. You guys had that vision and it's really important to tell the story, at the beginning with Kubernetes. You guys were sitting around, having a little beer, free food at the Google cafeteria, what was it like? What happened? How did it all come together? >> All right well, I started at Google probably 10, 12 years ago, did a whole bunch of stuff but eventually landed doing cloud. Craig and I started up a Google compute engine, VM as a service and the odd thing to recognize is that nobody who had been at Google for a long time thought that there was anything to this VM stuff. Because Google had been on containers for so long, that was their mindset, Borg was the way that stuff was actually deployed, so my boss at the time, who's now in Cloud Era booted up a VM for the first time, and anybody in the outside world would be like hey, that's really cool and his response was like, well now what? You're sitting at a prompt, that's not super interesting, how do I run my app? That's what everybody's been struggling with with Cloud, it's not how do I get a VM, how do I actually run my code? As Google got more and more serious about Cloud, every big company wants to dog food their products. How do we make the experience that folks inside of Google have, developers inside of Google have, match the experience that Cloud customers have? The choice there was either we make everybody inside of Google start using VM's which would have felt like that step backwards, or we teach the rest of the world about Borg. Now around the same time, docker started getting a lot of attention and we were like hey, those guys are onto something, they really found a good way to make this technology accessible to users on a single node level, but our experience at Google really taught us that that clusters you, how do you actually create this abstraction that a whole bunch of computers are one thing that you operate with? That was the thing that was going to be interesting and so out of that, we decided Kubernetes was going to be the thing or at least getting Borg out to the rest of the world, and we knew for it to be effective, it couldn't just be Google doing it alone, we had to do it in a way that would bring the rest of the industry with us. That's the motivation behind Kubernetes. It took us about another three months to convince all the folks at Google that this was a good idea, it was controversial, the open source projects at the time were things like, the biggest things would be like Chrome and Android. Those things were, the relationship with their community was very different from what we were aiming for with Kubernetes, they were much more consumer focused versus infrastructure focused. >> It was early too for Google to recognize the multi cloud world. >> I think some it wasn't so much multi cloud as much as developers have a really strong sense of where the lock in is, where the vendor lock in is, and we knew that if we wanted to win the hearts and minds of engineers and developers and folks that took this stuff seriously, as the underdog in the cloud world at the time, you had to really go out there and build something that was going to be widely applicable. Because you don't want to invest your time and energy into something that's super specialized to one cloud and I think the whole multi cloud thing, honestly I think it's engineers and developers and operations folks that had that sense from the get go, we were just reacting to that. >> Good instincts too. Kubernetes certainly working out today, state of the union, cause we're still only less than three years old as a community, seems like 20, but the momentum's been amazing, has been a lot of revision, a lot of people have their own versions of Kubernetes, yet there's a core, vanilla Kubernetes, but it's working. People have gotten around this. What is the big thing that has surprised you the most and where are you most excited right now, where Kubernetes is at? >> Okay surprise, there's 4100 people here at KubeCon, that's absolutely insane. I think we had this idea that it could be a thing and that, but I don't think that any of us imagined that within three years we'd be sitting here, doing this type of thing. That I think for me is the most surprising. It's a challenge to take these ideas that have been successful inside at Google and translate those to the rest of the world and it wasn't an easy or obvious thing, there were a lot of good ideas but figuring out how to get those out there, I think that really is due to the larger community. Folks like Clayton Pullman from Red Hat coming in early with a lot of that really brought a lot of that outside DNA necessary to bridge that gap. Surprising that we got here, but really it took the community to make that happen. In terms of what I'm most excited about right now, with the announcement of EKS from Amazon, it definitely feels like we're moving into a new phase of Kubernetes where folks are being much more focused on what do you do with Kubernetes versus how do you get Kubernetes running. Kelsey tweeted it the other day, but I think we've been saying for a while, Kubernetes at its heart is a platform for building platforms, really we viewed it from the start as a toolbox and I think we're only now starting to see, what other things are people going to be building with that toolbox and I think that's going to be that larger ecosystem, is going to be much larger than Kubernetes itself. >> Joe, coming into this show, there were so many announcements around Kubernetes, there's like 42 certified different versions out there. I think you could help explain a little bit because there's the big cloud guys, you mentioned Clayton who we had earlier from Red Hat, there's all these companies, oh well, Kubernetes is just like it's a piece and it's in there. Your company is around Kubernetes, so what does this mean that Kubernetes is, I guess we'd say commoditized across there, I think it's a good thing for the industry, but what does it mean, why is there a need for Heptio and what do you guys see as your role in the ecosystem? >> There's a bunch of folks that are really concentrating on how do I get Kubernetes up and running and that's one thing, and I think that landscape is going to be changing and evolving over time. We're definitely happy to help folks be successful with Kubernetes, it's one of those things we're going to do, we're going to do an open source project, services, support and training with that, but when we look forward, I think a big part of it is, how do we bridge the gap to integrate Kubernetes into businesses, how do we start building those next layer tools on top of it and to some degree, it's a wild west. There's those 42 companies, everybody's trying to actually find something that's going to be interesting, start solving problems, but the thing that's really encouraging to me is that Kubernetes is the base and we're doing work, both Heptio and the community around conformance to make sure that we actually have a solid base that folks can build on top of. Then everybody's focused on how can we actually capture the attention of developers, how can we actually deliver value there and so that's a really great dynamic, when everybody's like I want to do something really great that people are going to get a lot out of, only good things are going to come from that. >> Yeah and I liked, there was a concern some people had, oh last week AWS is now all in, they've got EKS, but you had an announcement about the Heptio authenticator open source authentication, a little bit of a partnership with AWS it looked like. Maybe explain, it sounds like one of the things you're building on top of this. >> Yeah exactly. Like everybody else, we had heard all the rumors, hey is Amazon going to do a Kubernetes offering or not. In our mind, there were two ways. >> Didn't they have to Joe? >> Well that's what I thought last year, but who knows, I think Amazon doesn't have to do anything but when we first started Kubernetes, we reached out to the folks at Amazon including Deepak and we're like hey, you guys are welcome, come join us here and they were like yeah, yeah, we'll join you when the customers are asking for it. Well it turns out the customers were asking for it, so here they are and I think it's a great thing. I think it could've gone two ways, they could have built in a bunch of integrations into Kubernetes that were only available through EKS that really made EKS a more integrated, better Kubernetes than running open source Kubernetes on top of Amazon, or they could've worked with the community, with upstream to try and make Kubernetes run great on Amazon, better on Amazon as is but then run even better when you're running it with EKS and they actually have the management on top of it. I think they decided to go that second route which is much more community friendly. A couple weeks before the announcement, they reached out to us, said hey, we noticed you had this project, it looks really interesting, we need a way to bridge IM to authenticate to Kubernetes and we like the approach that you're taking, can we work together to continue to develop this and that was the first signal to us that they wanted to really reach out and work with the community and so we're like hey, that sounds great, let's work together and get that stuff out there. It's still very early, I think EKS is GA next year, they set an aggressive goal for themselves, so I'm really looking forward to see where they take that and we're going to partner with them where it makes sense around things like authenticator. >> You mentioned we're going to a whole other level with Kubernetes and Amazon's announcement goes to the next level, you also mentioned you worked at Google Compute, Apple, all these other cool names with Google and you got Heptio, you're solving making interesting things happen with Kubernetes and you got a new class of developers coming in that have never heard of what a local director is. Infrastructure as code is happening, so you got the cloud game going on. I got to ask you, as Kubernetes starts to continue to take shape, a lot of people are trying to survive. In this technical architecture decisions, almost a tech chess game, which side of history will you be on thing going on and customers want more clarity. You have a lot of movement and customers want clarity. How do you see it continuing and what is the right path in your mind because it's looking good right now and commoditization as some say, I think is a good thing because value, there's value in interoperability, there's value in orchestration, there's value in a new class of web developer creating, solving problems with code, whether it's societal problems or other things, so there's a lot of big picture, wholistic things happening and Kubernetes kind of strikes at the heart of that. What's the right path in your mind, what's the vision you think Kubernetes should go into. >> Well I think first of all, I think change happens in the industry both fast and slow. It feels like it's been three years since Kubernetes, since we open sourced Kubernetes, and it's come a huge way since then. That happened really fast. You look at Enterprise, you look at Enterprise adoption cycles, I believe last I heard the mainframe division was a growing profit center for IBM. This stuff doesn't go away so as we see things like containers and Kubernetes and serverless and cloud, as we see these things come on the scene, it doesn't necessarily replace stuff, it augments and it adds over time so we see the mix of where people invest shift. In that way, things become established quickly, but old things go away slowly. I don't think it's going to be as quick of a shift as maybe it might seem at first. Now in terms of where the opportunities are moving forward and where we see this developing, the thing that's exciting for me is as we have, and this is something early on, talking with Brendon, he got super excited about, is as we provide new abstractions, as we provide a new toolbox, how do people start creating systems and applications that take advantage of that. I'll give you an example, distributed systems, pre-systems like Kubernetes were very difficult because not only did you have to do the thing that you wanted to do, you had to build all of this plumbing to actually get your things to talk to each other, the finds, the secure, all that stuff had to be created from scratch and those systems were rare and hard to manage and few and far between. Now with things like Kubernetes, there's a whole set of problems that you actually don't have to solve. The floor that you need, the floor is that much higher for building these systems so I think we're going to see a shift not just to cloud native, but I also think we're going to see a set of applications that are Kubernetes native. These are applications that assume that Kubernetes is the substrate that they're running on, and they take special advantage of it and I think we're going to see amazing thing happens when we really democratize the plumbing for building distributed systems. >> And that's the key, make that frictionless so if people want to go Kubernetes native, they're taking advantage, that's cool. I want to get to, to take that to the next level, as the world of IOT comes down, you can almost look at the world now as all IOT. There's no on prem and there's no cloud. If you believe this service mission unpluggable architectures, you could argue that a data center is a network point, it's an attached device to a myriad things, so you're going to need policy, the light bulb has a process in it, the wifi has wifis everywhere, so in a way, this is all going to be a grid if you will, it's going to be kind of a mesh. This is the right direction don't you think, the more services that come online, you just want to connect to them. That's the nirvana right? Are we smoking the peace pipe here too much? >> I think there's a bunch of trends that we're seeing happen there. I think with IOT, we see also a move towards edge computing, this idea of, we're going to see much more stuff happening in a more distributed manner. Whether that edge happens to be in your house or whether it's in a telecom cabinet or whether it's just mini data centers that are dropped in to parking lots here and there. That introduces a whole bunch of new problems in terms of how do you manage that stuff at scale. One of the things that I see is that we're seeing an interesting overlap between CDM providers and cloud providers, so you have cloud flare introducing their cloud workers, where you can start running actual code in their CDM nodes and that's the culmination of CDM providers over time fighting with each other to drive more and more customization. On the other hand, you have Amazon taking lambda, finding ways to actually use lambda and push that out to the edge, even into devices that are doing local machine learning. There's this overlap between these two different worlds. Then also, as we move stuff closer out to the clouds, the political situations that people deal with become that much more complex. As you start running compute in all these different countries, all of a sudden you can't necessarily go to one provider to actually deal with all of that. We're moving from this world where, when you're centered around data which is the traditional cloud, when you want to put it all in one big pile with compute around the edges, that's kind of like the traditional data center. Going with a few large providers makes a ton of sense. As we move towards a much more distributed world, it becomes a more distributed problem both in terms of how do you manage the compute, but how do you manage the relationships and how do you actually understand what's happening across all that and I think Kubernetes can be a part of that puzzle for sure, but it's not the end of the answer, there's still a lot of problems to be solved there. >> No but you get the first mile post. You can say hey, I can start orchestrating workloads and have endpoints that have services that talk to each other as the first step. >> Joe, one thing I wanted to ask you, what are the stumbling blocks? What do people need to look out for? Because most companies out there aren't Google. >> This morning at today's keynote and you can find it online, there's that cloud native road map that Dan was showing. That is an interesting thing that cuts both ways. On the one hand, it shows an enormous amount of innovation, it shows that we're seeing this explosion of interest in this world and it's really invigorating. That's from an entrepreneur's view and a technologist's view. If I'm a customer, that thing's kind of horrifying. I look at that and I say wow, I really have to understand all of this stuff to get ahead? I think the biggest stumbling block is really being able to make sense of all the noise out there. I think that noise is part and parcel of an active, innovative, chaotic ecosystem, but I think it's one of those things that makes it that much harder for enterprises and for more mainstream developers to adopt. Tim, we've been saying this for a while, for Kubernetes to be successful, we had to make it boring. That's Tim Hawkin, I think maybe was the first one to say that, but we not only had to make Kubernetes boring, we had to make that entire stack boring, we had to make cloud native boring. That's when it will have succeeded. I don't know what this conference will look like when cloud native is boring, but it'll probably be very different than. >> It'll certainly create some excitement, boring is reliable, boring is safe, boring is secure, boring is comfortable. Mark Zuckerberg once said move fast, break stuff, then he revised it to move fast and be 100% reliable. That's boring. >> Did he actually say that? >> I don't know, he shifted his narrative because that was the maverick early days when he started running at five nines it's like a whole nother ball game. >> Actually that matters. >> Joe, great to have you on theCube, thanks for sharing your awesome insight into the dynamics of the computing industry that's going cloud native, going KubeCon, and certainly Kubernetes that you helped put together with the team, it's certainly taken on a life of its own, last minute, take a minute to talk about Heptio, what you guys are working on, get the plug in. >> Yeah Heptio, we have services, support and training that we're offering to make customers successful with Kubernetes today and that's been invigorating, really getting out there and talking with folks, seeing the problems that they're hitting now versus where we want it to go. We're doing a bunch of work around open source projects, we have Heptio Arc which is a backup disaster recovery project open source, we have Sona Boy, which is a diagnostic project for running the conformance tests and it underpins the Kubernetes conformance effort. We have K Sonic which helps you configure applications and then we also have Contour, which is an ingress controller building on top of Envoy and other CNCF project and then into 2018, we're going to be offering more products and projects and services that really start targeting the special needs of larger and larger enterprises and that's where our focus is going to shift over time. >> You guys are certainly helping customers who are under pressure to add more services, including what Amazon's doing, more pronouncements, there are little announcements, some big some little, but still, the cadence of new things happening is fast at all times right now. >> I can't keep up either, nobody else can. >> We try. Two and a half hour keynote, it's ridiculous. Joe Beda here inside theCube, cofounder CTO of Heptio a hot startup, making Kubernetes interesting and exciting and reliable and boring. Not boring, we should say that. >> Oh boring's good. >> Infrastructure's good, it's theCube, bringing you all the live action from Austin, Texas, I'm John Furrier, Stu Miniman, KubeCon and Cloud Native Con, we'll be right back after this short break.