>>Hey guys. Welcome back to Detroit, Michigan. Lisa Martin and John Furrier here live with the cube at Coan Cloud Native Con North America. John, it's been a great day. This is day one of our coverage of three days of coverage. Kubernetes is growing up. Yeah, it's maturing. >>Yeah. We got three days of wall to wall coverage, all about Kubernetes. We about security, large scale, cloud native at scale. That's the big focus. This next segment's gonna be really awesome. You have a fast growing private company and a practitioner, big name, blue chip practitioner, building out next NextGen Cloud first, transforming, then building out the next level. This is classic of what we call super cloud-like, like interview. It's gonna be great. I'm looking forward >>To this anytime we can talk about Super Cloud. All right, please welcome back. One of our alumni, Bani is here, the CEO of Rafe. Great to see you Santos. Ula also joins us, the global head of Cloud SRE at Mass Mutual. Ge. Great to have you on the program. Thanks >>For having us. Thank you for having me. >>So Steve, you've been on the queue many times. You were on just recently with the momentum that that's around us today with the maturation of Kubernetes, the collaboration of the community, the recognition of the community. What are some of the things that you're excited about with on, on day one of the show? >>Wow, so many new companies. I mean, there are companies that I don't know who are here. And I, I, I live in this industry and I'm seeing companies that I don't know, which is a good thing. I mean, it means that the, the community's growing. But at the same time, I'm also seeing another thing, which is I have met more enterprise representatives at this show than other coupons. Like when we hung out at, you know, in Valencia for example, or even, you know, other places. It hasn't been this many people, which means, and this is, this is a good thing that enterprises are now taking Kubernetes seriously. It's not a toy. It's not just for developers. It's enterprises who are now investing in Kubernetes as a foundational component, right. For their applications going forward. And that to me is very, very good. >>Definitely becoming foundational. >>Yep. Well, you guys got a great traction. We had many interviews at the Cube and you got a practitioner here with you. You guys are both pioneering kind of what I call the next gen cloud. First you gotta get through gen one, which you guys done at Mass Mutual, extremely well, take us through the story of your transformation. Cause you're on the, at the front end now of that next inflection point. But take us through how you got here. You had a lot of transformation success at Mass Mutual. >>So I was actually talking about this topic few, few minutes back, right? And, and the whole cloud journey in big companies, large financial institutions, healthcare industry or, or our insurance sector. It takes generations of leadership to get, to get to that perfection level. And, and ideally the, the, the cloud for strategy starts in, and then, and then how do you, how do you standardize and optimize cloud, right? You know, that that's, that's the second gen altogether. And then operationalization of the cloud. And especially if, you know, if you're talking about Kubernetes, you know, in the traditional world, you know, almost every company is running middleware and their applications in middleware. And then containerization is a topic that come, that came in. And docker is, is you know, basically the runtime containerization. So that came in first and from Docker, you know, eventually when companies started adopting Docker, Docker Swarm is one of the technologies that they adopted. And eventually when, when, when we were taking it to a more complicated application implementations or modernization efforts, that's when Kubernetes played a key role. And, and Hasi was pointing out, you know, like you never saw so many companies working on Kubernetes. So that should tell you one story, right? How fast Kubernetes is growing and how important it is for your cloud strategy. So, >>And your success now, and what are you thinking about now? What's on your agenda now as you look forward? What's on your plate? What are you guys doing right now? >>So we are, we are past the stage of, you know, proof of concepts, proof of technologies, pilot implementations. We are actually playing it, you know, the real game now. So in the past I used the quote, you know, like, hello world to real world. So we are actually playing in the real world, not, not in the hello world anymore. Now, now this is where the real time challenges will, will pop up, right? So if you're talking about standardizing it and then optimizing the cloud and how do you put your governance structure in place? How do you make sure your regulations are met? You know, the, the, the demands that come out of regulations are met and, and how, how are you going to scale it and, and, and while scaling, however you wanna to keep up with all the governance and regulations that come with it. So we are in that stage today. >>Has Steve talked about, you talked about the great evolution of what's going on at Mass Mutual has talked a little bit about who, you mentioned one of the things that's surprising you about this Coan and Detroit is that you're seeing a lot more enterprise folks here who, who's deciding in the organization and your customer conversations, Who are the deci decision makers in terms of adoption of Kubernetes these days? Is that elevating? >>Hmm. Well this guy, >>It's usually, you know, one of the things I'm seeing here, and John and I have talked about this in the past, this idea of a platform organization and enterprises. So consistently what I'm seeing is, you know, somebody, a cto, CIO level, you know, individual is making a determin decision. I have multiple internal buss who are now modernizing applications. They're individually investing in DevOps. And this is not a good investment for my business. I'm going to centralize some of this capability so that we can all benefit together. And that team is essentially a platform organization and they're making Kubernetes a shared services platform so that everybody else can come and, and, and sort of, you know, consume it. So what that means to us is our customer is a platform organization and their customer is a developer. So we have to make two constituencies successful. Our customer who's providing a multi-tenant platform, and then their customer who's a developer, both have to be happy. If you don't solve for both, you know, constituencies, you're not gonna be >>Successful. You're targeting the builder of the infrastructure and the consumer of that infrastructure. >>Yes sir. It has to be both. Exactly. Right. Right. So, so that look, honestly, that it, it, you know, it takes iterations to figure these things out, right? But this is a consistent theme that I am seeing. In fact, what I would argue now is that every enterprise should be really stepping back and thinking about what is my platform strategy. Cuz if you don't have a platform strategy, you're gonna have a bunch of different teams who are doing different things and some will be successful and look, some will not be. And that is not good for business. >>Yeah. And, and stage, I wanna get to you, you mentioned that your transformation was what you look forward and your title, global head of cloud sre. Okay, so sre, we all know came from Google, right? Everyone wants to be like Google, but no one wants to be like Google, right? And no one is Google, Google's a unique thing. It's only one Google. But they had the dynamic and the power dynamic of one person to large scale set of servers or infrastructure. But concept is, is, is can be portable, but, but the situation isn't. So board became Kubernetes, that's inside baseball. So you're doing essentially what Google did at their scale you're doing for Mass Mutual. That's kind of what's happening. Is that kind of how I see it? And you guys are playing in there partnering. >>So I I totally agree. Google introduce, sorry, Ty engineering. And, and if you take, you know, the traditional transformation of the roles, right? In the past it was called operations and then DevOps ops came in and then SRE is is the new buzzword. And the future could be something like product engineering, right? And, and, and in this journey, you know, here is what I tell, you know, folks on my side like what worked for Google might not work for a financial company, might not work for an insurance company. So, so, so it's, it's okay to use the word sre, but but the end of the day that SRE has to be tailored down to, to your requirements and and, and the customers that you serve and the technology that you serve. Yep. >>And this is, this is why I'm coming back, this platform engineering. At the end of the day, I think SRE just translates to, you're gonna have a platform engineering team cuz you gotta enable developers to be producing more code faster, better, cheaper guardrails policy. So this, it's kind of becoming the, you serve the business, which is now the developers it used to serve the business Yep. Back in the old days. Hey, the, it serves the business. Yep. Which is a terminal, >>Which is actually true >>Now it the new, it serves the developers, which is the business. Which is the business. Because if digital transformation goes to completion, the company is the app. Yep. >>And the, you know, the, the hard line between development and operations, right? So, so that's thining down over the time, you know, like that that line might disappear. And, and, and that's where asari is fitting in. >>Yeah. And they're building platforms to scale the enablement up that what is, so what is the key challenges you guys are, are both building out together this new transformational direction? What's new and what's the same, The same is probably the business results, but what's the new dynamic involved in rolling it out and making people successful? You got the two constituents, the builders of the infrastructures and the consumers of the services on the other side. What's the new thing? >>So the new thing if, if I may go fast these, so the faster market to, you know, value, right? That we are bringing to the table. That's, that's very important. You know, business has an idea. How do you get that idea implemented in terms of technology and, and take it into real time. So that journey we have cut down, right? Technology is like Kubernetes. It makes, it makes, you know, an IT person's life so easy that, that they can, they can speed up the process in, in, in a traditional way. What used to take like an year or six months can be done in a month today or or less than that, right? So, so there's definitely the losses, speed, velocity, agility in general, and then flexibility. And then the automation that we put in, especially if you have to maintain like thousands of clusters, you know, these, these are today like, you know, it is possible to, to make that happen with a click off a button. In the past it used to take like, you know, probably, you know, a hundred, a hundred percent team and operational team to do it. And a lot of time. But, but, but that automation is happening. You know, and we can get into the technology as much as possible. But, but, you know, blueprinting and all that stuff made >>It possible. Well say that for another interview, we'll do it take time. >>But the, the end user on the other end, the consumer doesn't have the patience that they once had. Right? Right. It's, I want this in my lab now. Now, how does the culture of Mass Mutual, how is it evolv to be able to deliver the velocity that your customers are demanding? >>So if once in a while, you know, it's important to step yourself into the customer's shoes and think it from their, from their, from their perspective, business does not care how you're running your IT shop. What they care about is your stability of the product and the efficiencies of the product and, and, and how, how, how easy it is to reach out to the customers and how well we are serving the customers, right? So whether I'm implementing Docker in the background, Dr. Swam or es you know, business doesn't even care about it. What they really care about it is if your environment goes down, it's a problem. And, and, and if you, if your environment or if your solution is not as efficient as the business needs, that's the problem, right? So, so at that point, the business will step in. So our job is to make sure, you know, from an, from a technology perspective, how fast you can make implement it and how efficiently you can implement it. And at the same time, how do you play within the guardrails of security and compliance. >>So I was gonna ask you if you have VMware in your environment, cause a lot of clients compare what vCenter does for Kubernetes is really needed. And I think that's what you guys got going on. I I can say that you're the v center of Kubernetes. I mean, as a, as an as an metaphor, a place to manage it all is all 1, 1 1 paint of glass, so to speak. Is that how you see success in your environment? >>So virtualization has gone a long way, you know where we started, what we call bare metal servers, and then we virtualized operating systems. Now we are virtualizing applications and, and we are virtualizing platforms as well, right? So that's where Kubernetes basically got. >>So you see the need for a vCenter like thing for Uber, >>Definitely a need in the market in the way you need to think is like, you know, let's say there is, there is an insurance company who actually mented it and, and they gain the market advantage. Right? Now the, the the competition wants to do it as well, right? So, so, so there's definitely a virtualization of application layer that, that, that's very critical and it's, it's a critical component of cloud strategy as >>A whole. See, you're too humble to say it. I'll say you like the V center of Kubernetes, Explain what that means and your turn. If I said that to you, what would you react? How would you react to that? Would say bs or would you say on point, >>Maybe we should think about what does vCenter do today? Right? It's, it's so in my opinion, by the way, well vCenter in my opinion is one of the best platforms ever built. Like ha it's the best platform in my opinion ever built. It's, VMware did an amazing job because they took an IT engineer and they made him now be able to do storage management, networking management, VMs, multitenancy, access management audit, everything that you need to run a data center, you can do from a single, essentially single >>Platform, from a utility standpoint home >>Run. It's amazing, right? Yeah, it is because you are now able to empower people to do way more. Well why are we not doing that for Kubernetes? So the, the premise man Rafa was, well, oh, bless, I should have IT engineers, same engineers now they should be able to run fleets of clusters. That's what people that mass major are able to do now, right? So to that end, now you need cluster management, you need access management, you need blueprinting, you need policy management, you need ac, you know, all of these things that have happened before chargebacks, they used to have it in, in V center. Now they need to happen in other platforms. But for es so should do we do many of the things that vCenter does? Yes. >>Kind >>Of. Yeah. Are we a vCenter for es? Yeah, that is a John Forer question. >>All right, well, I, I'll, the speculation really goes back down to the earlier speed question. If you can take away the, the complexity and not make it more steps or change a tool chain or do something, then the devs move faster and the service layer that serves the business, the new organization has to enable speed. So this, this is becoming a, a real discussion point in the industry is that, oh yeah, we've got new tool, look at the shiny new toy. But if it doesn't move the needle, does it help productivity for developers? And does it actually scale up the enablement? That's the question. So I'm sure you guys are thinking about this a lot, what's your reaction? >>Yeah, absolutely. And one thing that just, you know, hit my mind is think about, you know, the hoteling industry before Airbnb and after Airbnb, right? Or, or, or the taxi industry, you know, before Uber and after Uber, right? So if I'm providing a platform, a Kubernetes platform for my application folks or for my application partners, they have everything ready. All they need to do is like, you know, build their application and deployed and running, right? They, they, they don't have to worry about provisioning of the servers and then building the middleware on top of it and then, you know, do a bunch of testing to make sure, you know, they, they, they iron out all the, all the compatible issues and whatnot. Yeah. Now, now, today, all I, all I say is like, hey, you have, we have a platform built for you. You just build your application and then deploy it in a development environment. That's where you put all the pieces of puzzle together, make sure you see your application working, and then the next thing that, that you do is like, you know, you know, build >>Production, chip, build production, go and chip release it. Yeah, that's the nirvana. But then we're there. I mean, we're there now we're there. So we see the future. Because if you, if that's the case, then the developers are the business. They have to be coding more features, they have to react to customers. They might see new business opportunities from a revenue standpoint that could be creatively built, got low code, no code, headless systems. These things are happening where this I call the architectural list environment where it's like, you don't need architecture, it's already happening. >>Yeah. And, and on top of it, you know, if, if someone has an idea, they want to implement an idea real quick, right? So how do you do it? Right? And, and, and you don't have to struggle building an environment to implement your idea and testers in real time, right? So, so from an innovation perspective, you know, agility plays a key role. And, and that, that's where the Kubernetes platforms or platforms like Kubernetes >>Plays. You know, Lisa, when we talked to Andy Chasy, when he was the CEO of aws, either one on one or on the cube, he always said, and this is kind of happening, companies are gonna be builders where it's not just utility. You need that table stakes to enable that new business idea. And so he, this last keynote, he did this big thing like, you know, think like your developers are the next entrepreneurial revenue generators. And I think that, I think starting to see that, what do you think about that? You see that coming sooner than later? Or is that in, in sight or is that still ways away? >>I, I think it's already happening at a level, at a certain level now. Now the question comes back to, you know, taking it to the reality, right? Yeah. I mean, you can, you can do your proof of concept, proof of technologies, and then, and then prove it out. Like, Hey, I got a new idea. This idea is great. Yeah. And, and it's to the business advantage, right? But we really want to see it in production live where your customers are actually >>Using it and the board meetings, Hey, we got a new idea that came in, generating more revenue, where'd that come from? Agile developer. Again, this is real. Yeah, >>Yeah. >>Absolutely agree. Yeah. I think, think both of you gentlemen said a word in, in your, as you were talking, you used the word guardrails, right? I think, you know, we're talking about rigidity, but you know, the really important thing is, look, these are enterprises, right? They have certain expectations. Guardrails is key, right? So it's automation with the guardrails. Yeah. Guardrails are like children, you know, you know, shouldn't be hurt. You know, they're seen but not hurt. Developers don't care about guard rails. They just wanna go fast. They also bounce >>Around a little bit. Yeah. Off the guardrails. >>One thing we know that's not gonna slow down is, is the expectations, right? Of all the consumers of this, the Ds the business, the, the business top line, and of course the customers. So the ability to, to really, as your website says, let's see, make life easy for platform teams is not trivial. And clearly what you guys are talking about here is you're, you're really an enabler of those platform teams, it sounds like to me. Yep. So, great work, guys. Thank you so much for both coming on the program, talking about what you're doing together, how you're seeing the, the evolution of Kubernetes, why, and really what the focus should be on those platform games. We appreciate all your time and your insights. >>Thank you so much for having us. Thanks >>For our pleasure. For our guests and for John Furrier, I'm Lisa Martin. You're watching The Cube Live, Cobe Con, Cloud Native con from Detroit. We've out with our next guest in just a minute, so stick around.

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America 2020 Virtual brought to you by Red Hat The Cloud, Native Computing Foundation and Ecosystem Partners. Hello, everyone. And welcome back to the cubes Ongoing coverage of Cuba con North America. Joe Fernandez is here. He's with Stephanie, Cheras and Joe's, the V, P and GM for core cloud platforms. That red hat and Stephanie is this s VP and GM of the Red Hat Enterprise. Lennox bu. Two great friends of the Cube. Awesome seeing you guys. How you doing? >>It's great to be here, Dave. Yeah, thanks >>for the opportunity. >>Hey, so we all talked, you know, recently, uh, answerable fest Seems like a while ago, but But we talked about what's new? Red hat really coming at it from an automation perspective. But I wonder if we could take a view from open shift and what's new from the standpoint of you really focus on helping customers, you know, change their operations and operationalize. And Stephanie, Maybe you could start, and then, you know, Joe, you could bring in some added color. >>No, that's great. And I think you know one of the things we try and do it. Red hat clearly building off of open source. We have been focused on this open hybrid cloud strategy for, you know, really years. Now the beauty of it is that hybrid cloud and open hybrid cloud continues to evolve right with bringing in things like speed and stability and scale and now adding in other footprints, like manage services as well as edge and pulling that all together across the whole red hat portfolio from the platforms, right? Certainly with Lennox and roll into open shift in the platform with open shift and then adding automation, which certainly you need for scale. But it's ah, it's continues to evolve as the as the definition of open hybrid cloud evolves. >>Great. So thank you, Stephanie jokes. You guys got hard news here that you could maybe talk about 46? >>Yeah. Eso eso open shift is our enterprise kubernetes platform. With this announcement, we announced the release of open ship 4.6 Eso eso We're doing releases every quarter tracking the upstream kubernetes release cycle. So this brings communities 1.19, which is, um but itself brings a number of new innovations, some specific things to call out. We have this new automated installer for open shift on bare metal, and that's definitely a trend that we're seeing is more customers not only looking at containers but looking at running containers directly on bare metal environments. Open shift provides an abstraction, you know, which combines Cuban. And he's, uh, on top of Lennox with RL. I really across all environments, from bare metal to virtualization platforms to the various public clouds and out to the edge. But we're seeing a lot of interest in bare metal. This is basically increasing the really three automation to install seamlessly and manage upgrades in those environments. We're also seeing a number of other enhancements open shifts service mesh, which is our SDO based solution for managing, uh, the interactions between micro services being able to manage traffic against those services. Being able to do tracing. We have a new release of that on open shift Ford out six on then, um, some work specific to the public cloud that we started extending into the government clouds. So we already supported AWS and Azure. With this release, we added support for the A W s government cloud as well. Azaz Acela's Microsoft Azure government on dso again This is really important to like our public sector customers who are looking to move to the public cloud leveraging open shift as an abstraction but wanted thio support it on the specialized clouds that they need to use with azure gonna meet us Cup. >>So, joke, we stay there for a minute. So so bare metal talking performance there because, you know, you know what? You really want to run fast, right? So that's the attractiveness there. And then the point about SDO in the open, open shift service measure that makes things simpler. Maybe talk a little bit about sort of business impact and what customers should expect to get out of >>these two things. So So let me take them one at a time, right? So so running on bare metal certainly performances a consideration. You know, I think a lot of fixed today are still running containers, and Cuban is on top of some form of virtualization. Either a platform like this fear or open stack, or maybe VMS in the in one of the public clouds. But, you know containers don't depend on a virtualization layer. Containers only depend on Lennox and Lennox runs great on bare metal. So as we see customers moving more towards performance and Leighton see sensitive workloads, they want to get that Barry mental performance on running open shift on bare metal and their containerized applications on that, uh, platform certainly gives them that advantage. Others just want to reduce the cost right. They want to reduce their VM sprawl, the infrastructure and operational cost of managing avert layer beneath their careers clusters. And that's another benefit. So we see a lot of uptake in open shift on bare metal on the service match side. This is really about You know how we see applications evolving, right? Uh, customers are moving more towards these distributed architectures, taking, you know, formally monolithic or enter applications and splitting them out into ah, lots of different services. The challenge there becomes. Then how do you manage all those connections? Right, Because something that was a single stack is now comprised of tens or hundreds of services on DSO. You wanna be able to manage traffic to those services, so if the service goes down, you can redirect that those requests thio to an alternative or fail over service. Also tracing. If you're looking at performance issues, you need to know where in your architecture, er you're having those degradations and so forth. And, you know, those are some of the challenges that people can sort of overcome or get help with by using service mash, which is powered by SDO. >>And then I'm sorry, Stephanie ever get to in a minute. But which is 11 follow up on that Joe is so the rial differentiation between what you bring in what I can just if I'm in a mono cloud, for instance is you're gonna you're gonna bring this across clouds. I'm gonna You're gonna bring it on, Prem And we're gonna talk about the edge in in a minute. Is that right? From a differentiation standpoint, >>Yeah, that That's one of the key >>differentiations. You know, Read has been talking about the hybrid cloud for a long time. We've we've been articulating are open hybrid cloud strategy, Andi, >>even if that's >>not a strategy that you may be thinking about, it is ultimately where folks end up right, because all of our enterprise customers still have applications running in the data center. But they're also all starting to move applications out to the public cloud. As they expand their usage of public cloud, you start seeing them adopted multi cloud strategies because they don't want to put all their eggs in one basket. And then for certain classes of applications, they need to move those applications closer to the data. And and so you start to see EJ becoming part of that hybrid cloud picture on DSO. What we do is basically provide a consistency across all those environments, right? We want run great on Amazon, but also great on Azure on Google on bare metal in the data center during medal out at the edge on top of your favorite virtualization platform. And yeah, that that consistency to take a set of applications and run them the same way across all those environments. That is just one of the key benefits of going with red hat as your provider for open hybrid cloud solutions. >>All right, thank you. Stephanie would come back to you here, so I mean, we talk about rail a lot because your business unit that you manage, but we're starting to see red hats edge strategy unfolded. Kind of real is really the linchpin I wanna You could talk about how you're thinking about the edge and and particularly interested in how you're handling scale and why you feel like you're in a good position toe handle that massive scale on the requirements of the edge and versus hey, we need a new OS for the edge. >>Yeah, I think. And Joe did a great job of said and up it does come back to our view around this open hybrid cloud story has always been about consistency. It's about that language that you speak, no matter where you want to run your applications in between rela on on my side and Joe with open shift and and of course, you know we run the same Lennox underneath. So real core os is part of open shift that consistently see leads to a lot of flexibility, whether it's through a broad ecosystem or it's across footprints. And so now is we have been talking with customers about how they want to move their applications closer to data, you know, further out and away from their data center. So some of it is about distributing your data center, getting that compute closer to the data or closer to your customers. It drives, drives some different requirements right around. How you do updates, how you do over the air updates. And so we have been working in typical red hat fashion, right? We've been looking at what's being done in the upstream. So in the fedora upstream community, there is a lot of working that has been done in what's called the I. O. T Special Interest group. They have been really investigating what the requirements are for this use case and edge. So now we're really pleased in, um, in our most recent release of really aid relate 00.3. We have put in some key capabilities that we're seeing being driven by these edge use cases. So things like How do you do quick image generation? And that's important because, as you distribute, want that consistency created tailored image, be able to deploy that in a consistent way, allow that to address scale, meet security requirements that you may have also right updates become very important when you start to spread this out. So we put in things in order to allow remote device mirroring so that you can put code into production and then you can schedule it on those remote devices toe happen with the minimal disruption. Things like things like we all know now, right with all this virtual stuff, we often run into things like not ideal bandwidth and sometimes intermittent connectivity with all of those devices out there. So we put in, um, capabilities around, being able to use something called rpm Austria, Um, in order to be able to deliver efficient over the air updates. And then, of course, you got to do intelligent rollbacks for per chance that something goes wrong. How do you come back to a previous state? So it's all about being able to deploy at scale in a distributed way, be ready for that use case and have some predictability and consistency. And again, that's what we build our platforms for. It's all about predictability and consistency, and that gives you flexibility to add your innovation on top. >>I'm glad you mentioned intelligent rollbacks I learned a long time ago. You always ask the question. What happens when something goes wrong? You learn a lot from the answer to that, but You know, we talk a lot about cloud native. Sounds like you're adapting well to become edge native. >>Yeah. I mean, I mean, we're finding whether it's inthe e verticals, right in the very specific use cases or whether it's in sort of an enterprise edge use case. Having consistency brings a ton of flexibility. It was funny, one of our talking with a customer not too long ago. And they said, you know, agility is the new version of efficiency. So it's that having that sort of language be spoken everywhere from your core data center all the way out to the edge that allows you a lot of flexibility going forward. >>So what if you could talk? I mentioned just mentioned Cloud Native. I mean, I think people sometimes just underestimate the effort. It takes tow, make all this stuff run in all the different clouds the engineering efforts required. And I'm wondering what kind of engineering you do with if any with the cloud providers and and, of course, the balance of the ecosystem. But But maybe you could describe that a little bit. >>Yeah, so? So Red Hat works closely with all the major cloud providers you know, whether that's Amazon, Azure, Google or IBM Cloud. Obviously, Andi, we're you know, we're very keen on sort of making sure that we're providing the best environment to run enterprise applications across all those environments, whether you're running it directly just with Lennox on Ralph or whether you're running it in a containerized environment with Open Chef, which which includes route eso eso, our partnership includes work we do upstream, for example. You know, Red Hat help. Google launched the Cuban community, and I've been, you know, with Google. You know, we've been the top two contributors driving that product that project since inception, um, but then also extends into sort of our hosted services. So we run a jointly developed and jointly managed service called the Azure Red Hat Open Shift Service. Together with Microsoft were our joint customers can get access to open shift in an azure environment as a native azure service, meaning it's, you know, it's fully integrated, just like any other. As your service you can tied into as you're building and so forth. It's sold by by Azure Microsoft's sales reps. Um, but you know, we get the benefit of working together with our Microsoft counterparts and developing that service in managing that service and then in supporting our joint customers. We over the summer announced sort of a similar partnership with Amazon and we'll be launching are already doing pilots on the Amazon Red Hat Open ship service, which is which is, you know, the same concept now applied to the AWS cloud. So that will be coming out g a later this year, right? But again, whether it's working upstream or whether it's, you know, partnering on managed services. I know Stephanie team also do a lot of work with Microsoft, for example, on sequel server on Lenox dot net on Lenox. Whoever thought be running that applications on Linux. But that's, you know, a couple of years old now, a few years old, So eso again. It's been a great partnership, not just with Microsoft, but with all the cloud providers. >>So I think you just shared a little little He showed a little leg there, Joe, what's what's coming g A. Later this year. I want to circle back to >>that. Yeah, eso we way announced a preview earlier this year of of the Amazon Red Hat Open ships service. It's not generally available yet. We're you know, we're taking customers. We want toe, sort of be early access, get access to pilots and then that'll be generally available later this year. Although Red Hat does manage our own service Open ship dedicated that's available on AWS today. But that's a service that's, you know, solely, uh, operated by Red Hat. This new service will be jointly operated by Red Hat and Amazon together Idea. That would be sort of a service that we are delivering together as partners >>as a managed service and and okay, so that's in beta now. I presume if it's gonna be g a little, it's >>like, Yeah, that's yeah, >>that's probably running on bare metal. I would imagine that >>one is running >>on E. C. Two. That's running an A W C C T V exactly, and >>run again. You know, all of our all of >>our I mean, we you know, that open shift does offer bare metal cloud, and we do you know, we do have customers who can take the open shift software and deploy it there right now are managed. Offering is running on top of the C two and on top of Azure VM. But again, this is this is appealing to customers who, you know, like what we bring in terms of an enterprise kubernetes platform, but don't wanna, you know, operated themselves, right? So it's a fully managed service. You just come and build and deploy your APS, and then we manage all of the infrastructure and all the underlying platform for you >>that's going to explode. My prediction. Um, let's take an example of heart example of security. And I'm interested in how you guys ensure a consistent, you know, security experience across all these locations on Prem Cloud. Multiple clouds, the edge. Maybe you could talk about that. And Stephanie, I'm sure you have a perspective on this is Well, from the standpoint of of Ralph. So who wants to start? >>Yeah, Maybe I could start from the bottom and then I'll pass it over to Joe to talk a bit. I think one of these aspects about security it's clearly top of mind of all customers. Um, it does start with the very bottom and base selection in your OS. We continue to drive SC Lennox capabilities into rural to provide that foundational layer. And then as we run real core OS and open shift, we bring over that s C Lennox capability as well. Um, but, you know, there's a whole lot of ways to tackle this we've done. We've done a lot around our policies around, um see ve updates, etcetera around rail to make sure that we are continuing to provide on DCA mitt too. Mitigating all critical and importance, providing better transparency toe how we assess those CVS. So security is certainly top of mind for us. And then as we move forward, right there's also and joke and talk about the security work we do is also capabilities to do that in container ization. But you know, we we work. We work all the way from the base to doing things like these images in these easy to build images, which are tailored so you can make them smaller, less surface area for security. Security is one of those things. That's a lifestyle, right? You gotta look at it from all the way the base in the operating system, with things like sc Lennox toe how you build your images, which now we've added new capabilities. There And then, of course, in containers. There's, um there's a whole focus in the open shift area around container container security, >>Joe. Anything you want to add to that? >>Yeah, sure. I >>mean, I think, you know, obviously, Lennox is the foundation for, you know, for all public clouds. It's it's driving enterprise applications in the data center, part of keeping those applications. Security is keeping them up to date And, you know, through, you know, through real, we provide, you know, securing up to date foundation as a Stephanie mentioned as you move into open shift, you're also been able to take advantage of, uh, Thio to take advantage of essentially mutability. Right? So now the application that you're deploying isn't immutable unit that you build once as a container image, and then you deploy that out all your various environments. When you have to do an update, you don't go and update all those environments. You build a new image that includes those updates, and then you deploy those images out rolling fashion and, as you mentioned that you could go back if there's issues. So the idea, the notion of immutable application deployments has a lot to do with security, and it's enabled by containers. And then, obviously you have cured Panetti's and, you know, and all the rest of our capabilities as part of open Shift managing that for you. We've extended that concept to the entire platform. So Stephanie mentioned, real core West Open shift has always run on real. What we have done in open shift for is we've taken an immutable version of Ralph. So it's the same red hat enterprise Lennox that we've had for years. But now, in this latest version relate, we have a new way to package and deploy it as a relic or OS image, and then that becomes part of the platform. So when customers want toe in addition to keeping their applications up to date, they need to keep their platform up to dates. Need to keep, you know, up with the latest kubernetes patches up with the latest Lennox packages. What we're doing is delivering that as one platform, so when you get updates for open shift, they could include updates for kubernetes. They could include updates for Lennox itself as well as all the integrated services and again, all of this is just you know this is how you keep your applications secure. Is making sure your you know, taking care of that hygiene of, you know, managing your vulnerabilities, keeping everything patched in up to date and ultimately ensuring security for your application and users. >>I know I'm going a little bit over, but I have I have one question that I wanna ask you guys and a broad question about maybe a trends you see in the business. I mean, you look at what we talk a lot about cloud native, and you look at kubernetes and the interest in kubernetes off the charts. It's an area that has a lot of spending momentum. People are putting resource is behind it. But you know, really, to build these sort of modern applications, it's considered state of the art on. Do you see a lot of people trying to really bring that modern approach toe any cloud we've been talking about? EJ. You wanna bring it also on Prem And people generally associate this notion of cloud native with this kind of elite developers, right? But you're bringing it to the masses and there's 20 million plus software developers out there, and most you know, with all due respect that you know they may not be the the the elites of the elite. So how are you seeing this evolve in terms of re Skilling people to be able, handle and take advantage of all this? You know, cool new stuff that's coming out. >>Yeah, I can start, you know, open shift. Our focus from the beginning has been bringing kubernetes to the enterprise. So we think of open shift as the dominant enterprise kubernetes platform enterprises come in all shapes and sizes and and skill sets. As you mentioned, they have unique requirements in terms of how they need toe run stuff in their data center and then also bring that to production, whether it's in the data center across the public clouds eso So part of it is, you know, making sure that the technology meets the requirements and then part of it is working. The people process and and culture thio make them help them understand what it means to sort of take advantage of container ization and cloud native platforms and communities. Of course, this is nothing new to red hat, right? This is what we did 20 years ago when we first brought Lennox to the Enterprise with well, right on. In essence, Carozza is basically distributed. Lennox right Kubernetes builds on Lennox and brings it out to your cluster to your distributed systems on across the hybrid cloud. So So nothing new for Red Hat. But a lot of the same challenges apply to this new cloud native world. >>Awesome. Stephanie, we'll give you the last word, >>all right? And I think just a touch on what Joe talked about it. And Joe and I worked really closely on this, right? The ability to run containers right is someone launches down this because it is magical. What could be done with deploying applications? Using a container technology, we built the capabilities and the tools directly into rural in order to be able to build and deploy, leveraging things like pod man directly into rural. And that's exactly so, folks. Everyone who has a real subscription today can start on their container journey, start to build and deploy that, and then we work to help those skills then be transferrable as you movinto open shift in kubernetes and orchestration. So, you know, we work very closely to make sure that the skills building can be done directly on rail and then transfer into open shift. Because, as Joe said, at the end of the day, it's just a different way to deploy. Lennox, >>You guys are doing some good work. Keep it up. And thanks so much for coming back in. The Cube is great to talk to you today. >>Good to see you, Dave. >>Yes, Thank you. >>All right. Thank you for watching everybody. The cubes coverage of Cuba con en a continues right after this.

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America 2020 Virtual brought to you by Red Hat The Cloud Native Computing Foundation and Ecosystem >>Partners Everyone welcome back to the cubes. Coverage of Coop con Cloud, native con North America 2020. Normally the Cuba's in person. But like the EU event, this is gonna be a remote virtual event. This is the Cube virtual. We are the Cube Virtual. This is a keynote and show review with our analysts and hosts Lisa Martin, GOP Scar and myself. Guys, welcome to the program. Lisa, Great to see you. You great to see you remotely. Thanks for coming on. >>Always great to be part of the Cuban acute virtual keeping us connected. >>So Coop Con Cloud Native cons November and I remember in 2016 the first Coop Con. That's when Hillary Clinton got defeated by Trump. And now this year the election's passed this time and, uh, Biden the winner. So, you know, election more good vibes this year in the community because everyone was kind of sad last time. So if you remember the first Cube con, it was in Seattle during that time, so that was important to kinda reminisce on. That other thing I want to bring up to you guys is the somber news of the passing of Dan Con who was the executive director of C N C F. He passed a few weeks ago on his home. It was illness and great legend. So we're gonna call that out, and there are thoughts and prayers. Go with the families. Condolences to his wife and kids. So what? I'm say, Dan. Godspeed. Funny dance story, Lisa. Yo, piece that I always always pronounce his name wrong on the queue was like, John, it's con, not Cohen. Okay. All right, Dan, Good to see you. Sorry, but a great guy friend to everyone And super great human being. So rest in peace. Okay. Que con, I >>think the big thing. >>This you wanna get your thoughts, you have to start with you, C and C F. What are they up to? Obviously remote. It's been a terrible year with the pandemic and all the disruptions on DCI change your thoughts on where they are now, this year. >>So you know, it's funny, even though it's remote. Even though reaching people, it's become harder. Uh, you know, we all have to deal with this from our you know, our living room, our office at home. But still, the C in C F is doing what it's been doing for a little while now. So instead of focusing on the technology part of RT world, there are focusing on you know, the community side of it. So they're fighting for inclusivity. They're fighting for diversity, for resilience in terms off their community. And they are really working on making the open source community more accessible, both for end user companies. A swell as offer developers thio enter the space, have their contribution and, you know, make sure that everyone can reap the full benefits off these open source products. >>You know, we talked to Priyanka Sharma and Stephen Augustus, and this was a big theme. There's there's been there's been a lot of engagement online, obviously, even though they have a remote platform, some people are thrilled with it. Some aren't. No one's ever happy these days. It's on the Web. It's always difficult, but the community been activated and a lot more diversity. I covered the big story around. You know, Master slave. The terminology now is gonna go main, you know, terminology and how that's gonna be safer. Also for diversity stem women in tech, This >>has been >>a big theme. I'd love to get your thoughts on that, because I think that's been a very positive thing. Uh, Lisa, you and I have been talking about this for years on the Cube around this diversity peace. What's your thoughts as well, like to get both your reactions on where this directions going. >>Yeah. You know, I think there's a number of things that have been catalyzed this year by the challenges that we've been through and the diversity pushed into the spotlight again. The spotlight is different, and it's really causing change for good. I think it's opening people's minds and perspective, as is, I think, this entire time, you know, it's for events like Yukon and all the other events that were normally getting a lot of airline miles for John and you were not getting. We're sitting at home with our in home studios, but at the same time, the engagement is increasing in every event, I imagine that the great Q. Khan and cognitive community that Dan Cohen has built is on Lee getting bigger and stronger, even though folks are physically separated. That's been just been my observation and something I felt from everything show I've covered every interview I've done that diversity is being raised now to a visibility level that we haven't seen in terms of a catalyzing action. >>You your reaction, Thio. >>No, I completely agree. And I want to add to that where you know, just like Lisa said. You know, we used to fly to these events. We were privileged and lucky to to be there to have the opportunity. But because everything is now digital and virtual, it opens the community up to so many other people who, for whatever reason, weren't able to join in person but are able to join virtually indigenously. So I think you know, even though there's a lot of downsides Thio to this pandemic, this is one of the, you know, the small nuggets of off seeing the sea NCF community opening up to a broader audience. >>Yeah, and that's a great point. You know, we aren't getting the airline miles we're getting Certainly the zoom and the cube mileage remote Lisa, because what's interesting you're saying is is that you know, we're getting more action with him coming in, doing some or hosting yourself, um, Eliana Gesu as well, Others. But we can get people more because remember, the people aren't we're not trying, but so aren't other people that were coming the big names, but also the fresh voices, the new names, names? We don't know yet. I think that's what we're seeing with the remote interviews is that it's one click away from being on the Cube now. So cute. Virtual is 24 73 65 we're gonna continue to do that. I think this is gonna change the makeup of the engagement in the conversation because you're gonna have mawr participation that's going to be highly accelerated. But also, these new voices are gonna bring a positive change. It might upset the hierarchy a little bit in the working groups at the top you, But you know they're open. I mean, I talked with Stephen Augustus. He's totally cool with this Chris, and I check is the same way he's like, Hey, bring on more people. This is the >>This is >>the vibe of the of the Lennox foundations always been. >>It's always been that way. And, you know, going back Teoh to the early open source events in Europe that I went to you. I started doing that as a teenager 15 years ago, and the vibe, you know, hasn't necessarily changed. The makeup of the audience certainly has changed right from it, being dominated by white males. It's totally opened up. And, you know, if we see that happening with the C N C F now as well, I think that's for you know, for the better. I think, um, our community, the i t community in the open source community need that resilience. Need all of those different perspectives from all of you know, different kinds of people from different walks of life with different histories. And I think that only makes the community stronger and more viable in the long run. I >>agree it's that >>open source needs. >>Sorry, it's not thought diversity that I think we're seeing even more now again. Just my perspective is just that the light that this challenging time is shining on, exposing things that are really opportunities and it's I think it's imperative to look at it in that way. But that thought diversity just opens up so many more opportunities that folks that are maybe a little bit more tunnel visioned aren't thinking of. But for businesses, thio and people Thio thrive and move forward and learn from this we need to be able Thio, take into consideration other concepts, other perspectives as we learn and grow. >>Yeah, that's a good point. You know, It was giving a a shout out to Dan Conn. And when I heard the news, I put a clip. One of my favorite clips over the interviews was really me kind of congratulating him on the success of C and C. I think it was, like two years ago or maybe last year. I forget, Um, but I >>was a >>critic of it ever initially, and I was publicly on the record on the Cube. Lisa, you remember, uh, with Stew, who's now having a great new career? Red hat Still and I were arguing, and I was saying, Stew, I think this is gonna fail, because if c. N. C F doesn't balance the end user peace with the logos that we're coming because remember, you about four years ago. It was like a NASCAR logo. Farmers like you know, it's like, you know, everything was like sponsored by Google this and then Amazon came in. You look at the sponsor list. It was like It's the who's who and cloud and now cloud native. It was the industry the entire industry was like, stacked up against reinvent. This is before Amazon made their move. I mean, uh, as your maid, they're moving for Google. Cloud kind of got their footing. So is essentially coop con against a W s. And I said, That's gonna fail, and I had to eat my words, and I did. It was rightfully so, But the balance, the balance between end user projects and vendor was very successful. And that's still plays out today. Lisa. This is important now because you said pandemic de ecosystem still needs to thrive, but there's no face to face anymore. >>What's the >>challenge? What's the opportunity there? I wanna put you on the spot. >>Sure. No, I think I think it's both challenging and opportunistic. I tend to look at it more from an opportunistic view. I think that it forced a lot of us, Even people like myself who worked from home a lot before, when I wasn't traveling for my marketing company or the Cube. You can really have very personal interactions. The people on Zoom and I found that it's connecting people in a deeper way than you even would get in the office. That's something that I actually really appreciate, how it has been an opportunity to really kind of expand relationships or toe open new doors that wouldn't be there if we were able to be studying together physically in person. And it's obviously changing. You know, all the vendors that we work with. It's very different to engage an audience when you are on Lee on camera, and it's something that, as we know, is we work with folks who haven't done it before. That's one of the things that I think a lot of the C suite I talked to Mrs is that opportunity Thio. You know, be on a stage and and be able to show your body language and your energy with your customers and your partners and your employees. But I actually do think that there is what we're doing through Zoom and and all these virtual platforms like the Cube virtual is well, we're opening up doors for a more intimate way that I think the conversations are more authentic. You know, people are have, like, three year old Discover occurs and they're running in the room when they're screaming behind that. That's how things are today. We're learning toe work with that, but we're also seeing people in a more human >>way. Containers Mitch, mainstream and shifting, left the role of security this year. What's your >>take? So I mean, if we're talking about security and nothing else, I think we're at a point where you know, the C N C. F has become mainstream. Its most popular products have become mainstream. Um, because if we're talking about security, there's, you know, not a lot left. And I say that with, you know, a little bit of sarcasm. I don't mean to offend anyone, but if I did, uh, I do apologize, but, you know, security. Even though it is super important again, it means that we have, you know, moved on from talking about kubernetes and and container Management, or we've moved on from storage. Um, it means that the technology part of the C N. C. F. Like the hard work has been done for 80%. We're now into the 20% where we're kind of, you know, dotting the I's and and making sure that we cover all of the bases. And so one of the news sandbox sandbox projects that has been accepted, I think, today even eyes certain Manager Thio to manage certificates Uh, you know, at scale, um, in an automated fashion. And I think that's, you know, 11 prime example of how security is becoming the theme and kind of the conversation at Yukon this year where, you know, we're again seeing that maturity come into play with even with sandbox projects now being able to help customers help end users with, you know, certificates which is, you know, in in the the macro picture a very specific, a very niche thing to be able to solve with open source software. But for every company, this is one of those vital, you know, kind of boilerplate security measures so that the, um the customer and all of their infrastructure remains safe. >>I think you what You're kind of really articulate, and there is the evolution of CNC off much to John Surprises. You said you thought in the very beginning that this wasn't gonna take off. It has. Clearly, Dan Cohen's left a great legacy there. But we're seeing the evolution of that. I do know John. Wanna ask because you did a lot of the interviews here. We've been talking for, what, nine months now on the Cube Virtual about the acceleration of transformation, of every business to go from that. Okay, how do we do this work in this in this weird environment? Keep the lights on. How do we actually be successful and actually become a thriving business? As things go forward, what are some of the things that you heard from the guests regarding? Kobe has an accelerator. >>Well, I think I think a couple of things. Good. Good question. I think it ranges. Right. So the new They had some news that they're trying to announce. Obviously, new survey certifications, K a security certification, new new tech radar support, diversity stats. You know, the normal stuff they do in the event, they gotta get the word out. So that was one thing I heard, but on the overall macro trend. You know, we saw the covert impact, and no >>one's >>afraid of it there. I mean, I think, you know, part of the legacy of these tech communities is they've been online. They're they're used to being online. So it's not a new thing. So I don't think that the work environment has been that much of a disruption to the people in the in the core community. Linux Foundation, for instance, had a great shot with Chris and a sticker on this. He's the CTO. He's been the CEO, brought a senior roles. Um, in fact, they're they're creating a template around C N C f. And then they're announced The Finn Finn Ops Foundation. Uh, Jr store meant, um, is an executive director. That's part of the new foundation. It's a practitioner community. So I think, um, teasing out the conversation is you're gonna see a template model of the C N. C f. Where you're going to see how groups work together. I think what cove? It has definitely shown in some of the things that you guys were saying around how people are gonna be more engaged, more diversity, more access. I >>think you're >>gonna start to see new social constructs emerge around distinct user groups. And I think this Finn ops Foundation is a tell sign around how groups of people going to start together, whether they're cube host coming together on Cube fans and cube alumni. I mean, let me think about the alumni that have been on the Cube. Lisa, you know Tim Hopkins, Sarah Novotny. Chelsie Hightower. Um, Dan Burns, Craig MK Lucky. I mean, we've had everybody on that's now Captain of the industry. So, um, way had capital one we've had, uh, you know, lift on. I mean, it's becoming a really tight knit. Everyone knows each other, and I think now they realize that they have a lot of, uh, power to infect change. And so when you're trying to affect change, um, that's a good thing, and people are pumped about. So I think the big focus was, um, CNC have a successful again. It's there's there's a somber note around Dan cons passing, but I think he had already moved on to a new position. So he was already passed the baton to management, But he did leave a mark, but I think there's Priyanka Sharma. She's doing a great job. People are upbeat and I think the theme is kubernetes. It happened. It's went next level, then it's going next level again and I think that's kind of what people really aren't saying is kind of the public secret, which is okay, this thing's going mainstream. Now you're gonna start to see it in, in, In commercial deployments. You're gonna start to see it scale into organizations. And that's not the cool kids or the Emerging Dev ops crowd. That's I t. So you know you know it's gonna happen is like, Hey, you know, I'm a nice guy, our developer. What is this? It has toe work. Well, that's the big I think I think people weren't talking about That's the most important story. >>I think another element to that John is the cultural shift. You know, we were talking when we talk about Dev ops who was think about speed and I talked to some folks who said, You know, it's it has to be the I T. Cultures on the business cultures coming together in a meaningful way to collaborate in a very new way. Thankfully, we have the technology to enable us to collaborate. But I think that's been another underlying thing that I've heard a lot through recent times. Is that that facilitator of of cultural change, which is always hard to dio? And there's a bit of a catalyst here for organizations to not just keep the lights on. But to be successful, going forward and and and find new ways of delighting their customers, >>we'll get the final word. I just want to say my big take away to the show is and we'll go down the line. I'll start Lisa in Europe, you could go is the usage of cloud and multi cloud is here. Everyone sees that. I think there's a financial aspect going on with security. You're gonna be tied in. I think you see new sets of services coming built on the foundation of the C N C F. But cloud and multi cloud is here. Multi cloud meeting edges. Well, that is definitely on everyone's radar. That was a big theme throughout the interview, so we'll see more of that. Lisa, your takeaways. >>Yeah, I would agree with that. And I think one of the biggest things that I hear consistently is the opportunities that have been uncovered, the the collaboration becoming tighter and folks having the opportunity to engage more with events like Coop Con and C and C F. Because of this virtual shift, I think there's only ah lot of positive things that we're going to stay to come. >>Yep. Yeah, my point of view is I mean, open source is validated completely right? It's a viable model to build around software. On the one hand, on the other hand, the C and C s role in making that open source community broadly accessible and inclusive is, I think, the biggest win Thio look back at at the last year. >>Well, I'm super excited for moving on to the next event. It's been great pleasure. Lisa. You you guys are great co host Virtual Cube. Thanks for participating. And we'll see you next time. Thank you. Okay, that's the cubes. Coverage of Coop con 2020 cloud Native con Virtual This the cube Virtual. We are the cube. Virtual. Thanks for watching

