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

(bright upbeat music) >> Hey, guys. Welcome back to Detroit, Michigan. Lisa Martin and John Furrier here live with "theCUBE" at KubeCon CloudNativeCon, 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. It's maturing. >> Yeah, we got three days of wall-to-wall coverage, all about Kubernetes. We heard about Security, Large scale, Cloud native at scale. That's the big focus. This next segment's going to be really awesome. You have a fast growing private company and a practitioner, big name, blue chip practitioner, building out next-gen cloud. First transforming, then building out the next level. This is classic, what we call Super Cloud-Like interview. It's going to be great. I'm looking forward to this. >> Anytime we can talk about Super Cloud, right? Please welcome back, one of our alumni, Haseeb Budhani is here, the CEO of Rafay. Great to see you. Santhosh Pasula, also joins us, the global head of Cloud SRE at Mass Mutual. Guys, great to have you on the program. >> Thanks for having us. >> Thank you for having me. >> So, Haseeb, you've been on "theCUBE" many times. You were on just recently, with the momentum 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 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 live in this industry, and I'm seeing companies that I don't know, which is a good thing. It means that 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 KubeCons. Like when we hung out at in Valencia, for example, or even other places, it hasn't been this many people. Which means, and 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 for their applications going forward. And that to me is very, very good. >> Definitely, becoming foundational. >> Haseeb: Yeah. >> Well, you guys got a great traction. We had many interviews at "theCUBE," and you got a practitioner here with you guys, are both pioneering, kind of what I call the next-gen cloud. First you got to 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 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 minutes back. And the whole cloud journey in big companies, large financial institutions, healthcare industry or insurance sector, it takes generations of leadership to get to that perfection level. And ideally, the cloud for strategy starts in, and then how do you standardize and optimize cloud, right? That's the second-gen altogether, and then operationalization of the cloud. And especially if you're talking about Kubernetes, in the traditional world, almost every company is running middleware and their applications in middleware. And their containerization is a topic that came in. And Docker is basically the runtime containerization. So, that came in first, and from Docker, eventually when companies started adopting Docker, Docker Swarm is one of the technologies that they adopted. And eventually, when we were taking it to a more complicated application implementations or modernization efforts, that's when Kubernetes played a key role. And as Haseeb was pointing out, 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. >> 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 past the stage of proof of concepts, proof of technologies, pilot implementations. We are actually playing it, the real game now. In the past, I used the quote, like "Hello world to real world." So, we are actually playing in the real world, not in the hello world anymore. Now, this is where the real time challenges will pop up. 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? The demands that come out of regulations are met? And how are you going to scale it? And while scaling, how are you going to keep up with all the governance and regulations that come with it? So we are in that stage today. >> Haseeb talked about, you talked about the great evolution of what's going on at Mass Mutual. Haseeb talk a little bit about who? You mentioned one of the things that's surprising you about this KubeCon in Detroit, is that you're seeing a lot more enterprise folks here? Who's deciding in the organization and your customer conversations? Who are the decision makers in terms of adoption of Kubernetes these days? Is that elevating? >> Hmm. Well, this guy. (Lisa laughing) 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 somebody, a CTO, CIO level, an individual is making a decision. I have multiple internal Bus 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 sort of 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 your developer, both have to be happy. If you don't solve for both, you know, constituencies, you're not going to be successful. >> So, you're targeting the builder of the infrastructure and the consumer of that infrastructure? >> Yes, sir. It has to be both. >> On the other side? >> Exactly, right. So that look, honestly, it takes iteration to figure these things out. 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? Because if you don't have a platform strategy, you're going to 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 Santhosh, I want to get to you. You mentioned your transformations, 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. >> Haseeb: 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 can be portable, but the situation isn't. So, Borg 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 totally agree. Google introduce SRE, Site Reliability Engineering. And if you take the traditional transformation of the roles, in the past, it was called operations, and then DevOps ops came in, and then SRE is the new buzzword. And the future could be something like Product Engineering. And in this journey, here is what I tell folks on my side, like what worked for Google might not work for a financial company. It might not work for an insurance company. It's okay to use the word, SRE, but end of the day, that SRE has to be tailored down to your requirements. And the customers that you serve, and the technology that you serve. >> This is why I'm coming back, this platform engineering. At the end of the day, I think SRE just translates to, you're going to have a platform engineering team? 'Cause you got to enable developers to be producing more code faster, better, cheaper, guardrails, policies. It's kind of becoming the, these serve the business, which is now the developers. IT used to serve the business back in the old days, "Hey, the IT serves the business." >> Yup. >> Which is a term now. >> Which is actually true now. >> 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. >> The hard line between development and operations, so that's thinning down. Over the time, that line might disappear. And that's where SRE is fitting in. >> Yeah, and then building platform to scale the enablement up. So, what is the key challenges? You guys 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 I may go first. The faster market to value that we are bringing to the table, that's very important. Business has an idea. How do you get that idea implemented in terms of technology and take it into real time? So, that journey we have cut down. Technology is like Kubernetes. It makes an IT person's life so easy that they can speed up the process. In a traditional way, what used to take like an year, or six months, can be done in a month today, or less than that. So, there's definitely 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. These are today, it is possible to make that happen with a click off a button. In the past, it used to take, probably, 100-person team, and operational team to do it, and a lot of time. But that automation is happening. And we can get into the technology as much as possible, but blueprinting and all that stuff made it possible. >> We'll save that for another interview. We'll do it deep time. (panel laughing) >> But the end user on the other end, the consumer doesn't have the patience that they once had, right? It's, "I want this in my lab now." How does the culture of Mass Mutual? How is it evolve to be able to deliver the velocity that your customers are demanding? >> Once in a while, it's important to step yourself into the customer's shoes and think it 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 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, Docker Swam or Kubernetes, business doesn't even care about it. What they really care about, it is, if your environment goes down, it's a problem. And if your environment or if your solution is not as efficient as the business needs, that's the problem, right? So, at that point, the business will step in. So, our job is to make sure, 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 going to 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 can say that, you're the vCenter of Kubernetes. I mean, as as metaphor, a place to manage it all, is all one paint of glass, so to speak. Is that how you see success in your environment? >> So, virtualization has gone a long way. Where we started, what we call bare metal servers, and then we virtualized operating systems. Now, we are virtualizing applications, and we are virtualizing platforms as well, right? So that's where Kubernetes plays a role. >> So, you see the need for a vCenter like thing for Kubernetes? >> There's definitely a need in the market. The way you need to think is like, let's say there is an insurance company who actually implement it today, and they gain the market advantage. Now, the the competition wants to do it as well, right? So, there's definitely a virtualization of application layer that's very critical, and it's a critical component of cloud strategy as a whole. >> See, you're too humble to say it. I'll say, you're like the vCenter of Kubernetes. Explain what that means in your term? If I said that to you, what would you react? How would you react to that? Would you say, BS, or would you say on point? >> Maybe we should think about what does vCenter do today? So, in my opinion, by the way, vCenter in my opinion, is one of the best platforms ever built. Like it's the best platform in my opinion ever built. VMware did an amazing job, because they took an IT engineer, and they made him now be able to do storage management, networking management, VM's multitenancy, access management, audit. Everything that you need to run a data center, you can do from essentially single platform. >> John: From a utility standpoint, home-run? >> It's amazing. >> Yeah. >> Because you are now able to empower people to do way more. Well, why are we not doing that for Kubernetes? So, the premise man Rafay was, well, I should have IT engineers, same engineers. Now, they should be able to run fleets of clusters. That's what people that Mass Mutual are able to do now. So, to that end, now you need cluster management, you need access management, you need blueprinting, you need policy management. All of these things that have happened before, chargebacks, they used to have it in vCenter, now they need to happen in other platforms but for Kubernetes. So, should we do many of the things that vCenter does? Yes. >> John: Kind of, yeah. >> Are we a vCenter for Kubernetes? >> No. >> That is a John Furrier question. >> All right, well, the speculation really goes back down to the earlier speed question. If you can take away 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. This is becoming a real discussion point in the industry, is that, "Yeah, we got new tool. Look at the shiny new toy." But if it 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 hit my mind, is think about the hoteling industry before Airbnb and after Airbnb. Or the taxi industry before Uber and after Uber. 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 build their application and deploy it, and run it. They don't have to worry about provisioning of the servers, and then building the Middleware on top of it, and then, do a bunch of testing to make sure they iron out all the compatible issues and whatnot. Now, today, all I say is like, "Hey, 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 you do is like, do the correction. >> John: Shipping. >> Shipping. You build the production. >> John: Press. Go. Release it. (laughs) That when you move on, but they were there. I mean, we're there now. We're there. So, we need to see the future, because 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 there's, I call the Architectural List Environment where it's like, you don't need architecture, it's already happening. >> Yeah, and on top of it, if someone has an idea, they want to implement an idea real quick. So, how do you do it? And you don't have to struggle building an environment to implement your idea and test it in real time. So, from an innovation perspective, agility plays a key role. And that's where the Kubernetes platforms, or platforms like Kubernetes plays. >> You know, Lisa, when we talked to Andy Jassy, when he was the CEO of AWS, either one-on-one or on "theCUBE," he always said, and this is kind of happening, "Companies are going to be builders, where it's not just utility, you need that table stakes to enable that new business idea." And so, in this last keynote, he did this big thing like, "Think like your developers are the next entrepreneurial revenue generators." I think I'm starting to see that. What do you think about that? You see that coming sooner than later? Or is that an insight, or is that still ways away? >> I think it's already happening at a level, at a certain level. Now ,the question comes back to, you know, taking it to the reality. I mean, you can do your proof of concept, proof of technologies, and then prove it out like, "Hey, I got a new idea. This idea is great." And it's to the business advantage. But we really want to see it in production live where your customers are actually using it. >> In 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 both of you gentlemen said a word as you were talking, you used the word, Guardrails. We're talking about agility, but 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. Guardrails are like children, you know, shouldn't be heard. They're seen but not heard. Developers don't care about guardrails, they just want to go fast. >> They also bounce around a little bit, (laughs) off the guardrails. >> Haseeb: Yeah. >> One thing we know that's not going to slow down, is the expectations, right? Of all the consumers of this, the Devs, the business, the business top line, and, of course, the customers. So, the ability to really, as your website says, let's say, "Make Life Easy for Platform Teams" is not trivial. And clearly what you guys are talking about here, is you're really an enabler of those platform teams, it sounds like to me. >> Yup. >> 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 evolution of Kubernetes, why? And really, what the focus should be on those platform teams. We appreciate all your time and your insights. >> Thank you so much for having us. >> Thanks for having us. >> Our pleasure. For our guests and for John Furrier, I'm Lisa Martin. You're watching "theCUBE" Live, KubeCon CloudNativeCon from Detroit. We'll be back with our next guest in just a minute, so stick around. (bright upbeat music)

