>> Announcer: Live from the Computer History Museum in Mountain View, California. It's theCUBE, covering DevNet Create 2018, brought to you by Cisco. >> Hi there and welcome to the special CUBE live broadcast here at the Computer History Museum in Mountain View, California, It's theCUBE's exclusive coverage of Cisco's DevNet Create. This is Cisco's developer ecosystem brand new, second event that they've done, and it's one and a half years in existence. This is Cisco's extension to their DevNet developer program, which is mostly Cisco developers, mostly networking, and theCUBE is here covering the future of cloud native Kubernetes, and the future of application development, as networks become more programmable. I'm John Furrier, your host, with Lauren Cooney, analyst today co-hosting with me, all day coverage. Our guest is Allan Naim, who is the product manager at Google Kubernetes engine, at Google, right down the street here. Allan, great to have you, thanks for joining us. >> Yeah, thanks for inviting me. >> So, you are the key man with the fireside chat with Susie Wee who is heading up this whole program, doing an amazing job. Google's no stranger. We all know Google at the scale level, massive scale, running infrastructure, building your own stuff, really inventing the category and then fast followers, Facebook among others, large scale. So, you guys invented Kubernetes. So that's a fact. So, tell the story of how it started because there was a moment in Google where Kubernetes, there was a debate. Do we keep it internally, open it up? And you guys have history. You've created MapReduce, you've created the data surge that we're seeing now and changing the game there. Maybe a little bit differently than how Kubernetes is handled. What's the inside story about the creation of Kubernetes and how it's evolved? >> Yeah, so Google has been working with containers for a long, long, time. It's nothing new to Google, and we wanted really to take a lot of the best practices associated with how we manage and run containers internally and share that with the community as a whole. What we found initially was the move to the cloud was very much traditionally a lift and shift and modernized move. And, there's a reason why only, I think the latest statistic I've seen is less than 10% of the applications have actually moved to the cloud. What about the other 90%? So, we wanted to bring some of the magic that Google uses internally and bring that to the world, right, so that you can modernize wherever you're running, right, for those applications that can't just move to the cloud. Why not provide a way to take advantage of some of the innovations that we've created around packaging applications up, deploying applications very seamlessly, and then eventually moving them to the cloud with less friction? And that was really behind the reason we took Kubernetes, which is really a set of best practices around how Google runs and operates containers, and made it available to the open source community. We could've kept it internally, right, and not shared it with the community, but then that really stifles innovation. Google is not about stifling innovation. We're about enabling the community to really drive innovation and build an ecosystem around it. And looking back now, it was a tremendous move. >> Yeah, and you know what, the leadership I remember at that time, and I wanted to get that out there. Thank you for sharing that. Craig McLuckie, Brendan Burns, Joe Beda, those guys and the team around them, it was kind of a small team, held the line on that. And the conversation was, this needs to happen in an open way mainly because you saw, though, how to manage your workloads internally and wanted to bring it to the masses. So, real props to the original team, a really good call, and again, it worked out great. >> Yes. >> So, okay, today. Where are we today? Because now you go back at the creation of Kubernetes, you guys open it up, still contributed and nurtured it, and now it becomes part of the bigger part of the open source community. You have now new innovations. What is the update from your standpoint where Kubernetes is today? Okay, it's well know that the containers is now standard and standard. Now the business model container hasn't materialized. That's okay. The technical architecture is very solid. Kubernetes has become the favorite child in the architecture because of the benefits. What's the update? What's Kubernetes doing today that's compelling? What's the update? >> Yeah, so just as you said, containers are mainstream now. Kubernetes is on fire. We see a world today where Kubernetes is literally running everywhere, right, from Google Cloud to other clouds to partnerships that we have with the likes of Cisco. You now have these clusters that are popping up in heterogeneous environments. So, we've enabled developers now to really build services very efficiently and update those services in a consistent manner regardless of where those services are running. Now, as you build more and more clusters and expose more and more services, the day two experience starts coming in, right? How do I manage this environment? How do I manage my services? How do I find out what these services are actually doing, which services are talking to each other? How do I do more of the networking aspect around traffic management? And this is where I see a lot of the investments happening right now in the open source world with projects like Istio, which are fairly new, but are taking a lot of the goodness that Kubernetes is bringing and applying more of an operations mindset around networking. >> And what problem is that solving? Can you be specific? Because I like this day two experience. I mean, day three will be like, oh my God. How do you manage it beyond that, but, what is the problem that's being solved? Is it more industrial strength, is it more tolerance? Is it securities or all the above? What's the main problem? >> It's security, it's when you're running services in heterogeneous environments, there is no consistent security model, right? Istio helped solved some of that. It's service discovery. When services are running, again, in environments where you have different mechanisms for storing services, how do you discover these services? Now, how do you route traffic to the right service? How do you do canary deployments where perhaps I'd like to trickle certain load onto a new version and eventually move all my work into the new version that I've deployed? So, canary testing. Running services in geographic locations and using networking algorithms to route my requests to the closest location. Those are all really hard challenges that you need to solve, and technologies like Istio really make it possible for developers to get those benefits without having to write a single line of code, right? So, you leverage the API to get all these benefits that I just talked about. >> I want to get you in for a minute to talk about that if we can. Talk about Google cloud right now vis a vis the momentum because a lot's changed with Google just in the past couple of years. A lot of people on board, new hires, industry veterans, leaders. We've heard Lou Tucker from Cisco say at CubeCon that Istio is probably the biggest thing he's seen in years in terms of its implementation capability to impact the valued creation of application developers and also in creating efficiencies in networks. How is the Google team right now doing? Give an update, because you guys are now in the center of it and I've called you guys, the real competitor to Amazon, because I consider you and amazon probably the coolest cloud and most relevant clouds vis a vis what clients want to do in a modern era. Not so much retrofitting legacy cloud to make it kind of retrofit, but really doing ground zero cutting edge cloud stuff. What's the update from Google Cloud? What are you guys most proud of? What's the things that you want to highlight that are notable? >> So, Google Cloud's been growing at a tremendous rate. It's just mind-boggling how fast customer adoption has been. What we've seen is, the adoption has spanned all the way from startup to small, medium-sized businesses, extending into the Fortune 100s regardless of industry. And what we hear from customers is they like the clean APIs that Google provides. They like our compute infrastructure from a resiliency standpoint, the transparency that we provide in terms of enabling customers in running their workloads on Google Cloud. We've made a lot of investments in Google Cloud and we continue to make these investments. Now, on the cloud native and container fronts, what we're doing and what we're focusing on is really a differentiated model where we are working with customers to enable them to modernize in place and move to the cloud at their own pace versus having to lift and shift an application to take advantage of modernization and APIs in the cloud. That's really a differentiating story that we're bringing to the table. Along with that, we continue to invest in storage, in optimizing our networking, in setting up more and more points of presence around the world. We added, I believe, over 12 zones last year around the world. So, the growth rate has just been phenomenal. On the Kubernetes side, it's all about value, right? It's all about differentiated value as well. Google has been operating a managed Kubernetes service now for over two years. Building and providing a managed service is hard, right? We have the expertise to do that. We feel that Google Cloud is the best environment on the planet for running containers. And through this expertise, we'll continue to invest to bring our services and make it a first class experience to run managed scale containers as well. >> So, would it be safe to say that you guys are focused on differentiating and not trying to be the whole world, everything to everybody, to really kind of narrow the focus? >> Well, there are table stakes that you need to address, especially around storage and networking, and we feel we've gotten there, right? Now, for a customer that's picking a cloud, whether it's Google or any other cloud, we've addressed those table stakes. But on the cloud native side of the house, when building containerized applications, we feel that we have a differentiated offering that really no other cloud on the planet can deliver on. >> That's awesome. Let's talk about, and my last question is mush more about developers' relationship to the new architecture. We'll call this the new architecture. >> Yeah. >> You've got Kubernetes which has done some great innovate work, containers continue to be a great resource aspect of architecture, and storage infrastructure becoming more programmable like what Cisco's offering. Great stuff. App developers. I just want to write code. So, you've got some developers. How does a developer, in your opinion, Google's opinion, yours and Google's opinion, how do they determine their relationship to the network or the new architecture? You've got some guys who just want to write apps. So, I don't want to do any kind of speeds and feeds. Some guys want to get down and dirty and wire up some services when you get in the middle layer, and some might want to get down low in the stack. How does a developer kind of peg their orientation to different parts of the cloud architecture? >> So, when you really think about it, Kubernetes is a logical layer that sits on top of infrastructure that makes it possible to take an application that runs a certain way in one location to run consistently in other locations. So, for application developers that just want to write code, we've got a clean set of APIs that they can take advantage of to spin up cluster resources, deploy their applications. We've been heavily focused as well on not just creating an amazing story for stateless applications, but stateful applications as well. So, being able to orchestrate, you choreograph your application deployment. Now, for developers that want to get their hands dirty, the way we've designed Kubernetes is very much an extensible model. So, the Kubernetes APIs can be extended and functionality can actually be over written to tailor the experience. A developer may want to plug in a different type of controller, for example, versus the standard Kubernetes controller. So, we enabled that, think of it as a peel the onion approach, so that we can meet the developer where they are and give them the tools required for them to actually be productive in their companies or in the community. >> Awesome. Right, and you guys have a deal with Cisco, or relationship with Cisco, or else you're here, at the DevNet Create event, which is about cloud native, not so much about being kind of Cisco or DevNet, the classic developer program. On stage you talked about Istio. Is that the key to the partnership with Cisco? What specifically is your relationship to Cisco? >> Yeah, it's a great question. So, with Cisco, we've been hearing from customers a lot that getting Kubernetes up and running on premise is really hard. We've also been hearing a lot from customers that they want support. So, we got together with Cisco to provide a hybrid offering that tailors customers that want to start their journey to cloud native on prem. So, Cisco basically provides a mechanism, right, for customers to actually run Kubernetes on prem with a single support model for all their needs, which is great for Google because this is something that Cisco-- >> They know a lot about that. >> Absolutely. Now, for customers that want to start building in the cloud and connecting to the cloud, but you need secure performance networking. How do you do that, right? Well, Cisco is an innovator in networking and security. Google is an innovator in cloud and open source technology and cloud native technology. So, we bring these two things together to give really developers and sys admins a world where they can collaborate and have an API-driven approach to running workloads that span a hybrid estate. >> John: And it's great for you guys too. You open up your market to the enterprise. >> Yeah, I would say that also it really gives an opportunity for network engineers and developers, and I think you talked about clusters ops and Arkino and new types of app ops that you're bringing to the table-- >> Yep, yes. >> And what kind of roles do you see these people playing as you grow that ecosystem? >> Exactly. It's not just about the technology, but it's the culture within the company that oftentimes really drives, it's a hard obstacle to bypass. For customers that I talk to, a lot of times they tell me, look, we've settled. We want to go with Kubernetes, but what about the internal culture? How do we build our teams around Kubernetes? How do we scale our services in such a way where we have specialization of service?kino And I talked about Narkino, the whole notion of separation of concerns where we introduce this new notion in terms of how Google does things of an application ops team that's typically small in size, but their role starts where the developer role ends, and basically, they're responsible for taking an application from a developer and deploying it out into a environment. Then you have a cluster ops role team that's focused on the underlying infrastructure and maintains all the various cluster APIs, the Kubernetes environment. So, think of them as shared services that are very much tailored to enabling developers to do what they do best and build great applications and push changes in production very quickly. >> Well, thanks for coming out to theCUBE. I know you've got another hard stop. You're got another panel. Real quick, I'll give you the final word. What's the one thing people should know about Google Cloud that they may not know about or gets buried in the noise out in the marketplace? >> Yeah. Google Cloud is the most innovative cloud out there on the market. We have points of presence in literally every region around the world. Our APIs are some of the cleanest out there of any cloud, as well as the Kubernetes experience running in Google has been something that we've been invested in for over two years and it's actually a highly optimized experience for developers that want to run their containerized application and very differentiated. And 100% upstream compatible with Kubernetes open source. >> That's great stuff. I got to tell you, just Google team, we covered all the cloud players from day one. There's no shortcut. You've got to put the work in, whether it's public sector or getting the building blocks in there. You guys do a great job. Congratulations. >> Thank you. >> Kubernetes is worth noting. theCUBE covering all the action, and the story here is Kubernetes, Google's creation, which is now open standard for all, 100% upstream compatible here at the Cisco's DevNet Create event. Back with more live coverage. I'm John Furrier with Lauren cooney after this short break. (upbeat music) [Announcer] In center.