>> (upbeat music) >> production: From around the globe, it's the Cube covering Google cloud Next on-Air 20. (Upbeat music) >> Welcome back. I'm Stu Miniman and this is the CUBE coverage of Google cloud Next on Air 20. Of course, the nine week distributed all online program that Google cloud is doing and going to be talking about, of course, multi-cloud, Google of course had a big piece in multi-cloud. When they took what was originally Borg, They built Kubernetes. They made that open source and gave that to the CNCF and one of Google's partners and a leader in that space is of course, Red Hat. Happy to welcome to the program Sathish Balakrishnan, he is the Vice President of hosted platforms at Red Hat. Sathish, thanks so much for joining us. >> Thank you. It's great to be here with you on Google Cloud Native insights. >> Alright. So I, I tied it up, of course, you know, we talk about, you know, the hybrid multicloud and open, you know, two companies. I probably think of the most and that I've probably said the most about the open cloud are Google and Red Hat. So maybe if we could start just, uh, you hosted platforms, help us understand what that is. And, uh, what was the relationship between Red Hat and the Open Shift team and Google cloud? >> Absolutely. Great question. And I think Google has been an amazing partner for us. I think we have a lot of things going on with them upstream in the community. I think, you know, we've been with Google and the Kubernetes project since the beginning and you know, like the second biggest contributor to Kubernetes. So we have great relationships upstream. We also made Red Hat Enterprise Linux as well as Open Shift available on Google. So we have customers using both our offerings as well as our other offerings on Google cloud as well. And more recently with the hosted our offerings. You know, we actually manage Open Shift on multiple clouds. We relaunched our Open Shift dedicated offering on Google cloud back at Red Hat Summit. There's a lot of interest for the offering. We had back offered the offering in 2017 with Open Shift Three and we just relaunched this with Open Shift Four and we received considerable interest for the Google cloud Open Shift dedicated offering. >> Yeah, Sathish maybe it makes sense if we talk about kind of the maturation of open source solutions, managed services has seen really tremendous growth, something we've seen, especially if we were talking about in the cloud space. Maybe if you could just walk us through a little bit out that, you know, what are you hearing from customers? How does Red Hat think about managed solutions? >> Absolutely. Stu, I think it was a good question, right? I think, uh, as we say, the customers are looking at, you know, multiple infrastructure footprints, Be iteither the public cloud or on-prem. They'll start looking at, you know, if I go to the cloud, you know, there's this concept of, I want something to be managed. So what Open Shift is doing is in Open Shift, as you know it's Red Hat's hybrid cloud platform and with Open Shift, all the things that we strive to do is to enable the vision of the Open Hybrid Cloud. Uh, so, but Open Hybrid Cloud, it's all about choice, So we want to make sure the customers have both the managed as well as the self managed option. Uh, so if you really look at it, you know, Red Hat has multiple offerings from a managed standpoint. One as you know, we have Open Shift dedicated, which runs from AWS and Google. And, you know, we just have, as I mentioned earlier. We relaunched our Google service at Red Hat Summit back in May. So that's actually getting a lot of traction. We also have joint offerings with Azure that we announced a couple of years back and, there's a lot of interest for that offering as well as the new offering that we announced post-summit, the Amazon-Red Hat Open Shift, which basically is another native offering that we have on Amazon. If you really look at, having, having spoken about these offerings, if you really look at Red Hat's evolution as a managed service provider in the public cloud, we've been doing this since 2011. You know, that's kind of surprising for a lot of people, but you know, we've been doing Open Shift online, which is kind of a multi-tenant parcel multi-talent CaaS solution 2011. And we are one of the earliest providers of managed kubernetes, you know, along with Google Kubernetes engine GKE, we are our Open Shift dedicated offering back in 2015. So we've been doing Kubernetes managed since, Open Shift 3.1. So that's actually, you know, we have a lot of experience with management of Kubernetes and, you know, the devolution of Open Shift we've now made it available and pretty much all the clouds. So that customers have that exact same experience that they can get any one cloud across all clouds, as well as on-prem. Managed service customers now have a choice of a self managed Open Shift or completely managed Open Shift. >> Yeah. You mentioned the choice and one of the challenges we have right now is there's really the paradox of choice. If you look in the Kubernetes space, you know, there are dozens of offerings. Of course, every cloud provider has their offerings. You know, Google's got GKE, they have Anthos, uh, they, they have management tools around there. You, you talked a bit about the, you know, the experience and all the customers you have, the, you know, there's one of the fighters talks about, there's no compression algorithm for experience. So, you know, what is Red Hat Open Shift? What really differentiates in the market place from, you know, so many of the other offerings, either from the public high providers, some of the new startups, that we should know. >> Yeah. I think that's an interesting question, right? I think all Google traders start with it's complete open source and, you know, we are a complete open source company. So there is no proprietary software that we put into Open Shift. Open Shift, basically, even though it has, you know, OC command, it basically has CPR. So you can actually use native Google networks as you choose on any Google network offering that you have be it GKE, EKS or any of the other things that are out there. So that's why I think there are such things with google networks and providers and Red Hat does not believe in open provider. It completely believes in open source. We have everything that we is open source. From an it standpoint, the value prop for Red Hat has always been the value of the subscription, but we actually make sure that, you know, Google network is taken from an upstream product. It's basically completed productized and available for the enterprise to consume. But that right, when we have the managed offering, we provide a lot more benefits to it, right? The benefits are right. We actually have customer zero for Open Shift. So what does that mean? Right. We will not release Open Shift if we can't run open Shift dedicated or any of their (indistinct) out Open Shift for them is under that Open Shift. Really really well. So you won't get a software version out there. The second thing is we actually run a lot of workloads, but then Red Hat that are dependent on our managed or open shift off. So for example, our billing systems, all of those internal things that are important for Red Hat run on managed Open Shift, for example, managed Open Shift. So those are the important services for Red Hat and we have to make sure that those things are running really, really well. So we provide that second layer of enterprise today. Then having put Open Shift online, out that in public. We have 4 million applications and a million developers that use them. So that means, I've been putting it out there in the internet and, you know, there's security hosts that are constantly being booked that are being plugged in. So that's another benefit that you get from having a product that's a managed service, but it also is something that enterprises can now use it. From an Open Shift standpoint, the real difference is we add a lot of other things on top of google network without compromising the google network safety. That basically helps customers not have to worry about how they're going to get the CIC pipeline or how they have to do a bunch of in Cobra Net as an outside as the inside. Then you have technologies like Store Street Metrics kind of really help customers not to obstruct the way the containerization led from that. So those are some of the benefits that we provide with Open Shift. >> Yeah. So, so, so Sathish, as it's said, there's lots of options when it comes to Kubernetes, even from a Red Hat offering, you've got different competing models there. If I look inside your portfolio, if it's something that I want to put on my infrastructure, if I haven't read the Open Shift container platform, is that significantly different from the managed platform. Maybe give us a little compare contrast, you know. What do I have to do as a customer? Is the code base the same? Can I do, you know, hybrid environments between them and you know, what does that mean? >> It's a smart questions. It's a really, really good question that you asked. So we actually, you know, as I've said, we add a lot of things on top of google network to make it really fast, but do you want to use the cast, you can use the desktop. So one of the things we've found, but you know, what we've done with our managed offering is we actually take Open Shift container platform and we manage that. So we make sure that you get like a completely managed source, you know. They'll be managed, the patching of the worker nodes and other things, which is, again, another difference that we have with the native Cobra Net of services. We actually give plush that admin functionality to customers that basically allows them to choose all the options that they need from an Open Shift container platform. So from a core base, it's exactly the same thing. The only thing is, it's a little bit opinionated. It to start off when we deploy the cluster for the customer and then the customer, if they want, they can choose how to customize it. So what this really does is it takes away any of the challenges the customer may have with like how to install and provision a cluster, which we've already simplified a lot of the open shift, but with the managed the Open Shift, it's actually just a click of it. >> Great. Sathish Well, I've got the trillion dollar question for you. One of the things we've been looking at for years of course, is, you know, what do I keep in my data center? What do I move to the cloud? How do I modernize it? We understand it's a complex and nuanced solution, but you talk to a lot of customers. So I, you know, here in 2020, what's the trends? What are some of the pieces that you're seeing some change and movement that, you know, might not have been the case a year ago? >> I think, you know, this is an interesting question and it's an evolving question, right? And it's something that if you ask like 10 people you'll get real answers, but I'm trying to generalize what I've seen just from all the customer conversations I've been involved. I think one thing is very clear, right? I think that the world is right as much as anybody may want to say that I'm going to go to a single cloud or I'm going to just be on prem. It is inevitable that you're going to basically end up with multiple infrastructure footprint. It's either multicloud or it's on Prem versus a single cloud or on prem versus multiple cloud. So the main thing is that, we've been noticing as, what customers are saying in a whole. How do I make sure that my developers are not confused by all these difference than one? How do I give them a consistent way to develop and build their applications? Not really worry about, what is the infrastructure. What is the footprint that they're actually servicing? So that's kind of really, really important. And in terms of, you know, things that, you know, we've seen customers, you know, I think you always start with compliance requirements and data regulations. Back there you got to figure it out. What compliance do I need? And as the infrastructure or the platform that I'm going to go to meet the compliance requirements that I have, and what are the data regulations? You know, what is the data I'm going to be setting? Is it going to meet the data submitted rules that my country or my geo has? I got to make sure I worry about that. And then I got to figure out if I'm going to basically more to the cloud from the data center or from one cloud to another cloud. I might just be doing a lift or shift. Am I doing a transformation? What is it that I really worry about? In addition to the transformation, they got to figure it out, or I need to do that. Do I not need to do that? And then, you know, we've got to figure out what your data going to set? What your database going to look in? And do you need to connect to some legacy system that you have on prem? Or how do you go? How do you have to figure that out and give them all of these complexities? This is really, really common for any large enterprise that has like an enterprise ID for that multi-cloud. That's basically in multiple geographies, servicing millions of customers. So that has a lot of experience doing all these things. We have open innovation labs, which are really, really awesome experience for customers. Whether they take a small project, they figured out how to change things. Not only learn how to change things from a technology standpoint, but also learn how to culturally change things, because a lot of these things. So it's not just moving from one infrastructure to another, but also learning how to do things differently. Then we have things like the container adoption programmer, which is like, how do you take a big legacy monolith application? How do you containerize it? How do you make it micro services? How do you make sure that you're leveraging the real benefits that you're going to get out of moving to the cloud or moving to a container platform? And then we have a bunch of other things like, how do you get started with Open Shift and all of that? So we've had a lot of experience with like our 2,400 plus customers doing this kind of really heavy workload migration and lifting. So the customers really get the benefits that they see out of Open Shift. >> Yeah. So Sathish, if I think about Google, specifically talking about Google cloud, one of the main reasons we hear customers using Google is to have access to the data services. They have the AI services they have. So how does that tie into what we were just talking about? If I, if I use Open Shift and you know. I'm living in Google cloud, can, can I access all of those cloud native services? Are there any nuances things I need to think about to be able to really unleash that innovation of the platform that I'm tying into? >> Yeah, absolutely not. Right. I think it's a great question. And I think customers are always wondering about. Hey, if I use Open Shift, am I going to be locked out of using the cloud services? And if anything run out as antilock. We want to make sure that you can use the best services that you need for your enterprise, like the strategy as well as for applications. So with that, right. And we've developed the operator framework, which I think Google has been a very early supporter of. They've built a lot of operators around their services. So you can develop those operators to monitor the life cycle of these services, right from Open Shift. So you can actually connect to an AI service if you want. That's absolutely fine. You can connect the database services as well. And you can leverage all of those things while your application runs on Open Shift from Google cloud. Also I think that done us right. We recognize that, when you're talking about the open hybrid cloud, you got to make sure that customers can actually leverage services that are the same across different clouds. So when you can actually leverage the Google services from On Prem as well, if you choose to have localized services. We have a large catalog of operators that we have in our operator hub, as well as in the Red Hat marketplace that you can actually go and leverage from third party, third party ISV, so that you're basically having the same consistent experience if you choose to. But based on the consistent experience, that's not tied to a cloud. You can do that as well. But we would like for customers to use any service that they want, right from Open Shift without any restrictions. >> Yeah. One of the other things we've heard a lot from Google over the last year or so has been, you know, just helping customers, especially for those mission, critical business, critical applications, things like SAP. You talked a bit about databases. What advice would you give customers these days? They're, they're looking at, you know, increasing or moving forward in their cloud journeys. >> I think it sounds as an interesting question because I think customers really have to look at, you know, what is the ID and technology strategy? What are the different initiatives to have? Is it digital transformation? Is it cloud native development? Is it just containerization or they have an overarching theme over? They've got to really figure that out and I'm sure they're looking at it. They know which one is the higher priority when all of them are interrelated and in some ways. They also got to figure out how they going to expand to new business. Because I think as we said, right, ID is basically what is driving personal software is eating the load. Software services are editing them. So you got to figure out, what are your business needs? Do you need to be more agile? Do you need to enter new businesses? You know, those are kind of important things. For example, BMW is a great example, they use Open Shift container platform as well as they use Open Shift dedicated, you know. They are like a hundred hundred plus year old car, guess, you know what they're trying to do. They're actually now becoming connected car infrastructure. That's the main thing that they're trying to build so that they can actually service the cars in any job. So in one shoe, they came from a car manufacturing company to now focus on being a SAS, an Edge and IOT company. If you really look at the cars as like the internet of things on an edge computer and what does that use case require? That use case cannot anymore have just one data center in Munich, they have to basically build a global platform of data centers or they can really easily go to the cloud. And then they need to make sure that that application double close when they're starting to run on multiple clouds, multiple geographies, they have the same abstraction layer so that they can actually apply things fast. Develop fast. They don't have to worry about the infrastructure frequently. And that's basically why they started using Open Shift. And don't know why they're big supporters of Open Shift. And then I think it's the right mission for their use. So I think it really depends on, you know, what the customer is looking for, but irrespective of what they're looking for, I think Open Shift nicely fits in because what it does, is it provides you that commonality across all infrastructure footprints. It gives you all the productivity gains and it allows you to connect to any service that you want anywhere because we are agnostic to that and as well as we bring a whole lot of services from Red Hat marketplace so you can actually leverage your status. >> Well, Sathish Balakrishnan, thank you so much for the updates. Great to hear about the progress you've got with your customers. And thank you for joining us on the Google cloud Next On Air Event. >> Thank you Stu. It's been great talking to you and look forward to seeing you in person one day. >> Alright. I'm Stu Miniman. And thank you as always for watching the Cube. (upbeat music) (upbeat music)

>> 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)