(upbeat music) >> Live on the floor in San Francisco for AWS Summit. I'm John Furrier, host of theCUBE. Here for the next two days getting all the action back in person. We're at AWS re:Invent, a few months ago. Now we're back, events are coming back and we're happy to be here with theCUBE. Bring all the action, also virtual, we have a hybrid cube. Check out theCUBE.net, siliconangle.com for all the coverage. After the event we've got a great guest ticking off here. Matthew Park, Director of Solutions Architecture with Innovation Solutions, the booth is right here. Matthew, welcome to theCUBE. >> Thank you very much, I'm glad to be here. >> So we're back in person. You're from Tennessee, we were chatting before you came on camera. It's great that be back to events. >> It's amazing, this is the first summit I've been to in what two, three years. >> It's awesome, we'll be at the AWS Summit in New York as well. A lot of developers and the big story this year is as developers look at cloud going, distributed computing you got on-premises, you got public cloud, you got the edge. Essentially the cloud operations is running everything, Dev sec Ops, everyone kind of sees that, you got containers, you got Kubernetes, you got cloud native. So the game is pretty much laid out, and the edge is with the action is. You guys are number one premier partner at SMB for edge. >> That's right. >> Tell us about what you guys doing at innovative and what you do. >> That's right, so I'm the director of solutions architecture. Me and my team are responsible for building out the solutions that are around especially the edge public cloud. For us edge is anything outside of an AWS availability zone. We are deploying that in countries that don't have AWS infrastructure in region. They don't have it-- >> Give an example. >> Example would be Panama. We have a customer there that needs to deploy some financial tech, data and compute is legally required to be in Panama but they love AWS, and they want to deploy AWS services in region. So they've taken EKS anywhere. We've put storage gateway and snowball in region, inside the country and they're running their FinTech on top of AWS services inside Panama. >> You know, what's interesting, Matthew is that we've been covering AWS since 2013 with theCUBE about their events, and we watched the progression. Andy Jassy was in charge and became the CEO. Now Adam Slepsky is in charge, but the edge has always been that thing they've been trying to avoid. I don't want to say trying to avoid. Of course Amazon listens to customers, they work backwards from the customers, we all know that. But the real issue is they're bread and butters, EC2 and S3. And then now they got tons of services, and the cloud is obviously successful, and we're seeing that. But the edge brings up a whole nother level. >> It does. >> Computing. >> It does. >> That's not set centralized in the public cloud. Now they got regions, so what is the issue with the edge? What's driving the behavior? Outpost came out as a reaction to competitive threats and also customer momentum around OT, operational technologies and IT merging. We see with the data at the edge, you got 5G, so it's pretty obvious, but there was a slow transition. What was the driver for the edge? What's the driver now for edge action for AWS? >> Data is the driver for the edge. Data has gravity, right? And it's pulling compute back to where the customer's generating that data and that's happening over and over again. You said it best Outpost was a reaction to a competitive situation. Whereas today we have over 15 AWS edge services and those are all reactions to things that customers need inside their data centers, on location or in the field like with media companies. >> Outpost is interesting, we always used to rip on theCUBE 'cause it's basically Amazon in a box pushed in the data center, running native, all this stuff. But now cloud native operations are becoming the standard. You're starting to see some standard, Deepak Singh's group is doing some amazing work with opensource, Raul's team on the AI side. Obviously you got Swam who's giving the keynote tomorrow. You got the big AI machine learning big part of that edge. Now you can say, okay, Outpost, is it relevant today? In other words, did Outpost do its job? 'Cause EKS anywhere seems to be getting a lot of momentum. You see local zones, the regions are kicking ass for Amazon. This edge piece is evolving. What's your take on EKS anywhere versus say Outpost? >> Yeah, I think Outpost did its job. It made customers that were looking at Outpost really consider, do I want to invest in this hardware? Do I want to have this Outpost in my data center? Do I want to manage this over the long term? A lot of those customers just transitioned to the public cloud. They went into AWS proper. Some of those customers stayed on prem because they did have use cases that were not a good fit for Outposts, they weren't a good fit in the customer's mind for the public AWS cloud inside an availability zone. Now what's happening is as AWS is pushing these services out and saying, we're going to meet you where you are with 5G. We're going to meet you where you are with wavelength. We're going to meet you where you are with EKS anywhere. I think it has really reduced the amount of times that we have conversations about Outposts and it's really increased, we can deploy fast. We don't have to spin up Outpost hardware. We can go deploy EKS anywhere in your VMware environment and it's increasing the speed of adoption for sure. >> All right so you guys are making a lot of good business decisions around managed cloud service. Innovative as that, you have the cloud advisory, the classic professional services for the specific edge piece and doing that outside of the availability zone and regions for AWS. Customers in these new areas that you're helping out are, they want cloud, they want to have modernization, modern applications. Obviously they got data machine learning and AI all part of that. What's the main product or gap that you're filling for AWS outside of their availability zones or their regions that you guys are delivering. What's the key? Is it they don't have a footprint? Is it that it's not big enough for them? What's the real gap, why are you so successful? >> So what customers want when they look towards the cloud is they want to focus on what's making them money as a business. They want to focus on their applications. They want to focus on their customers. So they look towards AWS cloud and say, AWS you take the infrastructure you take some of the higher layers and we'll focus on our revenue generating business but there's a gap there between infrastructure and revenue generating business that innovative slides into, we help manage the AWS environment. We help build out these things in local data centers for 32 plus year old company. We have traditional on-premises people that know about deploying hardware, that know about deploying VMware to host EKS anywhere. But we also have most of our company totally focused on the AWS cloud. So we're filling that gap in helping deploy these AWS services, manage them over the long term. So our customers can go to just primarily and totally focusing on their revenue generating business. >> So basically you guys are basically building AWS edges? >> Matthew: Correct. >> For companies. >> Matthew: Correct. >> Mainly because the needs are there, you got data, you got certain products, whether it's low latency type requirements, and then they still work with the regions, it's all tied together, is that how it works? >> And our customers, even the ones in the edge they also want us to build out the AWS environment inside the availability zone because we're always going to have a failback scenario. If we're going to deploy FinTech in the Caribbean we're going to talk about hurricanes. And we're going to talk about failing back into the AWS availability zones. So innovative is filling that gap across the board whether it be inside the AWS cloud or on the AWS edge. >> All right so I got to ask you on the, since you're at the edge in these areas, now, I won't say underserved but developing areas where you now have data and you have applications that are tapping into that requirement. It makes total sense, we're seeing that across the board. So it's not like it's an outlier, it's actually growing. >> Matthew: Yeah. >> There's also the crypto angle. You got the blockchain. Are you seeing any traction at the edge with blockchain? Because a lot of people are looking at the web three in these areas like Panama. And you mentioned FinTech in the islands, there are a lot of web three happening. What's your view on the web three world right now relative? >> We have some customers actually deploying crypto especially in the Caribbean. I keep bringing the Caribbean up, but it's top of my mind right now, we have customers that are deploying crypto. A lot of countries are choosing crypto to underlie parts of their central banks. So it's up and coming. I have some personal views that crypto is still searching for a use case. And I think it's searching a lot and we're there to help customers search for that use case. But crypto as a to technology lives really well on the AWS edge. And we're having more and more people talk to us about that. And ask for assistance in the infrastructure because they're developing new cryptocurrencies every day. It's not like they're deploying Ethereum or anything specific. They're actually developing new currencies and putting them out there on-- >> It's interesting. I mean, first of all we've been doing crypto for many, many years. We have our own little projects going on. But if you go talk to all the crypto people they say, look we do a smart concept. We use the blockchain. It's a lot of overhead. It's not really very technical already but it's a cultural shift but there's underserved use cases around use of money but they're all using the blockchain just for smart contracts, for instance, or certain transactions. And they go into Amazon for the database. They all, don't tell anyone we're using a centralized service. Well, what happened if decentralized? >> Yeah, and that's a conversation. >> It's a performance issue. >> Yeah and it's a cost issue and it's a development issue. So I think more and more as some of these currencies maybe come up, some of the smart contracts get into, they find their use cases. I think we'll start talking about how does that really live on AWS and what does it look like to build decentralized applications but with AWS hardware and services. >> All right so take me through a use case of a customer, Matthew, around the edge. So I'm a customer, pretend I'm a customer. Hey, we're in an underserved area. I want to modernize my business. And I got my developers that are totally peaked up on cloud but we've identified that it's just a lot of overhead latency issues. I need to have a local edge and serve my app. And I also want all the benefits of the cloud. So I want the modernization and I want to migrate to the cloud for all those cloud benefits and the goodness of the cloud. What's the answer? >> Yeah big thing is industrial manufacturing. That's one of the best use cases. Inside industrial manufacturing we can pull in many of the AWS edge services, we can bring in private 5G so that all the equipment inside that manufacturing plant can be hooked up. They don't have to pay huge overheads to deploy 5G. It's better than wifi for the industrial space. When we take computing down to that industrial area because we want to do pre-processing on the data. We want to gather some analytics. We deploy that with regular commercially available hardware, running VMware, and we deploy EKS anywhere on that. Inside of that manufacturing plant, we can do pre-processing on things coming out of the robotics depending on what we're manufacturing, right? And then we can take those refined analytics and for very low cost with maybe a little bit longer latency transmit those back to the AWS availability zone, the standard-- >> John: For data lake, or whatever. >> To the data lake, yeah data lake house, whatever it might be. And we can do additional data science on that once it gets to the AWS cloud. But a lot of that just in time business decisions, just in time manufacturing decisions can all take place on an AWS service or services inside that manufacturing plant. And that's one of the best use cases that we're seeing. >> And I think, I mean, we've been seeing this on theCUBE for many, many years, moving data around is very expensive. But also compute, going to the data that saves that cost on the data transfer but also on the benefits of the latency. So I have to ask you, by the way, that's standard best practice now for the folks watching, don't move the data unless you have to, but there's new things are developing. So I want to ask you what new are you seeing emerging once this new architecture's in place? Love that idea, localize everything, right at the edge, manufacturing, industrial, whatever the use case, retail, whatever it is. But now what does that change in the core cloud? There's a system element here, what's the new pattern? >> There's actually an organizational element as well. Because once you have to start making the decision do I put this compute at the point of use or do I put this compute in the cloud? Now you start thinking about where business decisions should be taking place. So not only are you changing your architecture you're actually changing your organization because you're thinking about a dichotomy you didn't have before. So now you say, okay, this can take place here. And maybe this decision can wait. And then how do I visualize that? >> By the way, it could be a bot too, doing the work for management. >> Yeah, exactly. >> You got observability going right. But you got to change the database architecture in the backs. There's new things developing. You've got more benefit. >> There are, there are. And we have more and more people that want to talk less about databases and want to talk more about data lakes because of this. They want to talk more about, customers are starting to talk about throwing away data. For the past maybe decade, it's been store everything. And one day we will have a data science team that we hire in our organization to do analytics on this decade of data. >> I mean, this is a great point. We don't have time to drill into, maybe we do another session on this but the one pattern we're seeing come of the past year is that throwing away data's bad. Even data lakes that so-called turn into data swamps. Actually is not the case. You look at Databrick, Snowflake and other successes out there. And even Time Series Data which may seem irrelevant efforts over actually matters when people start retraining their machine learning algorithms. >> Matthew: Yep. >> So as data becomes code, as we call it in our last showcase, we did, a whole event on this. The data's good in real time and in the lake. Because the iteration of the data feeds the machine learning training, things are getting better with the old data. So it's not throw it away. It's not just business benefits. There's all kinds of new scale. >> There are. And we have many customers that are running petabyte level. They're essentially data factories on premises, right? They're creating so much data and they're starting to say, okay we could analyze this in the cloud. We could transition it. We could move petabytes of data to the AWS cloud or we can run computational workloads on premises. We can really do some analytics on this data, transition those high level and sort of raw analytics back to AWS, run 'em through machine learning. And we don't have to transition 10, 12 petabytes of data into AWS. >> So I got to end the segment on a kind of a fun note. I was told to ask you about your personal background on premise architect, AWS cloud, and skydiving instructor. How does that all work together? What does this mean? You jumped out a plane and got a job. You got a customer to jump out? >> Kind of, so I was-- >> You jumped out? >> I was teaching skydiving before I started in the cloud space, this was 13, 14 years ago. I was a, I still am a skydiving instructor. I was teaching skydiving. And I heard out of the corner of my ear a guy that owned an MSP that was lamenting about storing data and how his customers are working. And he can't find enough people to operate all these workloads. So I walked over and said, hey, this is what I went to school for. I'd love to, I was living in a tent in the woods, teaching skydiving. I was like, I'd love to not live in a tent in the woods. So I started and the first day there we had a discussion, EC2 had just come out and-- >> This is amazing. >> Yeah and so we had this discussion, we should start moving customers here. And that totally revolutionized that business, that led to, that guy actually still owns skydiving airport. But through all of that and through being an on premises migrated me and myself, my career into the cloud. And now it feels like almost looking back and saying, now let's take what we learned in the cloud and apply those lessons in those services to on premises. >> It's such a great story, is going to, the whole growth mindset, pack your own parachute. >> Matthew: Exactly. >> The cloud in the early days was pretty much will the chute open? >> Matthew: Yeah. >> It was pretty much you had to roll your own cloud at that time. And so, you jump out a plane you got to make sure that parachute is going to open. >> And so was Kubernetes by the way, 2015 or so when that was coming out, it was, I mean, it was still, maybe it does still feel like that to some people. But it was the same kind of feeling that we had in the early days of AWS, the same feeling we have when-- >> It's pretty much now with you guys, it's more like a tandem jump. But a lot of this cutting edge stuff is like jumping out of an airplane. You got the right equipment. You got to do the right things. >> Exactly. >> John: Matthew, thanks for coming on theCUBE. Really appreciate it. Absolutely great conversation. >> Thanks for having me, thank you. >> Okay theCUBE's here live in San Francisco for AWS Summit. I'm John Furrier, host of theCUBE. We'll be at AWS Summit in New York coming up in the summer as well. Look up for that. Look at this calendar for all theCUBE action at theCUBE.net. We'll be right back with our next segment after this break. (upbeat music)