>> Live from Seattle, Washington, it's theCUBE, covering KubeCon and Cloud Native Con North America 2018 brought to you by Red Hat, the Cloud Native Computing Foundation and it's ecosystem partners. >> Hey welcome back everyone, we are live here in Seattle. It's theCUBE's coverage of KubeCon, Cloud Native Con, a part of CNCF, Cloud Native Computing Foundation, the rise of Kubernetes, this is what the show is all about. Three days of wall to wall coverage. We've been there from the beginning covering this KubeCon effort from the beginning. I'm John Furrier with Stu Miniman, we're here to analyze and break down the event with our guest analyst for the segment, Steve Herrod, CUBE alumni, he was there the first day we ever did theCUBE in 2010. He's been a good friend of theCUBE. Now he's a venture capitalist, managing director at General Catalyst, a premiere VC in the industry. Steve, great to see you. >> Good to be here. >> Thanks for coming on. >> Feels like the early days of some of the other conferences, too, doesn't it? >> It feels like AWS, you know seven/eight years ago where it tips over, there's a tipping point. We see that doubling, so you know, it's kind of that tipping point where there's more demand for theCUBE and we can fill it so there's great content but it's a bigger picture, right? And I want to break through that, I want to get your thoughts and let's have a shared conversation around what's really going on here. You're talking about a disruption in the industry of cloud computing. You got Amazon, just a freight train just taking all the beach, the waves coming in and this is an opportunity, this is my opinion, for the industry to kind of say, hey, it's a multi cloud world so you're not going to take all of it. You got Google, you got Microsoft, you got start ups. This is a way to create an opensource way to fill the gap. Your thoughts? You agree? >> I totally agree and I think what's interesting, this conference does not have a corporate, at least an explicit corporate sponsor. It has four or five that are all trying to have their play in it. Microsoft's not one of them, which is sort of interesting. But it was, I think, a very bold thing this year to have this big of a venue and invite this many people and then hope that you're going to get the sponsorships and all the other stuff that follows. >> In Seattle. >> In Seattle. Yeah, our weather is a little bit-- >> It's very meta. (laughing) >> Interesting. But, just to your point, I do think this is really interesting because it is more open than a lot of these conferences where people are coming together. Both open source but also so much focus on how do you do functions in a way that works across places, how do you service meshes. Like everything is, it's both good and bad because there's so many choices that people are being seen right now. >> You were the CTO of VMware, Stu you worked in the CTO office at EMC back in the day, you're seeing a systems kind of vibe going on in cloud and you got application renaissance, kind of almost like the app server days, think WebSphere or whatever, that movement in the 90's and 2000's, that kind of grew quickly, all kind of being modernized. So you have cloud scale. >> Mm-hmm. >> AI has been around for a long time but because of the cloud, there's a renaissance. Video's been around for a long time but because of the cloud, things like theCUBE is happening. So the cloud is enabling a rebirth of a lot of things. >> Mm-hmm. >> And enabling a lot of new things, how do you guys view that systems view, application renaissance? Jassy talks about a reinvent as a new kind of persona developing. >> Mm-hmm. >> As a buyer and IT investments are changing, you're making start up investments, it's crazy. >> Yep. >> What do you think? >> Yeah, so first of all John, I like what you're saying about that systems view because too often we would kind of focus on a specific tool. So virtualization was great, but, you know, big thing, I took a bunch of servers and made it smaller servers but I took the same old application and I shoved it in there, and I left it running for another five or 10 years when I probably should have modernized it. Today, you know we just had Cheryl on talking about the ecosystem and customers and what I want to focus on is how the users get value. What are building on top of this? >> Right. >> Not the next cool thing to build, but how do I run my business? How do I do cool things with genomics? How do I improve healthcare? And in many ways we're seeing some of these top down things. I mean what's gotten me so excited about things like serverless and been really poking and teasing at how that fits in with this ecosystem is it's not just about a way to kind of turn the crank on making things a little bit more efficient or, you know, I can manage more machines with fewer people, but you know it moves up things and for someone like myself, a networking guy with an infrastructure background? >> Right. >> It's a little out of my comfort zone and that's okay. You know we talked to Lou Tucker, Lou's really excited about where AI's going and what's there, so I think we're in a real renaissance here and it's a big inflection point. >> Well I think to your point, what's interesting, whenever I do a teacher course to a college or when I'm talking to start ups or even in the old days it's really easy to forget that infrastructure is not a thing in it's own right. It's solely there to enable applications and to enable other things and so whenever you get really deep in the weeds on this is a new security model for this type of container or this, it's important and you're thinking about the best way to do it but, really you're right, you have to abstract it out to can I ship value faster? Can I save customers money? Can I do something safer? You really have to think about it in that context. And there's so much activity here you have to really make sure you're thinking about where it all fits together. >> And you know, the computer science conversations changes, too. The nature of what is computer science is evolving. I want to get to that in the next kind of discussion point but I want to just, Steve, ask you, you were on the VMware side when VMware kind of entered in with virtualization. It was a desktop, it was an app, it was like you loaded it on a machine and then that ended up transforming a massive industry and so a lot of people compare what VMware did in it's growth and it's impact but saying the cloud has got certainly more orders of magnitude, you mentioned security. >> Mm-hmm. >> Where's the VMware moment in this cloud transformation impact? Your thoughts there, just because you've been on both sides, one as a driver, CTO at VMware and now as an investor. Where do you see cloud-- >> Yeah, I kind of thought of it as two different angles. One is, appealing to developers and then that taking you all the way through operations which is, I mean that is, dev ops is sort of looking at that. VMware's first product was a workstation product that made developers have a bunch of environments right in front of them and we always had a vision for getting into the operations center but we knew we had to kind of come up through that path and I think likewise, a lot of this tooling that we see here is developer first and it's them saying, "I like this tool "and I can make my job be more enjoyable this way." But what you're really seeing, especially at this one is, how do you start in the developer tools and then not be detested by developers but then actually be paid for it by the operations side. So if you look at the type of vendors that are here? You start having venture capitalists here. You have a few people wearing suits here. It is about making this more enterprisey, more production ready and that's kind of the natural progression of any major impact like this. >> And Heptio, certainly Stu was reporting earlier, the number has been better than the filing of VMware. You know, a half a billion dollar acquisition for talent and a position in the marketplace. There's liquidity so there's investment opportunities. We talked to Jerry Chan about this at AWS, I want to get your thoughts, how is the investment thesis going on because what are you investing in? The notion of a stack, has kind of transformed into Lego blocks and services. >> Yep. >> So the notion of a stack is kind of changing although I've heard people say the, "Kubernetes stack." I'm like, well, what does that mean? (laughing) >> Which one? Yeah. >> So there's a lot of kind of stack derivatives. >> Mm-hmm. >> But how do you invest in this? What are you looking for? Where is the value? >> Yep. >> Where are sniffing out the deals? Where's the white spaces? And where should entrepreneurs go? >> Yeah, and I have several companies presenting here so I've certainly done some investments around this space, but I focus on a few things very specifically. I've been around this a little while. I really like to think about not tools that go to the new, hot new companies. I really try to think about what is more mainstream company going to adopt? And that usually means a few things. It has to have enterprise capabilities. It has to fit into the rest of the things. But I look at like how are you going to digest this with your other tools and the other processes that you have in place? If it's a security solution, I look at, I don't want really something that only protects the brave new world, I want it to fit in somehow with security policies and other things that are happening. >> So mainstream adoption? IT kind of impact? >> Yeah, just like a tool that actually works across environments and lets you go from here to there. You all have talked to Illumio several times? >> Yeah. >> They're trying to do micro segmentation for physical machines all the way through containers. The other thing I'm keeping a close eye on is, this is chaos, in terms of the number of start ups doing very specific point solutions and you have to really think about how does that grow into a big enough chunk of a budget or a big enough problem. So every single time I make an investment, I ask how does this do something 10 times better than something else and is that important to the company? And that's really hard to answer sometimes. >> Steve, and what's your take on the kind of opensource, open core, business model today? To be honest, I go around, I talked to some of the founders there, and everybody wants to contribute to opensource but maybe I don't want to build a business around it, because actually monetizing that is really tough. Is it just, I look to get acquired by one of the big players here? Or can I actually build a business with opensource at it's core? >> That's literally the billion dollar question. >> Yeah. >> But I do think, like on the positive side, the number of exits or big things recently with Magento, with Cloudera doing great, with, obviously, Red Hat, but we've seen, and Neilsoft, like a lot of big acquisitions and some good IPOs. But on the flip side, you definitely have to think about it differently now. There's a growing license that is very careful about allowing clouds to host your opensource project without contributing back. Hopefully that'll allow this hosted model to play out. I personally, I certainly look to opensource. You can see what's going on from traction but when you see it as a great lead generation engine which it often is for folks, I think that's a really healthy way to avoid spending a bunch of marketing money. >> Yeah, it's been fun. A lot of different shows we go to. Love your analysis, thanks for coming on, appreciate it. Just in general, as not a VC, but as a tech person and in the industry, I want to ask you and Stu what wave are we on? Obviously Kubernetes is now kind of front and center but we've still got cloud native. Is it the cloud? You got IoT and Amazon ARM, but we saw a lot of conversations around Edge. They had some interesting announcements around satellite telemetry coming in to regions. So you got Google, you got Microsoft, you got the big players. Is it the rich get richer? Is there going to be a new second tier? Cloud service provider? Where is this going? How is it going to reshape the industry? I mean, just big picture, what's your thoughts? >> Well, this is literally what I get paid to do is figure out where things are headed. I'd say, just at a top level, this is a super fun time to be in this lower level of the stack. You mentioned already AI gets, sort of AI washing goes on a lot right now but the very core of it is literally changing every application in interesting ways. And for me, I was a former hardware designer. The fact that you can now build and have really cool new hardware that's accelerating this stuff is really exciting. You saw Amazon's announcements, not only an ARM based server but Inferentia chips. Google has been doing this with TPUs-- >> Hundred gig networking in there, like, you know, high speed-- >> It is impressive. >> Cluster configurations, it's amazing stuff. >> So I love the fact that we can actually have very big innovation at each stage of the stack and it's because the combination of every company becoming an app, digital company coupled with the power of AI to transform things means you need dev ops to faster, you need these platforms that let you do more self service. And then I sprinkle on top of that is just the ridiculous demand for high quality engineers and if you don't give them an environment where they feel productive, they're just not going to stay at your company. And so all the mix comes together. I don't think they're going to be, there'll be some giant companies that already are, but I think the ability to create a new company that becomes large quickly or becomes small quickly if you screw up is bigger than ever. >> Yeah, I think it's total acceleration. >> Everything's faster. >> Values accelerated but it's also failure, too, right? >> Exactly, everything is accelerated. >> You have an option to abandon in you NPV calculations and IRRS (laughing) in your portfolio. >> Exactly, no it's-- >> The word pivot comes to mind. >> Everything is faster, that's the right way to think about it. >> Stu what's your take on this? >> Yeah, so we're at an interesting point in the industry. It's a bit of a paradox. On the one hand, the challenge of our time, we've been talking on theCUBE since the early days, John, is it's about distributed architectures and we're decomposing all of the pieces. Even Kubernetes itself, we're going to talk about how it's decomposing. On the other hand, everything is consolidating. >> That's right. >> I've seen more vertical stack integration from the chip and hardware level all the way through. You see Apple, Microsoft, Google-- >> That's right. >> And Amazon, all have chips companies and are going really interesting stuff there but it is such a complex individual. >> It is. >> That no one company can do it all, so there is opportunity for people to build on top of that. We have new marketplaces, we have new ways of doing it so it's, yes, there's going to be some really big winners and we have seen changes but there are still opportunities and yeah, John, keeps us busy always. >> Well here's my take on it, I want to get you guys' reaction to my view on this. So obviously we're in the media business, we're disrupting media with theCUBE so we look at the market and it's kind of matched the music industry. The power curve, the power law is very flat and straight and then a very long tail, with the head of the power law is the big players. But then when media came out, it kind of created a fatter tail and a bigger torso. I think that I see in the cloud, I see the rich getting richer. Amazon, Google, Microsoft, Alibaba, and maybe a couple players underneath there, IBM, Oracle, those big guys. And then it's going to be a second tier of cloud service providers. Someone who's going to package all these awesome sets of features in the long tail so you're going to start to see a growth because the big guys cannot be winning all the mid range business. I think, you're right, I think there's going to be a lot of solutions that are just exceptional. >> Mm-hmm. >> And I think the scale of the cloud is going to create an opportunity for new kinds of service providers. Someone who says, hey, you know what? I'm going to package this differently. I'm going to assemble-- >> I think so. >> A cloud solution, on either one of all of the clouds. Why wouldn't I use the accelerated Amazon, or the power of Google? >> I think that's well thought and I do think, we've talked about this for a while too, but I do believe there's going to be specialization by industry where you have certain algorithms and data that's unique to it, by geography. There's still going to be sovereignty issues. Even by just what type of things am I trying to build. So I do think simultaneously there's commonality on the platform but that allows you to do specialization and to really serve a specific industry quite well. >> And machine learning is a great specialty thing. The metadata to power machine learning. >> So Steve, do you have final questions you want to ask us before we run out of time? >> Well I would just say, you see a lot of these conferences. I actually like to show up at these and say, what in point time does this look like the AWS reinvent. For me, what point in time does this look like maybe the VMware event in my case, but I don't know, it just feels to me like we've jumped over, we're sort of at that point where this is going to keep going and growing. >> Yeah, how do we make sure we've hit the inflection point but not jumped the charts? >> Yeah, I mean, do you think we are here? And how does this feel versus some of the other events that you spend time on? >> Yeah, I mean, John you want me to? >> I mean, you know. >> So my take, first of all, is there's a little worry and there's some concern of us that have been through this before, is like, wait, did we just create another OpenStack? >> Yeah. >> And my resounding answer so far, is no. While there might be 35 main projects here each one of those was started for a reason. They stand on their alone, they have, you know we've got Matt Klein on from Lyft, as our next guest here. >> Yeah. >> You know, Envoy, if Kubernetes didn't exist, Envoy would probably still exist. So there's a lot of these pieces that are good but it is complicated. >> It is very complicated. >> And there's all these pieces but that's a real opportunity for a lot of companies. The SIs, the big platforms, to be able to help put this together. >> Yeah. >> And the customers are thrilled with what is going on. >> That's well stated, yeah. >> There's interesting things there. Right, this ecosystem, the only ecosystem I've seen probably grow faster is the Amazon one so it is doing well and we've been looking for years as to like a nice, vendor independent ecosystem. >> Right. >> To grow because, you know, there's some of the ones in the storage industry and things like that. >> Yeah. >> All died. >> That's right. >> So there are vendor shows and this, you know the Lennox Foundation's done a nice job. >> Right, I agree. >> With it and it's been-- >> That's the unique part here for me. >> We bet early on it, so. >> Well we bet early on it, it was a good bet, but here's the challenge that they have; they have lightning in a bottle and it's definitely arrived so there's a little bit of jump to shark moment. You got some things happening that's kind of glam oriented but absolutely it's arrived. I think the challenge that they have is opensource community is a core constituency of this event, and the Lennox Foundation is structured to be kind of a very tight top, thin at the top period of management and the scale of this event and this movement is too big for them, I think, to handle. I think they either have to have sub brand or start segmenting out because if they lose the opensource community, the they're going to lose the vibe of the event and that's the core of what it is. >> Right. >> The downstream benefits, kind of a an opensource parlance, is the IT impact and the developer impact. And inherent in that is business benefits so you're going to start to see more suits coming in and you're going to start to have a melting pot and that is a risky proposition if they don't get out front on that. So yes, it's arrived, but there's so much time they're going to be doing it just to the projects. >> Right. >> Just to the innovation. >> You're going to have to wear these next time that you see them. >> There's a money making aspect of it, yes. >> Right. >> The money making aspect of this is huge. >> Yeah. >> And I think that's what we're watching. >> Yep. >> As the business people come in and say, look at this, this is billions and billions of dollars. >> Yeah. >> This is-- >> Maybe just one more thought on that. The notion is really important, this is a distributed, not really owned by one person, one company, and there's the chaos that comes with that and so how do you do the balance between these two things? >> Yeah, yeah. >> Its like when, I know, when Amazon announced their Blockchain thing, it's like, Blockchain's supposed to be distributed. Now we have a company running it in one cloud. It's like that balance between the push and pull of centralization that we're going to see. >> Well have to put some computer science architecture together and put an operating system around it. >> There ya go. >> We'll have some dev ops. Steve, thanks for coming on theCUBE, great to have you on. >> Good to see you guys. >> Well it's great to see you. A legend in the industry, Steve Herrod, CUBE alumni from 2010, been on every year. Now a venture capitalist, former CTO of VMware. With Stu Miniman, I'm John Furrier, analyst of KubeCon, stay with us for more coverage after this short break. (upbeat techno music)

>> Live from Seattle, Washington, it's theCUBE, covering KubeCon and Cloud Native Con North America 2018. Brought to you by RedHat, the Cloud Native Computing Foundation and its ecosystem partners. >> Okay welcome back everyone we're here live in Seattle for KubeCon and Cloud Native Con. I'm John Furrier your host, Stu Miniman from Wikibon here. Next guests Anthony Lye, whose the senior vice president general manager of Cloud Data Services at NetApp, and Jonsi Stergesson, CTO and VP of Cloud Services. Great to have you guys on, great to see you again Anthony. >> As always thank you. >> So first I want to get out there we talked lots in the Kube lounge just to reset. The value parsons of NetApp have significantly been enhanced with the cloud. What is that value proposition? What have you guys seen the explosive headroom for value creation that you guys are enabling with NetApp and the cloud? >> You know what I think NetApp has done over now, probably five years, is really pushed itself to embrace the cloud. To recognize that the cloud is a very important part of everybody's IT infrastructure whether it's an extension of the existing IT infrastructure for things like DR or backup or whether it's the primary platform for legacy workloads or, as we're all here to do, to discuss the refactoring and rebuilding of applications around microservices. I think NetApp chose, unlike all of the traditional storage vendors, to see the cloud as an opportunity and I think it's helped the company and it's helped our customers to operate in what is, I think, is by default now, the end state for many companies is hybrid cloud. >> You guys also made some good moves early on with the cloud. We've documented certainly on SiliconANGLE and theCUBE early on. And then as flash comes in for performance, now you've got compute, storage and networking all being optimized in the cloud, creates app developers an environment where it's programmable infrastructure finally. I mean dev ops is happening, this is where services and notion of compute has gone from standing something up in seconds on the cloud to with functions milliseconds. This is changing the dynamic of applications but you've still got to store the data. Talk about, Jonsi, the impact of the services in piece to the developer, storage, services, provisioning, all that and it covers. >> We are taking, I mean all of our services that are running in all the hyperskills in Google and Azure and AWS and more and even on premise. Our view is our role is always to find the best home for any workload at any given time. Even though it's in public cloud or on premise. However storage has always been sort of left aside, it's always been living in this propietary chunk that is hard to move and the weight of the data is actually quite heavy. So we actually want to use Kubernetes and microservices and resistant volume claims by taking that data and making that very easily migratable replicated between locations, between hyperscalers and sort of adopt a true multi cloud strategy. With data with it not only moving those workloads or applications but the data is key, data is key. >> Sometimes, you know, you want to move the data to a compute and sometimes you want to move compute to the data. >> And that's been validated by Amazon's RDS announcement on VMware, Amazon announced outposting on premises, and the number one thing was latency, work was not yet moving. This is exactly to what you guys have been doing and implementing, today, this is like real product. >> I think the reality of the world is, you know, while there is a ton of innovation that exists in public cloud there are well documented use cases that struggle with a cloud only environment. I think NetApp has chosen to make each one of those three potential persistent stores equal to one another. So whether that's in a traditional on premise and upgrading on premise environments to get better price performance characteristics, embracing the public cloud or combining public and private cloud. >> While it's not trivial NetApp, at it's core, always was software so moving it from a hardware appliance, I mean, back in the day Network Appliance was the original name of the company to a software defined solution to being multi-cloud, you can kind of see that genesis where it can go. A lot of times the tougher part is from the customer standpoint. You know, the traditional person that bought and managed this was a storage administrator and getting them to understand cloud native applications and dev ops and all those things, those are pretty challenging moves so how much of it is education? How much of it is new buying centers inside the company or new clients, help us walk through that. >> Yeah I would make two points in maybe answering to you. So I think NetApp's history, actually 25 years ago, NetApp started off as selling into the developers who were running SUN workstations, who wanted shared everything and NetApp actually you know went around IT and put those appliances into the developers. We built a SaaN business, a very successful SaaN business, with the IT people. Now you're absolutely right, the people around here fall into the, sort of, the modern day dev ops characters. What Google calls the SREs the Site Reliability Engineers. And they're a new breed, they're young, they're doing more and more CICD. Storage is an integral part of what they do but maybe not a primary part. They expect storage to work. We are really lucky you know, a little company called Microsoft and another little company called Google sell our stuff so we get introduced into all of those cloud first, cloud only sort of use cases. Not just of refactoring of primary but building. So we're actually, in many cases now, very relevant to those people but we've been fortunate enough to leverage the big public clouds together. >> So you have a relationship with AWS, Google and Microsoft, Microsoft and Google, which you've just mentioned. You mentioned SRE, Site Reliability Engineer, this is a new persona that's clearly emerging and it has a focus around operations, now IT operations has been around for a long time, dev is changing too but this is, if they sell your stuff, their customers need to operate at scale. This is a big point, can you elaborate on the importance of this and what you guys are doing specifically to help that. >> So the Site Reliability Engineer, he is not doing operations. He is actually in charge of running the workload or the development or the application or the product that comes from development. They have to abide by specific rules that are actually set by the SRE. And to your point, because you were talking about different selling motions and not selling into the storage admin or not selling to traditional IT. This is actually what has actually been really surprising and showcases the power of Kubernetes and how widely adopted it has been, both on premise and in the public cloud because customers are actually coming to us and saying, "Hey we had no idea NetApp was actually "doing all of this in the public cloud. "We had no idea that you had your own Kubernetes services "that actually help solve one of the biggest problems "which is persistent volume claims and application of data." So it's actually coming, and you sort of see how important CNCF is, because they're actually educating the market and educating the enterprise space just as well as the new up and coming development team like I've traditionally come from. So I'm actually seeing that it's easier than I would have sort of thought in the beginning. So they're actually becoming more educated about microservices, more educated about how to run their, actually everybody almost in any company that I go into now, they have the SRE playbook somewhere in their meeting room somewhere and everybody sort of getting educated on how they need to, sort of, elevate themselves from being traditional system administrators into that SRE or dev op role. >> And it's also a cultural thing too, they have to develop, not just the playbook, but have some experience in economies of scale, managing it, and certainly it's a tail wind for you guys, storage because, again, it's also a lot of coating involved they need a pool of resources, storage being one of them. But the other thing that's interesting, those are single clouds, Amazon, Google, multi cloud is really where the action is, right? So multi cloud to me is just, to me, a modern version of multi vendor, which basically is about choice. Choice is critical, but having choice around the app, it becomes the value creator. So if you guys can scale with the app development environments that seems to be a sweet spot. How are you guys talking about that particular point because this becomes an under the covers, a new kind of operations, a new kind of scale, pushing code, not just you know stacking interacting boxes but, like, really making things, patching security things or could have been head of security things so doing things in a really really automated way. >> Yeah, I mean, I think the one thing I'm most proud of at my time at NetApp and what the team does and what the team continues to do is we took a very, very, I think, deliberate perspective that we would deliver storage, but we would do it in a very unique way. That my background was from Saas, I spent my entire career building applications, and when you build an application, you run the application, there is nothing you give the customer and say, "Here, administer it." When you look at a lot of the infrastructure services, they make the customer do a lot of work. So what we did at NetApp was we decided that we ourselves would almost create like an always available protocol that people could just ask for it and it would be there. There was no concept of setting it up or patching it or upgrading it. And that's really I think we have set a bar now on the public clouds that, I think, even the public clouds themselves have not done, and giving those developers that I asked for a storage through an API and all I need to do is ask for capacity and throughput. Nothing else, that's something to a developer they're like, "So now I don't even have to ask "anybody with storage skills. "I can tell my application to ask for it's own storage." >> It's interesting you're living in a new world where you need the scale of a system but the functionality of like an app server. I feel like we're living in that app server days where that middle ground and app development was the key focus, you've got to have both now. You need scalable systems but really application performance. >> And then you add an additional layer because now everybody wants to be able to use the same deployment script, the same configuration management system, Terraform, whatever they're actually using to deploy it on premise or in a public cloud but it needs to be done in a unified manner. This is why it's so important to be upstream compatible and there's a lot of companies out there that are actually destroying that model and not following the true cloud concept. >> Yes give them a slap on the wrist, get in line, fix it! >> If you are going to play in this space with the CNCF and with Kubenetes, you better play by the rules and do the open standards. And so you're actually compatible no matter where your workload resides. >> We've been monitoring how storage is maturing in this whole cloud native Kubenetes ecosystem here. A year ago there were a lot of backroom arguments over what were the right architectures, a few sub projects working through here, it actually blew me away in the keynote this morning to hear that 40% of all applications that are deployed in Kubernetes are stateful. So where are we? What's working? What's good for customers? And what do we still need to work on to kind of solidify the storage data piece of this? >> I think it's interesting, 'cause I think we, sort of, ourselves now consider NetApp to be a data company. Storage is an enabler but what's interesting, everyone talks about their Saas strategy, their PaaS strategy their IaaS strategies. I always ask people, "What's your data strategy?" and that's something I think the CNCF Kubernetes, themselves, recognize that they've done a lot of really great things for compute around the microservices themselves but the storage piece has always been something of a challenge. And we said, about solving that problem, we have an open source project called Trident, that essentially enables people to make persistent volume claims and if the container dies, they can essentially start a new container and pick up the storage exactly where they left off. So we really believe that stateful is an ever increasing percentage of the overall application model. Databases are important things, people need them. >> I would agree with that and that's developing too, it's early on. All right so I want to ask you guys a question, kind of outside the box. Multi cloud certainly is part of a hybrid, what they call a hybrid today, it's really a choice, multi cloud will be a future reality, no matter what anyone says, I believe that. How is multi cloud changing IT investments? Business investments, technical investments or both, what's your guys thoughts on how multi cloud is driving and changing IT investments? >> Well I actually think it offers you the opportunity to have like placement policy algorithms that fit your workload at any given time. For example, if this particular application is latency sensitive, and I created an application that all of a sudden became really popular in Mexico, then I should be able to see which one of the hyperscalers actually has a presence in Mexico City, deploy it there. If I'm under utilizing my private cloud and I have a lot of space on it and there is no specific requirements, it gives you that flexibility to, like I said, always find the best home for your workload at any given time. >> Dynamic policy based stuff? >> Yeah, precisely. And it allows you also, I mean, you can choose to do it whether its based on workload requirements or you can start doing it in a least cost effective route, I mean least cost routing. So it actually impacts both from a technical and a business sense in my opinion. >> I think you know you cannot help but get excited every day with what one cloud delivers over another cloud, and we're seeing something not unlike the arms race, you know, Google does this, then Amazon does this, then Microsoft does this. As developers we're very keen to take advantage of all these capabilities and we want to, in many cases, let the application itself make the decision. >> So yeah Amazons got there, everyone's catching up. Competitions good. All right, final question. Predictions for multi cloud in 2019. What's going to happen? Is there going to be a loud bang? Is there going to be a crash? Is it going to be fruit on the trees? What's the state of the multi cloud predictions for 2019? >> Well I actually believe it's going to become a standard. Nobody should be locked into any region or any one provider, I don't even care if it's on premise or NetOps specific, you should be able to... I mean, I think it's just going to become standard. Everybody has to have a multi cloud strategy and you can see that, like the IDC report that 86% of Fortune 500 companies are adopting multi cloud. And I think I'm actually quite fed up of this hyper cloud stuff because, in my opinion, on premise is just the fourth or the fifth hyperscaler and should be treated as such. So if you actually have that true cloud concept, you should be able to deploy that using the same script, the same APIs to deploy it everywhere. >> As I said in theCube the data center and non print, they're just an edge, a big edge. If it's an operating mall? >> My prediction? Your prediction. >> 2019 is the year of Istio. I think we've become enamored with Kubernetes, I think what Istio brings significantly advances Kubernetes, and we barely scratched the surface, I think, with the service mesh and all of the enhancements and all the contributions that will go into that. I think, you know, that 2019 will probably see as many vendors here next year with Istio credentials and STO capabilities as we see today with Kubernetes. >> Anthony, Jonsi, thanks for coming on, great insights, smart commentary, appreciate it. We should get in the studio and dig into this a little bit deeper. Really a great example of an incumbent, large company, NetApp, really getting a tailwind from the cloud, good smart bets you guys made, programmable infrastructure, dynamic policy routing, all kinds of under the covers goodness from smart cloud deployments. This is where software drives the data. >> Yep data is the new oil, that's what they say right? If you don't have a data set you're not very competitive. >> Thanks for coming on I appreciate it. More Kube coverage here, getting all the breakdown here, the impact of cloud computing at scale, the role of data software, all happening here at the CNCF. This is the KubeCon, I'm John Furrier and Stu Miniman, thanks for watching. More live coverage after this short break.

>> Live from Seattle, Washington, it's the Cube, covering KubeCon and Cloud Native Con North America 2018. Brought to you by Red Hat, the Cloud Native Computing Foundation and its ecosystem partners. >> Welcome back everyone. We are live in Seattle for KubeCon 2018, Cloud Native Con. It's the Cube, I'm John Furrier, your host with Stu Miniman. Our next guest is Ashesh Badani, who is the Vice-President and General Manager of Cloud Platforms at Red Hat. Great to see you, welcome back to the Cube. >> Thanks for having me on. Always good to be back. >> So you guys, again, we talk every year with you. It's almost like a check-in. So what's new? You got some big, obviously, the news about the IBM. We don't really want to get into that detail. I know you just a stop on that because it's already out there. But you guys had great success with platformers of service. Now you got the growth of Kubecon and Cloud Native Con, 8000 attendees and users. There's uptake. What's the update on the Red Had side? >> Yeah, we're excited. Excited to be back at Kubecon. It's bigger and better than it's ever been, I think so. That's fantastic. We've been investing in this community for over four years now, since 2014. Really, from the earliest days. Based the entire platform on it. Continue growing that, adding lots of customers across the world. And I think what's really been gratifying for us to see is just the diversity of participants. Both in user perspective as well as the wider ecosystem. So whether you're a storage player, a networking player, management, marketing, what have you. Everything sort of building around this ecosystem. I think we're creating a great amount of value and we're seeing diverse applications being built. >> So you guys have been good then on (mumbles), good timing, a lot of things are going on. This show is an open-source community, right. And that's been a great thing. This is kind of where the end users come from. But two other personas come in that we're seeing participate heavily. The IT pro, the IT expert, and then the classic developer. So you have kind of a melting pot of how this is kind of horizontally connecting. You guys have been successful in the IT side. Where is this impacting the end users?6 How is this open-source movement impacting IT, specifically, and at the end of the day, the developers who are writing code? Have to get more stuff out. What's your thoughts? >> So, we hosted OpenShift Commons yesterday. OpenShift Commons, for the the folks who don't know, is our gathering of participants within the larger OpenShift community. We had lots of end users come and talk about the reason they're adopting a Kubernetes-based platform is to get greater productivity. So for example, if you're someone like Progressive Insurance, an established organization, how do you release applications quicker? How do you make your developers more productive? How do you enable them to have more languages, tools, frameworks at their disposal? To be able to compete in this world where you've got start-ups, you've got other companies trying to compete aggressively with you. I think it's a big dent here, right? It's not just for if you work traditional IT. But it's for if you were a company of all sizes. >> When you talk about customers, every customer is different. You've got, you look at IT, everything is additive, it tends to be a bit of a heterogeneous mess when you get there. Help connect for us what are you hearing from customers? How does, not just Kubernetes, but everything going on here in the Cloud Native environment? How is it helping them? How is it changing the way that they do their business and how's Red Hat involved? >> So one thing we've been noticing is that Hybrid Cloud is here and here to stay. So we've consistently been hearing this from customers. They've invested lots of money and time and energy, skills, in their existing environments. And they want to take advantage of public clouds. But they want to do that with flexibility, with portability, to bring to bear. What we've been trying to do is focus on exactly that. How do we help solve that problem and provide an abstraction. How do you provide primitives. So, for example, we announced our support of Knative, and how we'll make that available as part of OpenShift. Why's that? Well, how can we provide Serverless primitives within the platform so folks can have the flexibility to be able to adopt next-generation technologies. But to be able to do that consistently regardless of where they deploy. >> So, I love that. Talk about meeting the customers there. One of the things that really strikes me, there's so much change going on in the industry. And that's an area that Red Hat has a couple decades of experience. Maybe help explain how Red Hat in bringing some of that enterprise, oversight. Just like they've done for Linux for a long time. >> Yeah, yeah. Stu, you're following us very closely, as are you John, and the team at the Cube. We're trying to embrace that change as it comes upon us. So, I think the last time I was here, I was here with Alex Polvi of Core OS. Red Hat acquired Core OS in January. >> Big deal. >> Yeah, big acquisition for us. And now we're starting to see the fruits of some of that labor. In terms of integrating that technology. Why did we do that? We wanted to get more automation into the platform. So, customers have said, hey, look, I want these clusters to be more self-managing, self-healing. And so we've been really focused on saying how can we take those challenges the customers have, bring that directly into a platform so they're performing more and more like the expectations that they have in the public cloud, but in these diverse, introgenous, environments. >> That speaks to the operating model of cloud. You guys have a wholistic view because you're Red Hat. You got a lot of customers. You have the Dev House model, you got the Kubernetes container orchestration, micro-services. How does that all connect together for the customer? I mean, is it Turn Key and Open Shift? You guys had that nice bet with Core OS, pays big, huge dividends. What are some of those fruits in the operating model? So the customer has to think about the systems. It's a systems model, it's an operating system, so-to-speak. But they still got to develop and build apps. So you got to have a systems-wholistic view and be able to deliver the value. Where does it all connect? What's your explanation? >> So distributed systems are complex. And we're at the point where no individual can keep track of the hundreds, the thousands, the hundred-thousand containers that are running. So, the only way, then, to do it is to be able to say, how can the system be smart? So, at the Commons yesterday we had sort of a tongue-in-cheek slide that said, the factory of the future will only have two employees, a man and a dog. The man's there to feed the dog, and the dog's in place to ensure the man doesn't go off and actually touch the equipment. And the point really being, how can we bring technology that can bring that to bare. So, one example of that is actually through our Core OS acquisition. The Core OS team was working on a technology called, operators. Which is to say, how can we take the human knowledge that exists. To take complex software that's built by third parties and bring that natively into the platform and then have the platform go and manage them on behalf of the actual customer itself. Now we've got over 60 companies building operators. And we've, in fact, taken entire open-shift platforms, put operators to work. So it's completely automated and self-managed. >> The trend of hybrid is hot. You mentioned it's here to stay. We would argue that it's going to be a gateway to multi-cloud. And as you look at the stacks that are developing and the choices, the old concept of a stack-- and Chris was on earlier, the CTO of CNCF. And I kind of agree with him. The old notion of stack is changing because if you've got a horizontal, scale-able cloud framework, you got specialty with machine learning at the top, you got a whole new type of stack model. But, multi-cloud is what the customers want choice for. Red Hat's been around long enough to know what the multi-vendor word was years ago. Multi-vendor choice, multi-cloud choice. Similar paradigms happening now. Modern version of multi-vendor is multi-cloud. How do you guys see the multi-cloud evolution? >> So we keep investing and helping to make that a reality. So, last week, we made some announcements around Open Shift dedicators. Open Shift dedicators is the Open Shift manage service, or AWS. Open Shift is available in ways where it can be self-managed directly by customers in a variety of environments. Directly run around any public cloud or open stack, or what you'd like environment. We have third-party partners. For example, DXC D-systems providing managed versions of Open Shift. And then you can have Red Hat managed Open Shift for you. For example, on AWS, or coming next year, with Microsoft. Through our partnership for Open Shift on Azure. So you as a customer now have, I think, more choice than you ever had before. In terms of adopting Dev-Ops or dealings with micro-services. But then having flexibility with regard to taking advantage of tools, services, that are coming from, pretty much, every corner of IT industry. >> You guys have a huge install base. You've been servicing customers for many, many years, decades. Highest level support. Take us through what a customer, a traditional Red Hat customer that might not be fully embracing the cloud in the past, now is on-boarding to the cloud. What's the playbook? What do you guys offer them? How do you engage with them? What's the playbook? Is it, just buy Open Shift? Is there a series of-- how do you guys bring that Red Hat core Lenux customer that's been on Prim. Maybe a little bit out of shadow IT in the cloud, saying, hey, we're doing additional transformation. What's the playbook? >> So, great question, John. So, first fall into the transformation might be an over-hyped term. Might be a peak hype at this point in time. But I think that the bigger point from my perspective is how do you move more dollars, more euros, more spend towards innovation. That's what every company is sort of trying to do. So, our focus is, how can we build on the investments that they've made? At this point in time, (mumbles) Lenux probably has 50,000 customers. So, pretty much, every customer, any size, around the world, is some kind of Lenux user. How can we then say, how can we now provide you a platform to have greater agility and be able to develop these services quicker? But, at the same time, not forget the things that enterprises care about. So, last week we had our first big security issue released on Kubernetes. The privilege escalation flaw. And so, obviously, we participate in the community. We had a bunch of folks, along with others addressing that, and then we rolled our patches. Our patch roll-out went back all the way to version 3.2, 3.2 shipped in early 2016. Now, the one hand you say, hey, everyone has Dev-Ops, why do you need to have a patch for something that's from 2016? That's because customers still aren't moving as quickly as we'd like. So, I just want to temper, there's an enthusiasm with regard to, everyone's quick, everything's lightning fast. At the same time, we often find-- and so, going back to your question, we often find some enterprises will just take a little bit longer, in reality to kind of get-- (both speaking at once) >> Work loads, they're not going to be moving overnight. >> That's right. >> So there's some legacy from those workloads. >> Right, right. And so, what we want to do is ensure, for example, the platform. So we talked about the security and lifecycle. But, is supporting these Cloud Native, next generation, stateless applications, but also established legacy stateful applications all on the same platform. And so the work we're doing is ensure we don't-- you know, it's like, leave no application behind. So, either the work that we'll do, for example, with Red Hat Innovation Labs. We help sort of move that forward. Or with GSIs, global integrated, real integrators to bring those to bare. >> Ashesh, wonder if we could drill a little bit. There's a lot of re-training that needs to happen. I've been reading lots on there. It's not, oh, I bring in this new Cloud Native team that's just going to totally re-vamp it and take my old admins and fire them all. That's not the reality. There's not enough training people to do all of this wonderful stuff. We see how many people are at this show. Explain what Red Hat's doing. Some of the training maturation, education paths. >> So we do a lot of work on the just core training aspect, learning services, get folks up to speed. There's work that happens, for example, in CNCF. But we do the same thing around certifications, around administering the systems, developing applications, and so on. So that's one aspect that needs to be learned. But then there's another aspect with regard to how do we get the actual platform, itself, to be smart enough to do things, that in the past, individual people had to do? So, for example, if we were to sort of play out the operator vision fully and through execution. In the past, perhaps you needed several database admins. But, if you had operators built for databases, which, for example couch, base, and mongo, and others, have built out. You can now run those within the platform and then that goes and manages on behalf. Now you don't need as many database admins, you free those people up now to build actual business innovation value. So, I think what we're trying to do is increasingly think about how we sort of, if you will, move value up the stack to free up resources to kind of work on building the next generation of services. And I think that's our business transformation work. >> And I think, even though digital transformation is totally over-hyped, which I agree, it actually is really relevant. Because I think the cloud wave, right now, has been certainly validated. But what's recognized is that, people have to re-imagine how they do their infrastructure. And IT is programmable. You're seeing the network. The holy trinity of IT is storage, networking, and compute. So, when you start thinking about that in a way that's cloud-based, it's going to require them to, I don't want to say re-platform, but really move to an operating-environment that's different, that they used to have. And I think that is real. We're seeing evidence of that. With that in mind, what's next? What do you guys got on the horizon? What's the momentum here? What's the most important story that you guys are telling here at Red Hat? And what's around the corner? >> Yeah, so obviously, I talked about a few announcements that we made right around Open Shift Dedicated and the upgrades around that. And things like, for example, supporting bring-your-own-cloud. So, if you got your own Amazon security credentials, we help support that. And manage that on your behalf, as well. We've talked this week about our support native, trying to introduce more server-less technologies into Open Shift. We announced the contribution of SCD to the Cloud Native Computing Foundation. So, continuing re-affirming our commitment to the community I think looking ahead, going forward, our focus next year will be on Open Shift four, which will be the next release of the platform. And there, it's all about how do we give you a much better install than upgrade experience than you've had before? How do we give you these clusters that you can deploy in multiple different environments and manage that better for you? How do we introduce operators to bring more and more automation to the platform? So, for the next few months our focus is on creating greater automation in the platform and then enabling more and more services to be able to run on that. >> Pretty exciting for you guys riding the wave, the cloud wave. Pretty dynamic. A lot of action. You've guys have had great success, congratulations. >> Thank you very much. >> You're fun to watch. The Cube coverage here. We're in Seattle for KubeCon 2018 and Cloud Native Con. I'm John your host. Stay with us for more coverage of day one of three days of coverage after this short break. We'll be right back. (upbeat music)