>> Welcome back to Los Angeles. TheCUBE is live. I can't say that enough. The cube is live. We're at KubeCon Cloud Native Con 21. We've been here all day yesterday, and today and tomorrow I'm talking with lots of guests, really uncovering what's going on in the world of Kubernetes. Lisa Martin, here with Dave Nicholson. We've got some folks. Next we're going to be talking about a customer use case, which is always one of my favorite things to talk about. Please welcome Micah Coletti, the principal platform engineer at CHG healthcare, and Venkat Ramakrishnan VP of products from Portworx by Pure Storage, guys welcome to the program. >> Thank you. >> Happy to be here. >> Yeah. So Micah, first of all, let's go ahead and start with you. Give the audience an overview of CHG healthcare. >> Yeah. So CHG healthcare, we're a staffing company. So we try like a little companion. So our clients are doctors and hospitals, so we help staff hospitals with temporary doctors or even permanent placing. So we deal with a lot of doctors, a lot of nursing and we're a combination of multiple companies. So CHG is the parent. So, and yeah, we're known in the industry as one of the leaders in this field and providing hospitals with high quality doctors and nurses. And, you know, our customer service is like number one, and one of the things our CEO is really focused on is now how do we make that more digital? How do we provide that same level of quality of service, but a digital experience as rich for her. >> I can imagine it was a massive need for that in the last 18 months alone. >> COVID definitely really raised that awareness up for us and the importance of that digital experience and that we need to be out there in the digital market. >> Absolutely. So you're a customer port works by pure storage, we're going to get into that, but then Venkat talk to us about what's going on, the acquisition of port works by pure storage was about a year ago. Talk to us about your VP of products what's going on. >> Yeah, I mean, you know, first of all, I think I could not say how much of a great fit for a Portworx will be part of pure storage, it's, pure itself is a very fast moving, large startup that's a dominant leader in the flash and data center space, and, you know, pure recognizes the fact that Kubernetes is the new operating system of the cloud is not how, you know, it's kind of virtualizing the cloud itself, and there's a, you know, a big burgeoning need for data management and Kubernetes and how you can kind of orchestrate workloads between your on-prem data centers and the cloud and back. So Portworx fits right into the story as complete vision of data management for our customers, and it's been phenomenal. Our business has grown as part of being part of a pure, and you know, we're looking at launching some new products as well, and it's all exciting times. >> So you must've been pretty delighted to be acquired as a startup by essentially a startup because, because although pure has reached significant milestones in the storage business and is a leader in flash storage still that that startup mindset is absolutely unique. That's not, that's not the same as being acquired by a company that's been around for a hundred years seeking to revitalize itself. >> Absolutely. >> Can you talk a little bit about that aspect? >> Yeah, So I think, you know, purist culture is a highly innovation-driven and it's a very open, flat culture, right? I mean, it's, everybody in pure is accessible. It can easily have a composition with folks and everybody has his learning mindset and Portworx is and has always been the same way. Right? So when you put these teams together, if we can create wonders, I mean, we right after the acquisition, just within a few months, we announced an integrated solution that portworx orchestrates volumes and file shares in pure splash products and then delivers as an integrated solution for our customers, and pure has a phenomenal cloud-based monitoring and management system called pure one that we integrated well into. Now, we're bringing the power of all of the observability that pure's customers are used to for all of the corporate customers, and I've been super happy, you know, delegating that capability to our customers and our customers are delighted. Now they can have a complete view all the way from Kubernetes app to the flash. and I don't think any one company in the planet can even plan they can do that. >> I think it's fair to acknowledge that pure one was observability before observability was a word that everyone used regularly. >> Yep. >> Sounds very interesting. >> Micah Talk to us about, obviously you are a customer. CHG is a customer of Portworx now Portworx by Pure Storage. Talk to us about the use case. What, what was the compellent? Was there a compelling event and from a storage perspective that led you to Portworx in the first place. >> So we beat, they began this, our CEO base came to the vision, we need to have a digital presence we need enhances. and this was even before COVID. So they brought me on board and my, my manager read glossary. We basically had this task to, how are we going to get out into the cloud? How are we going to make that happen? And we chose to follow a very much a cloud native strategy and the platform of choice, I mean, it just made sense with Kubernetes. And so when we were looking at Kubernetes, we were starting to figure out how we're doing. We knew that data is going to be a big factor. You know, being a, provide data. We're very much focused on an event driven. We're really pushing to event driven architecture. So we leverage Kafka on top of Kubernetes, but at the time we were actually leveraging Kafka with a MSK down, out in AWS, and that was just a huge cost to us. So I came on board, I had experienced with Portworx, a prior company before that, and I basically said, we need to figure out a great storage relay overlay. and the only way to do is we got to have high performance storage, we've got to have secure. We got to be able to backup and recover that storage. And the Portworx was the right match. And that allowed us to have a very smooth transition off of MSK onto Kubernetes saving us a significant amount of money per month, and just leverage that already existing hardware that our existing compute memory and just, and the, and move right to Portworx. >> Leveraging your existing investments. >> Exactly. >> Which is key, >> Very key, very key so. >> So how common are the challenges that when you guys came together with CHG, how common are the challenges? >> It's actually a, that's a great question. You know, this is, you know, I'll tell you the challenges that Micah and his team are running into is what we see a lot in the industry where people pay a ton of money, you know to other vendors are, you know, especially in some cases use some cloud native services, but they want to have control over the data. They want to control the cost and they want higher performance and they want to have, you know, there's also governance and regulatory things that they need to control better. So they want to kind of bring these services and have more control over them. Right? So now we will work very well with all of our partners, including the cloud providers, as well as, you know, on-prem and server vendors and everybody, but different customers have different kinds of needs. And Portworx gives them that flexibility. If you are a customer who want, you know, have a lot of control over your applications, the performance, the latency, and want to control costs very well and leverage your existing investments Portworx can deliver that for you in your data center. Right now, you can integrate that with pure slash and you get a complete solution, or you want to run it in cloud, and you still want to have leverage the agility of the cloud and scale Portworx delivers a solution for you as well. So it kind of not only protects their investment its future proves their architecture, you get future proving your architecture completely. So if you want to tear the cloud or burst the cloud, you have a great solution that you can continue to leverage >> Micah, when you hear future-proof and I'm a marketer. So I always go, I love to know what it means to different people. What does that mean to you in your environment? >> My environment. So a future-proof means like one of the things we've been addressing lately, that's just a real big challenge. And I'm sure it's a challenge in the industry, especially the Q and A's is upgrading our clusters. The ability to actually maintain a consistent flow with how fast Kubernetes is growing, you know, they're, they they're out. I think he cast, we leverage the cast. So it's like 121 or 122 now, and that effort to upgrade a cluster, it can be a daunting one. With Portworx, we actually were able to make that to where we could actually spin up a brand new cluster. And with Portworx shift, all our applications, services, data migrated completely over, Portworx handles all of that for us and stand up that new cluster in, in less than a day. And that effort, I mean, it would take us a week, two weeks to do so, not even man hours and time spent there, but just the reliability of being able to do that in the cost, you know, instead of standing up a new cluster and configuring it and doing all that and spending all that time, we can just really, we move to what we call blue green cut-over strategy. And Portworx is an essential piece of that. >> So Venkat, is it fair to say that there are a variety of ways that people approach Portworx from a value perspective in terms of, I know that one area that you are particularly good in is the area of backups in this environment, but then you get data management and there's a third kind of vector there. What is the third vector? >> As all of the data services, >> Data services, >> Yeah Like for example, deep database as a service on any Kubernetes cluster feed on your cloud or your on-prem data centers. >> Which data, what kind of databases are you talking about? >> I mean we're talking about anything from Reddit Kafka, Post-stress my sequel console, we are supporting. We just announced something called a Portworx Data Services Offering that essentially delivers all these databases as a service on any Kubernetes cluster that a customer can point to and lets them kind of get the automated management of the database from day one to day three, the entire life cycle, you know, through regular Kubernetes, scoop cuddle experience through APIs and SDKs and a nice slick UI that they can, you know, that's, role-based access control and all of that, that they can completely control their data and their applications through it. And you know, that's the third vector of Portworx office. >> Micah a question for you. So Portworx has been a part of pure storage? You've known it since obviously for several years before you were at CHG, you brought it to CHG. You now know it a year into being acquired by a fast paced startup. Talk to me about the relationship and some of the benefits that you're getting with Portworx as a part of pure storage? >> Well, I mean, one of the things I, you know, when I heard about the acquisition, my first thing was, I was a little bit concerned is that relationship going to change? And when we were acquiring, when we were looking at adopting Portworx, one thing I would tell my management is Portworx is not just a vendor that wants to throw a solution on you and provide some capability. They're a partner. They want to partner with you and your success in your journey and this whole cloud native journey to provide this rich digital experience in the, for not only our platform engineering team, but our Dev teams, but also be able to really accelerate the development of our services. So we can provide that digital portal for our end users. And that didn't change. If anything, that it accelerated that relationship did not change. You know, I came to Venkat with an issue. We just we're, we're dealing with, he immediately got someone on a phone call with me. And so that has not changed. So it's really exciting to see that now that they've been acquired, that they still are very much invested in the success of their customers and making sure we're successful. You know, it's not all of a sudden. I was worried I was going to have to do a whole different support PA process, and it was going to go into a black hole. Didn't happen. They still are very much involved with their customers. >> It's sounds kind of Venkat similar to what you talked about with the cultural alignment. I've known here for a long time and they're very customer centric sounds like one of the areas in which there was a very strong alignment with Portworx >> Absolutely. and Portworx has always taken pride in being customer first company. Our founders are heavily customer focused. You know, they are aligned. They want, they have always aligned. our portraits business to our customers' needs. Now Pure is a company that's maniacally focused on customers, right? I mean, that's all in a pure pounder cars and everybody cared about. And so, you know, bringing these companies together and being part of the Pure team, I kind of see how, how synergistic it is. And, you know, we have, you know, that has enabled us to serve our customer's customers even better than before. >> So I'm curious about the two of you personally, in terms of your, your histories, I'm going to assume that you didn't both just bounce out of high school into the world of Kubernetes, right? So like Lisa and I you're spanning the generations between the world of say virtualization based on x86 architecture, virtualization, where you're not, you don't have microservices, you have a full blown operating system that you're working with. Kind of talk about, you know, Micah with you first talk about what that's been like navigating that change. We were in the midst of that. Do you have advice for others that are navigating that change? >> Don't be afraid of it. You know, a lot of people want to, you know, I call it we're moving from where we're name me. We still have cats and dogs. They have a name that the VMs either whether or not they're physical boxes or their VMs to where it's more like, he'd say cattle, you know, it's like we don't own the OOS and not to be afraid of afraid of that, because change is really good. You know, the ability for me to not have to worry about patching and operating system, it's huge, you know, where I can rely on someone like EKS and, and the version and allow them to, if a CV comes out, they let me know. I go and I use their tools to be able to upgrade. So I don't have to literally worry about owning that OOS and containers as the same thing. You know, you, you know, it's all about being fault-tolerant right. And being able to be changed or where, you know, you can actually roll out a new version of a container, a base image with a lot of ease without having to go and patch a bunch of servers. I mean, patch night was hell and sorry if I could say that, but it was a nightmare, you know, but this whole world has just been a game changer with that. >> So Venkat from your perspective, you were coming at it, going into a startup, looking at the landscape in the future and seeing opportunity. What what's that been like for you? I guess the question for you is more something, Lisa and I talk about this concept of peak Kubernetes, where are we in the wave? Is this just, is this just the beginning? Are we in the thick of it? >> I think I would say we're kind of transitioning from early adopters, early majority phase in the whole, you know, crossing the chasm analogy, right? So I would say we're still early stages of this big wave. That's going to transform how infrastructure is built. Apps are apps are built and managed and run in production. I think some of the pieces, the key pieces are falling in place and maturing. There are some other pieces like observability and security, you know, kind of edge use cases need to be, you know, they're kind of going to get a lot more mature and you'll see that the cloud, as we know today, and the apps, as we know today, they're going to be radically different. And you know, if you're not building your apps and your business on this modern platform, on this modern infrastructure, you're going to be left behind. You know, I, my wife's birthday was a couple of days ago. I was telling the story to my couple of friends is that I, I used another flowers delivery website. They miss delivering the flowers on the same day, right. So they told me all kinds of excuses. Then I just went and looked up a, you know, like door dash, which is delivers, you know, and then, you know, like your food, but there's also flower delivery and door dash and I don't do I door dash flowers to her, and I can track the flower delivery all the way she did not need them, but my kids love the chocolates though. Right. So, and you know, the case in point is that you cannot be in a building, a modern business without leveraging the model tool chain and modern tool chain and how the business is going to be delivered at that thing is going to be changing dramatically. And those kinds of customer experience, if you don't deliver, you're not going to be successful in business. And Kubernetes is the fundamental technology that enables this containers is a fundamental piece of technology that enables building new businesses, you know, modernizing existing businesses. And the 5G is going to be, there's going to be new innovations. It's going to get unleashed. And again, Kubernetes and containers enable us to leverage those. And so we're still scratching the surface on this. It's big. Now, it's going to be much, much bigger, you know, as, as we go into the next couple of years. >> Speaking, scratching the surface, Micah, take us out in the last 30 seconds or so with where CHG healthcare is on institutional transformation, how is Portworx facilitating that? >> So we're, we're right in the thick of it. I mean, we are, we still have what we call the legacy. We're working on getting those, but I mean, we're really moving forward to provide that rich experience, especially with event driven platforms like Kafka and Kubernetes and partnering with Portworx is one of the key things for us with that. And AWS along with that. But we're a, and I remember I heard a talk and I can't, I can't remember her name, but he talked about how, how Pure Kubernetes is sort of like the 56K modem, right. You're hearing it and see, but it's got to get to the point where it's just there. It's just the high-speed internet and Kelsey Hightower. That's great. But yeah, and I really liked that because that's true, you know, and that's where we are. We're all in that transition where we're still early, it's still at 50. So you still want to hear note, you still want to do cube CTL. You want to learn it the hard way and do all that fun stuff. But eventually it's going to be where it's just, it's just there. And it's running everything like 5G. I mean, stripped down doing micro, you know, Kate's things like that. You know, we're going to see it in a lot of other areas and just periphery and really accelerate the industry in compute and memory and storage, and. >> Yeah, a lot of acceleration. Guys thank you. This has been a really interesting session. I always love digging into customer use cases. How CHG is really driving its evolution with Portworx. Venkat, thanks for sharing with us, What's going on with Portworx a year after the acquisition. It sounds like all good stuff. >> Thank you. Thanks for having us. >> Pleasure. All right. For Dave Nicholson, I'm Lisa Martin. You're watching theCUBE live from Los Angeles. This is our coverage of KubeCon Cloud Native Con 21.

>>Welcome back to Los Angeles, Lisa Martin and Dave Nicholson here on day three of the cubes, coverage of coop con and cloud native con north America, 21, Dave, we've had a lot of great conversations. The last three days it's been jam packed. Yes, it has been. And yes, it has been fantastic. And it's been live. Did we mention that it's inline live in Los Angeles and we're very pleased to welcome one of our alumni back to the program. David Stephanie is here. The CEO of Trulio David. Welcome back. It's good to see you. >>Thanks for having me. It's good to be here. Isn't it great to be in person? Oh man. It's been a reunion. >>It hasn't been a reunion and they have Ubered been talking about these great little, have you seen these wristbands that they have? I actually asked >>For two, cause I'm a big hugger, so >>Excellent. So, so here we are day three of coupon. That's actually probably day five, our third day of coverage. I'm losing track to it's Friday. I know that, that I can tell you, you guys announced two dot five a couple of weeks ago. Tell us what's in that. What's exciting. Before we crack open Twilio, uh, choy. >>Sure, sure. Well, it's been exciting to be here. Look, the theme right of resiliency realize has been it's right up our wheelhouse, right? To signal that more people are getting into production type of environments. More people require data protection for cloud native applications, right? And, uh, there's two dot five releases. It is as an answer to what we're seeing in the market. It really is centered predominantly around, uh, ransomware protection. And uh, you know, for us, when we look at this, I I've done a lot of work in, in cybersecurity, my career. And we took a hard look about a year ago around this area. How do we do this? How do we participate? How do we protect and help people recover? Because recovery that's part of the security conversation. You can talk about all the other things, but recovery is just as important. And we look at, uh, everything from a zero trust architecture that we provide now to adhering, to NIST standards and framework that's everything from immutability. Uh, so you can't touch the backups now, right? Uh, th that's fine to encryption, right? We'll encrypt from the application all the way to that, to the storage repository. And we'll leverage Keem in that system. So it's kind of like Bitcoin, right? You need a key to get your coin. You as an end-user only have your key to your data alone. And that's it. So all these things become more and more important as we adopt more cloud native technology. And >>As the threat landscape changes dramatically. >>Oh yeah. I got to tell you right. Every time we, you, you publish an application into another cloud, it's a new vector, right? So now I'm living in a multi-cloud world where multiple applications in my data now lives, right? So people are trying to attack backups through, uh, consoles and the ministry of consoles to the actual back of themselves. So new vectors, new problems need new solutions. >>And you mentioned, you mentioned something, you, you, you asked the question, how do we participate? And we are here at KU con uh, w uh, cloud native foundation. So what about, what's your connection to the open source community and efforts there? How do you participate in that? >>Yeah, so it's a really great question because, you know, uh, we are a closed source solution that focuses all of our efforts on the open source community and protecting cloud native applications. Our roots have been protecting cloud native applications since 2013, 2014, and with a lot of very large logos. And, um, you know, through time there are open source projects that do emerge, you know, in this community. And for example, Valero is an open source data protection platform, um, for all of its goodness, as a, as a community-based project, they're also deficiencies, right? So Valero in itself is, uh, focuses only on label based applications. It doesn't really scale. It doesn't have a UI it's really CLI driven, which is good for some people and it's free. But you know, if you need to really talk about an enterprise grade platform, this is where we pick up, you know, we, in our last release, we gave you the ability to capture your Valero based backups. And now you want to be an adult with an enterprise caliber, you know, backup solution and continue to protect your environment and have compliance and governance needs all satisfied. That's where, that's where we really stand out. >>Well, when you're talking to customers in any industry, what are the things that you talk about in terms of relief, categorizing the key differentiators that really make Trulia stand out above the competition? >>Yeah. Cause there, there a bunch of, they're a bunch of great competitors out there. There's no doubt about it. A lot of the legacy folks that you do see perhaps on those show floor, they do tuck in Valero and under the, under the covers, they can check a box or you can set aside some customer needs some of the pure play people that, that we do see out there, great solutions too. But really where we shine is, you know, we are the most flexible agnostic solution that there is in this market. And we've had people like red hat and Susa and verandas, digital ocean and HPS morale. And the list goes on, certify, say, Trulio is the solution of choice. And now no matter where you are in this journey or who you're using, we have your back. So there's a lot of flexibility. There we are complete storage agnostic. >>We are cloud agnostic in going back to how you want to build our architecture application. People are in various phases in their, in their journey. A lot of times, many moons ago, you may have started with just a label based application. Then you have another department that has a new technique and they want to use helm, or you may be adopting open shift and you're using operators to us. It doesn't matter. You have peace of mind. So whether you have, you have to protect multiple departments or you as an end user, as one single tenant are using various techniques, we'll discover or protect and we can move forward. >>So if you looked at, if you look at it from a workload basis, um, and you look at your customers are the workloads that you're protecting. What's, what's the mix of what you think of as legacy virtualized things versus containerized things. And then, and then, and then the other kind of follow on to that is, um, are you seeing a lot of modernization and migration or are you seeing people leave the legacy things alone and then develop net new in sort of separate silos? >>Yeah. So that's a great question. And I, to tell you the answer varies, that's, that's the honest answer, right? You end up having, you may have a group or a CIO that says, look, your CTO says, we're moving to this new architecture. The water's great, bring your applications in. And so either it's, we're going to lift and shift an application and then start to break it apart over time and develop microservices, or we're gonna start net new. And it really does run, run the gambit. And so, you know, as we look at, for some of those people, they have peace of mind that they can bring their two on applications in and we can recover. And for some people that say, look, I'm going to start brand new, and these are gonna be stateless applications. Um, we've seen this story before, right? Our, our, uh, uh, I joke around, it's kinda like the movie Groundhog's day. >>Uh, you know, we, we started many moons ago within the OpenStack world and we started with stateless to stateful. Always, always, always finds a way, but for the stateless people, um, when you start thinking about security, I've had conversations with CSOs around the world who say, I'm going to publish a stainless application. What I'm concerned about things like drift, you know, what's happening in runtime may be completely different than what I intended. So now we give you the ability to capture that runtime state compare. The two things identify what's changed. If you don't like what you see, and you can take that point in time recovery into a sandbox and forensically take it apart. You know, one of our superpowers, if you will, is the, our point in time, backups are all in an open format. Everyone else has proprietary Schemos. So the benefit of an open format is you have the ability to leverage a lot of third party tooling. So take a point in time, run scanners across it. And it, God forbid Trulio goes away. You still have access and you can recreate a point in time. So when you start thinking about compliance, heavy environments, think about telcos, right? Or financial institutions. They have to keep things for 15 years, right? Technologies change, architectures change. You can't have that lock-in >>So we continue to thrive. And on that front, one of the marketing terms that we hear a lot, and I want to get your opinion on this as a feature proofing, how do you, what does, what does it mean to you and Trillium and how do you enable that for organizations, like you said, for the FSI is I have to keep data for 15 years and other industries that have to keep it for maybe even longer. >>I mean, right. The future proof, uh, you know, terminology, that's part of our mantra actually, when I talked about, you know, a superpower being as agnostic and flexible as can be right, as long as you adhere to standards, right? The standards that are out here, we have that agnostic play. And then again, not just capturing an applications, metadata data, but that open format, right? Giving you that open capability to unpack something. So you're not, there is no, there is no vendor lock-in with us at all. So all these things play a part into, into future-proofing yourself. And because we live and breathe cloud native applications, you know, it's not just Kubernetes right? Over the course of time, there'll be other things, right. You're going to see mixed workloads too. They're gonna be VM based in the cloud and container based in the cloud and server lists as well. But you, as long as you have that framework to continuously build off of it, that's, that's where we go. You know, uh, it shouldn't matter where your application lives, right? At the end of the day, we will protect the application and its data. It can live anywhere. So conversations around multi-cloud change, we start to think and talk across cloud, right? The ability to move your application, your data, wherever it, wherever it needs to be to. >>Well, you talked about recoverability and that is the whole point of backing up video. You have to be able to recover something that we've seen in the last 18, 19 months. Anyone can backup >>Data. >>That's right. That's right. If you can't recover it, or if you can't recover it in time. Yeah. We're talking like going on a business potential and we've seen the massive changes in the security landscape in the last 18, 19 months ransomware. I was looking at some, some cybersecurity data that showed that just in the first half of this calendar year, January one to June 30, 20, 21, ransomware was up nearly 11 X DDoS attacks are up. We've got this remote workforce. That's going to probably persist for a while. So the ability to recover data from not if we get hit by ransomware, but when we get hit by ransomware is >>When you're, you're absolutely right. And, and, and to your plate anyway. So anyone can back up anything. When you look at it, it's at its highest form. We talk about point time where you orchestration, right. Backup is a use case. Dr. Is a use case, right? How do you, reorchestrate something that's complex, right? The containers, these applications in the cloud native space, there are morphous, they're living things, right? The metadata is different from one day to the next, the data itself is different from when one day the net to the next. So that's, what's so great about Trillium. It's such an elegant solution. It allows your, reorchestrate a point in time when and where you need it. So yes. You have to be able to recover. Yes. It's not a matter of if, but when. Right. And that's why recovery is part of that security conversation. Um, you know, I I've seen insurance companies, right? They want to provide insurance for ransomware. Well, you're gonna have enough attacks where they don't want to provide that insurance anymore. It costs too much. The investment that you make with, with Trulio will save you so much more money down the road. Right. Uh, who's our product manager actually gave a talk about that yesterday and the economics were really interesting. >>Hmm. So how has the recovery methodology who participates in that changed over time? As, as we, you know, as we are in this world of developer operators who take on greater responsibility for infrastructure things. Yeah. Who's, who's responsible for backup and recovery today and how, how has that changed >>Everyone? Everyone's responsible. So, you know, we rewind however many years, right? And it used predominantly CIS admin that was in charge of backup administrator, but a ticket in your backup administrator, right. Cloud native space and application lifecycle management is a team sport. Security is a team sport. It's a holistic approach. Right? So when you think about the, the team that you put out on the field, whether your DevOps, your SRE dev sec ops it ops, you're all going to have a need for point in time, we orchestration for various things and the term may not be backup. Right? It's something else. And maybe for test dev purposes, maybe for forensic purposes, maybe for Dr. Right. So I say it's a team sport and security as a holistic thing that everyone has to get on board with >>The three orchestration is exactly the right way to talk about absolute these processes. It's not just recovery, you're rebuilding >>Yeah. A complex environment. It's always changing. >>That's one of the guarantees. It's always going to be changing >>That much. >>Can you give us a, leave us with a customer example that you think really articulates the value of what Trulio delivers? >>Yeah. So it's interesting. I won't say who the customer is, but I'll tell you it's in the defense agency, it's a defense agency. Uh, they have developers all over the place. Uh, they need self-service capabilities for the tenants to mind their own backups. So you don't need to contact someone, right. They can build, they have one >>Dashboard, single pane of glass or truth to manage all their Corinthians applications. And it gives them that infrastructure to progress whether your dev ops or not your it ops, uh, this, this group has rolled it out across the nation and they're using in their work with very sensitive environments. So now we have they're back. And what are some of the big business outcomes that they're achieving already? >>The big business outcomes? Well, so operational efficiencies are definitely first and foremost, right? Empowering the end user with more tools, right? Because we've seen this shift left and people talking about dev ops, right. So how do I empower them to do more? So I see that operational efficiency, the recoverability aspect, God forbid, something goes wrong. How do you, how do you do that in the cost of that? Um, and then also, um, being native to the environment, the Trillium solution is built for Kubernetes. It is built on go. It is a Qubit stateless Kubernetes application. So you have to have seamless integration into these environments. And then going back to what I was saying before, knowing peace of mind, the credibility aspect, that it is blessed by, you know, red hat and suicide Mirandas and all these other, other folks in the field, um, that you can guarantee it's going to work >>Well, that helps to give your customers the confidence that there, and that confidence might sound trivial. It's not, especially when we're talking about security, it's not at all that, that's a, that's a big business outcome for you guys. When a customer says, I'm confident I have the right solution, we're going to be able to recover when things happen, we try, we fully trust in the solution that we're, >>And we'll bring more into production faster that helps everyone out here too. Right? It feels good. You have that credibility. You have that assurance that I can move faster and I can move into different clouds faster. And that's, we're gonna continue to put, we're gonna continue to push the envelope there. You know, coming a, as we look into, you know, going forward, we're going to come out with other capabilities. That's going to continue to differentiate ourselves from, from folks. Uh, we'll, we'll talk about in time, the ability to propagate data across multiple clouds simultaneously. So making RTOs look at the split seconds and minutes. And so I hope that we can have that conversation next time we were together, because it's really exciting. >>Any, any CTA that you want to give to the audience, any, any, uh, like upcoming or recent webinars that you think they would be really benefit from? >>I guess one thing I put out there is that, um, I understand that people need to continuously learn. There is a skillset hole in, in this market. We can, we understand that, you know, and people look to us as not just a vendor, but a partner. And a lot of the questions that we do get are how do I do this? Or how do I do that? Engage us, ask us to consume our product is really, really easy. You can download from the website or go to an, you know, red hats operator hub, or go to the marketplace over at Susa, and let's begin to begin and we're here to help. And so reach out, right? We want everyone to be successful. >>Awesome. trillium.io. David, thank you for joining us. This has been an exciting conversation. Good >>To see you all. >>Likewise. Good to see you in person take care. We look forward to the next time we see you when unpacking what other great things are going on on Trulia. We appreciate your >>Time. Thank you so much. Good to be here >>For David's fie and David Nicholson, the two Davids I'm going to sandwich. I'm Lisa Martin, you we're coming to you live from Los Angeles. This is Q con cloud native con north America, 2021. Stick around our next guest joins us momentarily.

>>I want to welcome back to the cubes coverage. We're here at another event in person I'm John furrier, host of the cube. We've got to CNCF coop con cloud native con for in-person 2021. And we're back. It's a hybrid event and we're streaming lives on all channels, as well as all the folks watching a great guest kicking off the show here from the co-chairs from cataract coast. Is that right? Danielle Cook. Who's the vice president at Fairwinds and John Foreman director at Accenture. Thanks for coming on your co-chair. Your third co-chair is not here, but you guys are here to talk about the cloud maturity model. Pretty mature funding is flowing tons of announcements. We're going to have a startup on $200 million. They're announcing in funding and observability of all of all hot spaces. Um, so the maturity is it's the journey in the cloud native space now is crossed over to mainstream. That's the we've been telling that story for a couple of years. Now, you guys have been working on this. Tell us about the cloud maturity model you guys worked on. >>So we got together earlier this year because we, um, four of us had been working on maturity models. So Simon Forester, who is one of the co-chairs, who isn't here, he had worked on a maturity model that looked at your legacy journey, all the way to cloud native, um, myself, I had been part of the Fairwinds team working on the Kubernetes maturity model. So, and then, um, we have Robbie, who's not here. And John Foreman, who we all got together, they had worked on a maturity model and we put it together and I've been working since February to go, what is cloud native maturity and what are the stages you need to go through to achieve maturity. So put this together and now we have this great model that people can use to take them from. I have no idea what cloud native is to the steps they can take to actually be a mature organization. >>And, you know, you've made it when you have a book here. So just hold that up to the camera real quick. So you can see it. It's very much in spirit of the community, but in all seriousness, it book's great, but this is a real need. What was the pain point? What was jumping out at you guys on the problem? Was it just where people like trying to get more cloud native, they want to go move faster. It was a confusing, what were the problems you solve in? >>Well, and if anything is, if we start at the beginning, right, there was during the cloud journey DevSecOps and the Kootenays being a thing that then there's journeys to DevSecOps tributaries as well. But everything is leading to cloud native. It's about the journey to cloud native. So everybody, you know, we're taught to go John, the ecosystem's an eyesore man. If I look at, you know, landscape, >>The whole map I >>Need, it's just like in trend map, it's just so confusing what we do. So every time we go to, I revert the wheel and I get them from zero to hero. So we just put together a model instead that we can re reuse yeah. As a good reference architecture. So from that is a primary, how we built because the native trademark you have with us today. So it's a five scale model from one to five what's twice today, or how to, to, you know, what our job is getting to a five where they could optimize a really rocket rolling. >>You know, it's interesting. I love these inflection points and, you know, being a student of history and the tech business there's moments where things are the new thing, and they're really truly new things like first-time operationalized dev ops. I mean the hardcore dev ops or early adopters we've been doing that, you know, we know that, but now mainstream, like, okay, this is a real disruption in a positive way. So the transformation is happening and it's new, new roles, new, new workflows, new, uh, team formations. So there's a, it's complicated in the sense of getting it up and running so I can see the need. How can you guys share your data on where people are? Because now you have more data coming in, you have more people doing dev ops, more cloud native development, and you mentioned security shepherds shifting left. Where's the data tell you, is it, as you said, people are more like a two or more. What's the, what's the data say? >>So we've had, so part of pulling this model together was your experience at Accenture, helping clients, the Fairwinds, um, experience, helping people manage Kubernetes. And so it's from out dozens of clusters that people have managed going, okay, where are people? And they don't even know where they are. So if we provide the guidelines from them, they can read it and go, oh, I am at about two. So the data is actually anecdotal from our experiences at our different companies. Um, but we, you know, we we've made it so that you can self identify, but we've also recognized that you might be at stage two for one application, but five for another application. So just because you're on this journey, doesn't mean everything is in, >>It's not boiler plate. It's really unique to every enterprise because they everyone's different >>Journey. Put you in journey with these things. A big part of this also torn apart one to five, your clients wants to in denial, you know? So, so Mr. CX level, you are level two. We are not, there's no way we would deal with this stuff for years. You've got to be a five. No, sorry. You're too. >>So >>There's use denial also about this. People think they do a cloud-native director rolling, and I'm looking at what they're doing and go, okay, do you do workups security? And they go, what's that? I go, exactly. So we really need to peel back the onion, start from seed year out and we need to be >>All right. So I want to ask more about the, um, the process and how that relates to the themes are involved. What are some of the themes around the maturity model that you guys can share that you see that people can look at and say, how do I self identify? What's the process will come to expect? >>Well, one of the things we did when we were putting it together was we realized that there were themes coming out amongst the maturity model itself. So we realized there's a whole people layer. There's a whole policy layer process and technology. So this maturity model does not just look at, Hey, this is the tech you need to do. It looks at how you introduce cloud native to your organization. How do you take the people along with it? What policies you need to put in place the process. So we did that first and foremost, but one of the things that was super important to all of us was that security was ever present throughout it. Because as everything is shifting left, you need to be looking at security from day one and considering how it's going to happen and roll out from your developers all the way to your compliance people. Um, it's super important. And one of the themes throughout. >>So, so it would be safe to say, then that security was a catalyst for the maturity models because you gotta be mature. I mean, security, you don't fool around security. >>About the last year when I created the program for, since I worked with Cheryl Holland, from CCF, we put together the community certification, her special program. I saw a need where security was a big gap in communities. Nobody knew anything about it. They wanted to use the old rack and stack ways of doing it. They wanted to use their tray micro tombs from yesteryear, and that doesn't work anymore. You need a new set of tools for Kubernetes. It's the upgrade system. It's different way of doing things. So that knowledge is critical. So I think you're part of this again, on this journey was getting certifications out there for people to understand how to do better. Now, the next phase of that now it's how do we put all these pieces together and built this roadmap? >>Well, it's a great group. You guys have the working groups hard to pronounce the name, but, uh, it's a great effort because one of the things I'm hearing and we've been reporting this one, the Cubans looking angle is the modern software developers want speed, and they don't want to wait for the old slow groups now and security, and it are viewed as blockers and like slow things down. And so you start to see a trend where those groups could provide policy and then start putting, feeding up, uh, data models that allow the developers in real time to do their coding, to shift left and to be efficient and move on and code not be waiting for weeks or days >>Comes to play. So today is the age of Caleb's right now, get up this emerging we're only to have now where everything is code policies, code, securities, code policies, cookie figures, code. That is the place for, and then again, walk a fusion more need for a cargo office. >>Okay. What's your thoughts on that? >>So I think what's really important is enabling service ownership, right? You need the developers to be able to do security, see policy, see it live and make sure that, you know, you're not your configuration, isn't stopping the build or getting into production. So, you know, we made sure that was part of the maturity model. Like you need to be looking continuous scanning throughout checking security checking policy. What is your process? Um, and we, you know, we made that ever present so that the developers are the ones who are making sure that you're getting to Kubernetes, you're getting to cloud native and you're doing it. >>Well, the folks watching, if you don't know the cloud native landscape slide, that ecosystem slide, it's getting bigger and bigger. There's more new things emerging. You see role of software abstractions coming in, automation and AI are coming in. So it makes it very challenging if you want to jump right in lifting and shifting to the clouds, really easy check, been there, done that, but companies want to refactor their applications, not just replatform refactoring means completely taking advantage of these higher level services. So, so it's going to be hard to navigate. So I guess with all that being said, what you guys advice to people who are saying, I need the navigation. I need to have the blueprint. What do I do? How do I get involved? And how do I leverage this? >>We want people to, you can go on to get hub and check out our group and read the maturity model. You can understand it, self identify where you're at, but we want people to get involved as well. So if they're seeing something that like, actually this needs to be adjusted slightly, please join the group. The cardiograph is group. Um, you can also get copies of our book available on the show. So if you, um, if you know, you can read it and it takes you line by line in a really playful way as to where you should be at in the maturity model. >>And on top of that, if you come Thursday was Sonia book. And of course, a lot of money, one day, I promise >>You guys are good. I gotta ask, you know, the final question is like more and more, just more personal commentary. If you don't mind, as teams start to change, this is obviously causing a lot of positive transformation if done, right? So the roles and the teams are starting to change. Hearing SRS are now not just the dev ops guys provisioning they're part of the, of the scale piece, the developers shifting left, new kind of workflows, the role of certain engineers and developers now, new team formations. Why were you guys seeing that evolve? Is there any trends that you see around how people are reconfiguring their team makeup? >>I think a lot of things is going to a single panic last tonight, where I'm taking dev and ops and putting them one panel where I can see everything going on in my environment, which is very critical. So right now we're seeing a pre-training where every client wants to be able to have the holy grail of a secret credit class to drive to that. But for you to get there, there's a lot of work you've got to do overnight that will not happen. And that's where this maturity model, I think again, will enhance that ability to do that. >>There's a cultural shift happening. I mean, people are changing there's new skillsets and you know, obviously there's a lot of people who don't have the skill. So it's super important that people work with Kubernetes, get certified, use the maturity model to help them know what skills they need. >>And it's a living document too. It's not, I mean, a book and I was living book. It's going to evolve. Uh, what areas you think are going to come next? So you guys have to predict if you had to see kind of where the pieces are going. Uh, obviously with cloud, everything's getting, you know, more Lego blocks to play with more coolness you have in the, in this world. What's coming next with Sue. Do you guys see any, any, uh, forecasts or >>We're working with each one of the tag groups within the CNCF to help us build it out and come up with what is next based on their expertise in the area. So we'll see lots more coming. Um, and we hope that the maturity grows and because of something that everybody relies on and that they can use alongside the landscape and the trail map. And, um, >>It's super valuable. I think you guys need a plug for any people want to, how they join. If I want to get involved, how do I, what do I do? >>Um, you can join the Carter Garfish group. You can check us out on, get hub and see all the information there. Um, we have a slack channel within the CNCF and we have calls every other Tuesday that people can see the pools. >>Awesome. Congratulations, we'll need it. And super important as people want to navigate and start building out, you know, you've got to edge right around the corner there it's happening real fast. Data's at the edge. You got cloud at the edge. Azure, AWS, Google. I mean, they're pushing really hardcore 5g, lot changes. >>Everybody wants to cloud today. Now one client is, one is more cloud. At least both the cloud is comfortable playing everywhere. One pump wife had DevOps. >>It's distributed computing back in the modern era. Thank you so much for coming on the keep appreciating. Okay. I'm Jennifer here for cube con cloud native con 2021 in person. It's a hybrid event. We're here live on the floor show floor, bringing you all the coverage. Thanks for watching station all day. Next three days here in Los Angeles. Thanks for watching. >>Thank you.

>>Good morning from Los Angeles, Lisa Martin here at Qube con cloud native con north America, 2021. This is the cubes third day, a wall-to-wall coverage. So great to be back at an event in person I'm excited to be joined by Vince Wang, senior director of products at 49. We're going to talk security and Kubernetes then welcome to the program. >>Thank you for having me. >>So I always love talking to 40 minutes. Cybersecurity is something that is such an impersonal interest of mine. The fording that talks about the importance of integrating security and compliance and the dev sec ops workflow across the container life cycle. Why is this important and how do you help companies achieve it? >>Well, as companies are making digital innovations, they're trying to move faster and as to move faster, or many companies are shifting towards a cloud native approach, uh, rapid integrations, rapid development, and rapid deployment, uh, but sometimes speed, you know, there's a benefit to that, but there's also the downside of that, where, you know, you can lose track of issues and you can, uh, introduce a human error in a problem. So as part of the, as part of the, the, the means to deliver fast while maintaining his six year approach, where both the company and the organizations delivering it and their end customers, it's important to integrate security throughout the entire life cycle. From the moment you start planning and development, and people's in process to when you're developing it and then deploying and running in production, um, the entire process needs to be secured, monitored, and, um, and vetted regularly with good quality, um, processes, deep visibility, and an integrated approach to the problem. Um, and I think the other thing to also consider is in this day and age with the current situation with COVID, there's a lot of, uh, development of employment in terms of what I call NASA dental Baltic cloud, where you're deploying applications in random places, in places that are unplanned because you need speed and that, uh, diversity of infrastructure and diversity of, uh, of clouds and development and things to consider then, uh, produces a lot of, uh, you know, uh, opportunities for security and, and challenges to come about. >>And we've seen so much change from a security perspective, um, the threat landscape over the last 18 months. So it's absolutely critical that the integration happens shifting left. Talk to us about now let's switch topics. Application teams are adopting CIC D uh, CICB workflows. Why does security need to be at the center of that adoption? >>Well, it goes back to my earlier point where when you're moving fast, your organizations are doing, um, you're building, deploying, running continuously and monitoring, and then improving, right? So the idea is you're, you're creating smaller, incremental changes, throwing it to the cloud, running it, adjusting it. So then you're, you're rapidly integrating and you're rapidly developing and delivery. And again, it comes down to that, that rapid nature, uh, things can happen. There's, there's more, uh, more points of touching and there's more points of interactions. And, you know, and again, when you're moving that fast, it's really easy to, um, miss things along the way. So as you have security as a core fundamental element of that DNA, as you're building it, uh, that that's in parallel with everything you're doing, you just make sure that, um, when you do deliver something that is the most secure application possible, you're not exposing your customers or your organizations to unforeseen risks that just kind of sits there. >>Uh, and I think part of that is if you think about cloud infrastructure, misconfiguration is still number one, uh, biggest problem with, uh, with security on the, in the cloud space, there's, uh, tasks and vulnerabilities those, we all know, and there's there's means to control that, but the configurations, when you're storing the data, the registries, all these different considerations that go into a cloud environment, those are the things that organizations need visibility on. And, um, the ability to, to adopt their processes, to be proactive in those things and know what they, uh, do. They just need to know what, what then, where are they're operating in, um, to kind of make these informed decisions. >>That visibility is key. When you're talking with customers in any industry, what are the top three, let's say recommendations to say, here's how you can reduce your exposure to security vulnerabilities in the CIS CD pipeline. What are some of the things that you recommend there to reduce the risk? >>There's a couple, oh, obviously security as a fundamental practice. We've been talking about that. So that's number one, key number. The second thing that I would say would be, uh, when you're adopting solutions, you need to consider the fact that there is a very much of a heterogeneous environment in today's, uh, ecosystem, lots of different clouds, lots of different tools. So integration is key. The ability to, um, have choices of deployment, uh, in terms of where you wanted to play. You don't want to deploy based upon the technology limitations. You want to deploy and operate your business to meet your business needs and having the right of integrations and toolings to, uh, have that flexibility. Now, option is key. And I think the third thing is once you have security, the choices, then you can treat, you create a situation where there's a lot of, uh, you know, process overhead and operational overhead, and you need a platform, a singular cybersecurity platform to kind of bring it all in that can work across multiple technologies and environments, and still be able to control at the visibility and consolidate, uh, policies and nationally consistent across all closet points. >>So we're to the DevOps folks, what are some of the key considerations that they need to take into >>Account to ensure that their container strategy isn't compromising security? Well, I think it comes down to having to think outside of just dev ops, right? You have to, we talk about CIC D you have to think beyond just the build process beyond just where things live. You have to think continuous life cycles and using a cyber security platform that brings it together, such as we have the Fortinet security fabric that does that tying a lot of different integration solutions. We work well within their core, but theirs have the ability to integrate well into various environments that provide that consistent policies. And I think that's the other thing is it's not just about integration. It's about creating that consistency across class. And the reality is also for, I think today's dev ops, many organizations are in transition it's, you know, as, as much as we all think and want to kind of get to that cloud native point in time, the reality is there's a lot of legacy things. >>And so dev ops set ups, the DevSecOps, all these different kind of operational functions need to consider the fact that everything is in transition. There are legacy applications, they are new cloud native top first type of application delivery is using containers of various technologies. And there needs to be a, again, that singular tool, the ability to tie this all together as a single pane of glass, to be able to then navigate emerge between legacy deployments and applications with the new way of doing things and the future of doing things with cloud native, uh, and it comes down again to, to something like the Fortinet security fabric, where we're tying things together, having solutions that can deploy on any cloud, securing any application on any cloud while bringing together that consistency, that visibility and the single point management, um, and to kind of lower that operational overhead and introduce security as part of the entire life cycle. >>Do you have a Vincent example of a customer that 49 has worked with that has done this, that you think really shows the value of what you're able to enable them to achieve? >>We do. We do. We have lots of customers, so can name any one specific customer for various reasons, you know, it's security after all. Um, but the, the most common use cases when customers look at it, that when you, we talked to a CIO, CSO CTO is I think that's a one enter they ask us is, well, how do we, how do we manage in this day and age making these cloud migrations? Everyone? I think the biggest challenge is everyone is in a different point in time in their cloud journey. Um, there's if you talk to a handful of customers or a rueful customers, you're not going to find one single organization that's going to be at the same point in time that matches them yet another person, another organization, in terms of how they're going about their cloud strategies, where they're deploying it at what stage of evolution there are in their organizational transformations. >>Um, and so what they're looking for is that, that that's the ability to deploy and security any application on any topic throughout their entire application life cycle. Um, and so, so the most common things that, that our customers are looking for, um, and, you know, they're doing is they're looking to secure things on the network and then interconnected to the cloud with, uh, to deliver that superior, uh, application experience. So they were deploying something like the security fabric. Uh, again, you know, Fordanet has a cybersecurity approach to that point and securing the native environments. They're looking at dev ops, they're deploying tooling to provide, uh, you know, security posture management, plus a few posture management to look at the things that are doing that, the registries, their environment, the dev environment, to then securing their cloud, uh, networks, uh, like what we do with our FortiGate solutions, where we're deploying things from the dev ops. >>I feel secure in the cloud environment with our FortiGate environments across all the various multitudes of cloud providers, uh, like, uh, AWS Azure, Google cloud, and that time that together with, with some secure, um, interconnections with SD LAN, and then tying that into the liver and productions, um, on the web application side. So it's a very much a continuous life cycle, and we're looking at various things. And again, the other example we have is because of the different places in different, uh, in terms of Tod journeys, that the number one key is the ability to then have that flexibility deployment to integrate well into existing infrastructure and build a roadmap out for, uh, cloud as they evolve. Because when you talk to customers today, um, they're not gonna know where they're going to be tomorrow. They know they need to get there. Uh, they're not sure how they're going to get there. And so what they're doing now is they're getting to cloud as quickly as they can. And then they're looking for flexibility to then kind of adjust and they need a partner like Fordanet to kind of bring that partnership and advisorship to, uh, to those organizations as they make their, their, their strategies clearer and, uh, adjust to new business demands. >>Yeah. That partnership is key there. So afforded it advocates, the importance of taking a platform approach to the application life cycle. Talk to me about what that means, and then give me like the top three considerations that customers need to be considering for this approach. >>Sure. Number one is how flexible is that deployment in terms of, do you, do customers have the option to secure and deploy any application, any cloud, do they have the flexibility of, um, integrating security into their existing toolings and then, uh, changing that out as they need, and then having a partner and a customer solution that kind of grows with that? I think that's the number one. Number two is how well are these, uh, integrations or these flexible options tied together? Um, like what we do with the security fabric, where everything kind of starts with, uh, the idea of a central management console that's, you know, uh, and consistent policies and security, um, from the get-go. And I think the third is, is looking at making sure that the, the, the security integrations, the secure intelligence is done in real time, uh, with a quality source of information, uh, and, and points of, uh, of responsiveness, um, what we do with four guard labs. >>For example, we have swell of large, um, machine learning infrastructure where have supported by all the various customer inputs and great intelligence organizations, but real time intelligence and percussion as part of that deployment life cycle. Again, this kind of really brings it all together, where organizations looking for application security and, and trying to develop in a CSED fashion. And you have the ability to then have security from the get, go hide ident to the existing toolings for flexibility, visibility, and then benefits from security all along the way with real time, you know, uh, you know, leading edge security, that then kind of brings that, that sense of confidence and reassurance as they're developing, they don't need to worry about security. Security should just be part of that. And they just need to worry about solving the customer problems and, uh, and, you know, delivering business outcomes and results. >>That's it, right? It's all about those business outcomes, but delivering that competence is key. Vince, thank you for joining me on the program today, talking through what 49 is doing, how you're helping customers to integrate security and compliance into the dev dev sec ops workflow. We appreciate your insights. >>Thank you so much for your time. I really appreciate it. My >>Pleasure for vents Wang. I'm Lisa Martin. You're watching the cube live from Los Angeles, uh, cube con and cloud native con 21 stick around at Dave Nicholson will join me next with my next guest.

welcome back to los angeles lisa martin here with dave nicholson day three of the cube's coverage of kubecon cloud native con north america 2020 we've been having some great comp live conversations in the last three days with actual guests on set we're very pleased to welcome to for the first time to our program shimon ben david the cto of weka welcome hey nice to be here nice to be here great to be at an in-person event isn't it no it's awesome they've done a great job i think you're green you're green like we're green fully green which is fantastic actually purple and hearts wake up yeah good to know green means you're shaking hands and maybe the occasional hug so talk to us about weka what's going on we'll kind of dig into what you guys are doing with kubernetes but give us that overview of what's going on at weka io okay so weka has been around for several years already uh we actually jade our product of 2016 so it's been out there uh actually eight of the fortune 50 are using weka um for those of you that don't know weka by the way we're a fully software defined parallel file system cloud native i know it's a mouthful and it's buzzword compliant but we actually baked all of that into the product from day one because we did other storage companies in the past and we actually wanted to take the best of all worlds and put that into one storage that is is not another me too it's not another compromise so we built the the environment we built weka to actually accommodate for upcoming technologies so we identified also that cloud technology is upcoming network actually exploded in a good way one gig 10 gig 100 gig 200 gig came out so we knew that that's going to be a trend and also cloud we saw cloud being utilized more and more and we kind of like bet that being able to be a parallel file system for the cloud would be amazing and it does how are you not on me too tell me tell us that when you're talking with customers what are the like the top three things that really differentiate weka speed scale and simplicity speed skills i like how fast you said that like quicker so speed sorry you see a lot of file system a lot of storage environments that are very um throughput oriented so speed how many gigabytes can you do to be honest a lot of storage environments are saying we can do that in that many gigabytes when we designed weka actually we wanted to provide an environment that would actually be faster than your local nvme on your local server because that's what we see are actually customers using for performance they're copying the data for their local to their local nvmes and process it we created an environment that is actually throughput oriented iops oriented latency sensitive and metadata performance so it's kind of like the best of all worlds and it's just not just a claim we actually showed it in many benchmarks uh top 500s supercomputing centers can talk for hours about performance but that's performance um scalability we actually are able to scale uh and we did show that we scaled to multiple petabytes we actually uh took some projects from scale-out nas appliances that actually got to their limit of their scale out and we we just continued from there double digit triple digits petabytes upcoming um and also scale is also how many clients can you service at once so it's not only how much capacity but also how many clients can you can you work with concurrently and simplicity all of that we from the initial design points were let's make something that is usable by users and not like so my mother can really use it right and so we have a very simple intuitive user interface but it's also api driven so you can automate around it so simplicity speed and scale love it so shimon it's interesting you said that your company was founded in 2016 in that in that time period because uh before jade ga ga 2016. um but but in those in in those surrounding years uh there were a lot of companies that were coming out at sort of the tail end of the legacy storage world yeah trying to just cannibalize that business you came out looking into the future where are we in that future now because you could argue that you guys maybe started a little early you could have taken a couple of years off and waited for uh for for the wave in the world of containerization as an example to come through but this is really this is like your time to shine isn't it exactly and being fully software defined we can always um adapt and we're always adapting so we bet on new technologies networking flash environments and these keep just keep on going and improving right when we went out we were like in 10 gig environments with ssds but we already knew that we're going to go to 100 and we also designed already for nvmes so kind like hardware constantly improved uh cpus for example the new intel cpus the new amd cpus we just accommodated for them because being software defined means that we actually bypass most of their inner workings and do things ourselves so that's awesome and then the cloud environment is growing massively and containers we see containers now in everyday uh use cases where initially it was maybe vms maybe bare metal but now everything is containerized and we're actually starting to see more and more kubernetes orchestrated environment uh coming out as well i still have a feeling that this is still a bit of dev property hey i'm a developer i'm a devops engineer i'm going to do it uh and it's there is i actually saw a lot of exciting things here um taking it to the next level to the it environment so um that's where we will show benefit as well so talk about how kubernetes users are are working with weka what is what superpower does that give them so um i think if you look at the current storage solutions that you have for kubernetes um they're interesting but they're more of like the let's take what we have today and plug it in right um so what kind of has a csi uh plug-in so it's easy to integrate and work with but also when you look at it um block is still being used in in kubernetes environments that i'm familiar with block was still being used for high performance so i i used uh pvs and pvcs to manage my pods uh claims and then but then i mounted them as read write once right because i couldn't share them then if a pod failed i had to reclaim the pvc and connect it to multiple environments because i wanted block storage because it's fast and then nfs environments was were used as read write many uh to be a shared environment but low performance so by being able to say hey we now have an environment that is fully covered kubernetes integrated and it provides all the performance aspects that you need you don't need to choose just run your fleet of pods your cluster of pods read write many you don't need to to manage old reclamations just to create new pods you get the best of all words ease of use and also uh the performance additionally because there's always more right we now see more and more uh cloud environments right so weka also has the ability and i didn't focus on that but it's it's really uh amazing it has the ability to move data around between different environments so imagine and we see that imagine on-prem environments that are now using weka you're in the terabytes or petabyte scale obviously you can copy and rsync and rclone right but nobody really does it because it doesn't work for these capacities so weka has the ability to say hey i can move data around between different environments so create more copies or simply burst so we see customers that are working on-prem throwing data to the cloud we see customers working on the cloud and and then we actually now see customers starting to bridge the gap because cloud bursting is again is a very nice buzzword we see some customers exploring it we don't really see customers doing it at the moment but the customers that are exploring it are exploring uh throwing the compute out to the cloud using the kubernetes cluster and throwing the data to the cloud using the weka cluster so there's and and one last thing because that's another interesting use case weka can be run converged on the same kubernetes cluster so there is no need to have even it's so in essence it's a zero footprint storage you don't need to even add more servers so i don't need to buy a box and connect my cluster to that box i just run it on the same servers and if i want more compute nodes i add more nodes and i'll add more storage by doing that so it's that simple so i was just looking at the website and see that waka was just this was just announced last week a visionary in the gartner mq for what's the mq4 distributed file systems and object storage talk to me talk talk to us about that what does that distinction mean for the company and how does the voice of the customer validate that great so actually this is interesting this is a culmination of a lot of hard work that all of the team did writing the product and all of the customers by adopting the product because it was in order to get to that i know we don't know if anybody is familiar with the criteria but you need to have a large footprint a distinguished footprint worldwide so we worked hard on getting that and we see that and we see that in multiple markets by the way financials we see a massive amounts of aiml projects containerized kubernetes orchestrated so getting to that was a huge achievement you could see other storage devices not being there because not not every storage appliance is is a parallel file system usually i think uh when you look at parallel file systems you you you attribute complexity and i need an army of people to manage it and to tweak it so that's again one of the things that we did and that's why we really think that we're a cool vendor in that magikarp magic quarter right because you it's that simple to manage uh you don't have any uh find you you cannot you don't need to find unity in like a bazillion different ways just install it we work it works you map it to your containers simple so we're here at kubecon a lot of talk about cloud native a lot of projects a lot of integration a lot of community development you've described installing weka into a kubernetes cluster where you know are there are there integrations that are being worked on what are the is there connective tissue between essentially this parallel file system that's spanning you say you have five nodes you have weka running on those five nodes you have a kubernetes cluster spanning those five nodes um what kinds of things are happening in the community maybe that you're supporting or that you're participating in to connect those together so right now you you don't uh we only have the csi plugin we didn't invest in in anything more actually one of the reasons that i'm here is to get to know the community a bit more and to get more involved and we're definitely looking into how more can we help customers utilize kubernetes and and enjoy the worker storage uh do we need to do some sort of integration i'm actually exploring that and i think you'll see some well so we got interesting so we got you at a good time now exactly yeah because you can say with with it with an api approach um you have the you have the connectivity and you're providing this storage layer that provides all the attributes that you described but you are here live living proof green wristband and all showing that the future will be even more interesting voting on the future yeah and and seeing how we can help the community and what can we do together and actually i'm really impressed by the the conference it's been amazing we've been talking about that all week being impressed with the fact that there's we've been hearing between 2 700 and 3 100 people here which is amazing in person of course there's many more that are participating virtually but they've done a great job of these green wristbands by the way we've talked about these a minute ago um this you have a red yellow or green option to to tell others are you comfortable with contact handshakes hugs etc i love that the fact that i am i'm sandwiched by two grains but they've done a great job of making this safe and i hope that this is a message this is a big community um the cncf has 138 000 contributors i hope this is a message that shows that you can do these events we can get together in person again because there's nothing like the hallway track you can't replicate that on video exactly grabbing people in the hallway in the hotel in the lobby talking about their problems seeing what they need what we do it's amazing right so so give us a little bit in our last few minutes here about the go to market what is the the gtm strategy for weka so that's an interesting question so being fully software defined when we started we we thought do we do another me too another storage appliance even though we're storage defined could we just go to market with our own boxes and we actually uh decided to go differently because our market was actually the storage vendors sorry the server vendors we actually decided to go and enable other bare metal environments manufacturers to now create storage solutions so we now have a great partnership with hpe with supermicro with hitachi uh and and more as well with aws because again being software defined we we can run on the cloud we do have massive projects on the clouds some of the we're all familiar with some but i can't mention um so and we we chose that as our go to market because we we are fully software defined we don't need any specific hardware for we just need a server with nvmes or an instance with nvmes and that's it there's no usually when i talk about what we need is as a product i also talk about the list of what we don't need is longer we don't need j bar j buffs servers ups we don't need all of that raid arrays we just need the servers so a lot of the server vendors actually identify that and then when we approach them and say hey this is what we can do on your bare metal on your environment is that valuable of course so so that's mostly our go to market another thing is that we chose to to focus on the markets that we're going after we're not another me too we're not another storage for your home directories even though obviously we are in some cases uh by customers but we're the storage where if you could shrink your wall clock time of your pipeline from two weeks to four hours and we did that's like 84 times faster if you could do that how valuable is that that's what we do that we see that more and more in modern enterprises so when we started doing that people were saying hey so your go to market is only hpc uh no all if you look at ai email life science um financials and the list goes on right modern environments are now being what hpc was a few years ago so there's massive amounts of data so our go to market is to be very targeted toward uh these markets and then we can say that they also uh push us to to other sides of the hey i have a worker so i might put my vmware on it i might put my i'll do my distributed compilation on this it's it's growing organically so that's fun to see awesome tremendous amount of growth i love that you talked about it very clearly simplicity speed and scale i think you did a great job of articulating why waka is not a me too last question are there any upcoming webinars or events or announcements that that folks can go to learn more about weka uh great question um i didn't come with my marketing hat but we we constantly have events and uh we usually what we usually do we we talk about the markets that we go after so for example a while ago we were in bioit so we published some uh life science articles um i need to see what's in the pipeline and definitely share it with you well i know you guys are going to be at re invent we do so hopefully we'll see you re-invent we're very in super computing as well if you'll be there fantastic i see that on your website there um i don't think we're there but we will see you we're a strong believer of of these conferences of these communities of being on the ground talking with people obviously if you can do it we'll do it with zoom but this is prices yeah it is there's nothing like it shimon it's been great to have you on the program thank you so much for giving us an update on weka sharing what you guys are doing how you're helping kubernetes users and what differentiates the technology we appreciate all your insights and your energy too no it's not me it's the product ah i love it for dave nicholson i'm lisa martin coming to you live from los angeles this is kubecon cloudnativecon north america 21 coverage on the cube wrapping up three days of wall-to-wall coverage we thank you for watching we hope you stay well

>>mhm mhm >>Hey guys, welcome back to Los Angeles lisa martin. Coming to you live from cuba con and cloud native Con north America 2021. Very excited to be here. This is our third day of back to back coverage on the cube and we've got a couple of guests cube alumni joining me remotely. Please welcome parse our karate senior consultant, product marketing, Dell Technologies and David Noi VP product management at Dell Technologies. Gentlemen welcome back to the program. >>Thanks johnny >>so far so let's go ahead and start with you. Let's talk about what Dell EMC is offering to developers today in terms of unstructured data. >>Absolutely, it's great to be here. So let me start with the container storage interface. This is Q khan and a couple of years ago the container storage interface was still in beta and the storage vendors, we're very enthusiastically kind of building the plug in city of the different storage portfolio to offer enterprise grade features to developers are building applications of the Cuban this platform. And today if you look at the deli in storage portfolio, big block volumes. Nash shares s three object A P I S beyond their virtual volumes. However you're consuming storage, you have the plug ins that are required to run your applications with these enterprise Great feature speech right about snap sharks data replication, all available in the Cuban this layer and just this week at coupon we announced the container storage modules which is kind of the next step of productivity for developers beat you know uh in terms of observe ability of the storage metrics using tools like Prometheus visualizing it ravana authorization capabilities so that you know too bad moments can have better resource management of the storage that is being consumed um that so there are these multiple models were released. And if you look at unstructured data, this term may be a bit new for our kind of not very family for developers but basically the storage. Well there is a distinction that is being made you know, between primary storage and unstructured storage or unstructured data solutions And by unstructured we mean file and object storage. If you look at the cube contact nickel sessions, I was very glad to see that there is an entire stream for um machine learning and data so that speaks to how popular communities deployment models are getting when it comes to machine learning and artificial intelligence. Um even applications like genomics and media and entertainment and with the container storage interface uh and the container storage modules with the object storage portfolio that bill has, we offer the comprehensive unstructured data solutions for developers beat object or file. And the advantage the developers are getting is these you know, if you look at platforms like power scale and these areas, these are like the industry workhorses with the highest performance. And if you think of scale, you know, think of 250 nasnotes, you know with a single name space with NVIDIA gpu direct capabilities. All these capabilities developers can use um for you know, applications like machine learning or any competition intensive for data intensive applications that requires these nass uh scale of mass platforms. So so um that's that's what is new in terms of uh what we are offering, you have the storage heaters >>got a parcel. Thank you. David, let's bring you into the conversation now you've launched objects scale at VM World. Talk to us about that, what some of the key features and capabilities are and some of those big business benefits that customers are going to be able to achieve. >>Sure thing. So I really want to focus on three of the biggest benefits. This would be the fact that the product is actually based on kubernetes country, the scale of the product and then its ability to do global replication. So let me just touch on those in order. Mhm You said that the product is based on kubernetes and here we are cube concept. The perfect time to be talking about that. This product really caters to those who are looking for a flexible way to deploy object storage in containerized fashion, appeals to the devops folks and folks who like to automate things and call the communities a P I. S to make uh the actual deployment of the product. Very simple in turnkey and that's really what people turn to kubernetes for is the ability to spin things up when they need them and spend them down as they don't and make that all on commodity hardware and commodity, you know, the quantity pricing and the idea there is that I'm making it as simple and easy as possible. You're not going to get as much shadow I. T. You won't have people going off and putting things off into a public cloud. And so where security of an organization or control of the data that flows with an organization is important. Having something that's easy for developers to use in the same paradigm that they're used to is critical. Now I talked about scale and you know, if you have come to me two years ago I would have told you, you know, kubernetes, yeah, containers people are kicking it around and they're doing some interesting science experiments, I would say in the last year I started to see a lot of requests from customers um in the dozens, even 200 petabyte range as it relates to capacity for committees and specifically looking for C. S. I and cozy with this. This this is the the object storage implementation of the container storage interfaces. Uh So skin was definitely there and the idea of this product is to provide easy scalability from the terabytes range into the multi petabyte range and again it's that ease of use, ease of deployment because it is kubernetes basically because it's a KPI driven that makes that possible. So we're talking about going from a three night minimum to thousands of nodes. and this allows people to deploy the product either at the edge or in the data center um in the edge because you can get very small deployments in the data center to massive scale. So we want to provide something that covers the gamut. The last thing I talked about was replication. So let me just touch upon what I mean by that uh when people go and build these deployments, if you're building a deployment at the edge of an object scale product, you're probably taking in sensor data or some kind of information that you want to then send back to a data center for processing. So you make it simple to do bucket based replication. An object, sorry object storage based replication to move things to another location. And uh that can be used either for bringing data back for analytics from the edge, it can be used for availability. So making sure that you have data available across multiple data centers in the case that you have an outage. It could be even used for sharing data between developers in one site and another site. So we provide that level of flexibility overall. Um this is the next generation object store leveraging. Dell technologies number one position in object storage. So I'm pretty excited about >>and how David is object scale integrated with VM ware software. Stop give us that slice and dice. >>Yeah, and that's a good question. And so, you know, we're talking about this being a Kubernetes based product, you can deploy it on open shift or we integrate directly with VM ware cloud foundation and with Tansy, which is VM ware's container orchestration and management platform. I've seen the demo of the product myself from my team and they've showed it to be did all of the management of the product was actually done within the V sphere Ui, which is great. So easy to go and just enter the V sphere. You I installed the product very simply have it up and running and then go and do all of your management through that user interface or to automate it using the same api is that you used to through VM ware and the 10 Zoo uh platform. >>Thank you, paris are back to you. Security is a big theme here in kubernetes. It's also been a big theme here. We've been talking about it the last three days here at cop con. How does Dell EMC's unstructured portfolio offer that necessary cyber protection that developers need to have and bake that into what they're doing. So >>surely, you know, they talk about cybersecurity, you know, there are different layers of security right from, you know, smarter firewalls to you know how to manage privileged account access and so on. And what we are trying to do is to provide a layer of cyber defense, right at the asset that you're trying to protect, which is the data and this is where the ransom their defender solution is basically detecting any patterns of the compromise that might have happened and alerting the I. T. Um administration about this um possible um intrusions into their into the data by looking at the data access parents in real time. So that's a pretty big deal. Then we're actually putting all this, you know, observance on the primary data and that's what the power scale platform cybersecurity protection features offers. Now we've also extended this kind of detection mechanism for the object data framework on pcs platforms as well. So this is like an additional layer of security at the um layer of uh you know where the data is actually being read and written. Do that's the area, you know, in case of object here we're looking at the S. Three traffic and trying to find his parents in case of a file data atmosphere, looking at the file's access parents and so on. So and in relation to this we're also providing uh data isolation mechanism that is very critical in many cyber recovery processes with the smart absolution as well. So this is something that the developers are getting for like without having to worry about it because that is something implemented at the infrastructure layer itself. So they don't have to worry about you know trying to court it or develop their application to integrate these kinds of things because it's an it's embedded in the infrastructure at the one of the FBI level at the E C. S A P I level. So that's pretty um pretty differentiating in the industry in the country storage solutions. I'll get. >>Uh huh. Yeah. I mean look if you look at what a lot of the object storage players are doing as it relates to cyber security. They're they're playing off the fact that they've implemented object lock and basically using that to lockdown data. And that's that's good. I mean I'm glad that they're doing that and if the case that you were able to lock something down and someone wasn't able to bypass that in some way, that's fantastic. Or if they didn't already encrypted before I got locked down what parts are is referring to is a little bit more than that. It's actually the ability to look at user behavior and determined that something bad is happening. So this is about actually being able to do, you know, predictive analytics being able to go and figure out that you're under attack. There's anomalous behavior um and we're able to go and actually infer from that that something bad is happening and where we think it's happening and lock it down even even more securely than for example just saying hey we provide object like capabilities which is one of the responses that I've seen out there from object storage vendors >>can you share with us. Parts are a customer example like walk us through how this is actually being used and deployed and what some of those business outcomes are. >>Yes lisa. So in terms of container realization itself, they have a media and entertainment kind of customer story here. Um Swiss TXT um they have a platform as a service where they serve their customer base with a range of uh you know, media production and broadcasting solutions and they have containers this platform and part of this computerization is part of their services is they offer infrastructure as a service to you know, media producers who need a high performance storage, high performance computing and power skill And Iceland have been their local solutions to offer this And now that they have containerized their core platform. Well you see a sign interface for power skills, they are able to continue to deliver the infrastructure, high performance infrastructure and storage services to their customers through the A. P I. And it's great to see how fast they could, you know, re factor their application but yet continue to offer the high performance and degrees enterprise grade uh features of the power scale platform. So Swiss Txt and would love to share more. Keep it on the story. Yeah. Hyperlink. >>And where can folks go to learn more about objects scale and what you guys are announcing? Yes, particular. You are a website that you want to direct folks too. >>I would say that technologies dot com. And uh that's the best place to start. >>Yeah, I would go to the Delta product pages around objects should be publicly built. >>Excellent guys, thank you for joining me on the program today. Walking through what how Dell EMC is helping developers with respect to unstructured data, Talking to us about objects skill that you launched VM world, some of those big customer benefits and of course showing us the validation, the proof in the pudding with that customer story. We appreciate your insights. >>Thank you. Thank you lisa >>For my guests. I'm Lisa Martin. You're watching the Cube live from Los Angeles. We're coming to you from our coverage of coupon and cloud native on North America 21. Coming back. Stick around. Rather I should say we'll be back after a short break with our next guest.

(upbeat music) >> Greetings from Los Angeles, Lisa Martin here with Dave Nicholson. We are on day three of the caves wall-to-wall coverage of KubeCon CloudNativeCon North America 21. We're pleased to welcome Mark Hinkle to the program, the co-founder and CEO of TriggerMesh. Mark welcome. >> Thank you, It's nice to be here. >> Lisa: Love the name. Very interesting TriggerMesh. Talk to us about what TriggerMesh does and what, when you were founded and what some of the gaps were that you saw in the market. >> Yeah, so TriggerMesh actually the Genesis of the name is in, cloud event, driven architecture. You trigger workloads. So that's the trigger and trigger mesh, and then mesh, we mesh services together, so cloud, so that's why we're called TriggerMesh. So we're a cloud native open source integration platform. And the idea is that, the number of cloud services are proliferating. You still have stuff in your data center that you can't decommission and just wholesale lift and shift to the cloud. So we wanted to provide a platform to create workflows from the data center, to the cloud, from cloud to cloud and not, and use all the cloud native design principles, but not leave your past behind. So that's, what we do. We're, very, we were cloud, we are cloud operators and developers, and we wanted the experience to be very similar to the way that DevOps folks are doing infrastructure code and deploying that we want to make it easy to do integration as code. So we follow the same design patterns, use the same domain languages, some of those tools like Hashi corpse, Terraform, and that that's what we do and how we go about doing it. >> Lisa: And when were you guys founded? >> September, 2018. >> Oh so your young, your three years young. >> Three years it's feels like 21 >> I bet. >> And startup years it's a lot has happened, but yeah, we my co-founder and I were former early cloud folks. We were at cloud.com worked through the OpenStack years and the CloudStack, and we just saw the pattern of, abstraction coming about. So first you abstract the hardware, then you abstract the operating system. And now at with the Kubernetes container, you know, evolution, you're abstracting it up to the application layer and we want it to be able to provide tooling that lets you take full advantage of that. >> Dave: So being founded in 2018, what's your perception of that? The shift that happened during the pandemic in terms of the drive towards cloud adoption and the demands for services like you provide? >> Mark: Yeah, I think it's a mixed blessing. So we, people became more remote. They needed to enable digital transformation. Biggest thing, I think that that for us is, you know, you don't go to the bank anymore. And the banking industry is doing, you know, exponentially more remote, online transactions than in person. And it's very important. So we decided that financial services is where we were going to start with first because they have a lot of legacy architecture. They have a lot of need to move to the cloud to have better digital experiences. And we wanted to enable them to, you know, keep their mainframes online while they were still doing cutting edge, you know, mobile applications, that kind of thing. >> Lisa: And of course the legacy institutions like the BFA's the Wells Fargo, they're competing with the fintechs who are much more nimble, much more agile and able to sort of disrupt the financial services industry. Was that part of also your decision to start in financial services? >> It was a little bit of luck because we started with our network and it turned out the, you know, we saw, we started talking to our friends early on, cause we're a startup and said, this is what we're going to do. And where it really resonated was PNC bank was our, one of our first customers. You know, another financial regulatory company was another one, a couple of banks in Europe. And we, you know, as we started talking about what we were doing, that we just gravitated there because they had the, the biggest need, even though everybody has the need, their businesses are, you know, critically tied to digital transformation. >> So starting with financial services. >> It's, it's counter intuitive, isn't it? >> It was counterintuitive, but it lends credibility to any other industry vertical that you're going to approach. >> Yeah, yeah it does. It's a, it's a great, they're going to be our hardest customers and they have more at stake than a lot of like transactions are millions and millions of dollars per hour for these folks. So they don't want to play around, they, they have no tolerance for failure. So it's a good start, but it's sort of like taking up jogging and running a marathon in your first week. It's very very grilling in that sense, but it really has made us a lot better and gave us a lot of insight into the kinds of things we need to do from not just functionality, but security and that kind of thing. >> Where are you finding these customers with respect to adoption of Kubernetes? Are they leading? Are they knowing we've got to get there eventually from an infrastructure perspective? >> So the interesting thing is Kubernetes is a platform for us to deliver on, so we, we don't require you to be a Kubernetes expert we offer it as a SaaS, but what happens is that the Kubernetes folks are the ones that we end up really engaging with earlier on. And I think that we find that they're in this phase of they're containerizing their apps, that's the first step. And then they're putting them on Kubernetes and then their next step is a security and integration path. So once she, I think they call it and this is my buzzword of the show day two operations, right? So they, they get to day two and then they have a security and an integration concern before they go live. So they want to be able to make sure that they don't increase their attack face. And then they also want to make sure that this newly deployed containerized infrastructure is as well integrated as the previous, you know, virtualized or even, you know, on the server infrastructure that they had before. >> So TriggerMesh, doesn't solely work in the containerized world, you're, you're sort of you're bridging the divide. >> Mark: Yes. >> What percentage of the workloads that you're seeing are the result of modernization migration, as opposed to standing up net new application environments in Kubernetes? Do you have a sense for that? >> I think we live in a lot in the brown field. So, you know, folks that have an existing project that they're trying to bridge to it versus the Greenfield kind of, you know, the, the huge wins that you saw in the early cloud days of the Netflix and the Twitter's Dwayne scale. Now we're talking to the enterprises who have, you know, they have existing concerns. So I would say that it's, it's mostly people that are, you know, very few net new projects, unless it's a modernization and they're getting ready to decommission an old one, which is. >> Dave: So Brownfield financial services. You just said, you know, let's just, let's just go after that. >> You know, yeah. I mean, we had this dart forward and we put up buzzwords, but no, it was, it was actually just, and you know, we're still finding our way as far as early on where we're open source folks. And we did not open source from day one, which is very weird when everybody's new, your identity is, you know, I worked, I was the VP of marketing for Linux foundation and no JS and all these open source projects. And my co-founder and I are Apache committers. And our project wasn't open yet because we had to get to the point where it could be open and people could be productive in the use and contribution. And we had to staff up engineers. And now I think this week we open-sourced our entire platform. And I think that's going to open up, you know, that's where we started because it was not necessarily the lowest hanging fruit, but the profitable, less profitable, lowest hanging fruit was financial services. Now we are letting our code out into the wild. And I think it'll be interesting to see what comes back. >> So you just announced that this week TriggerMesh integration platform as an open source project here at KubeCon, what's been some of the feedback? >> It's all been positive. I haven't heard anything negative. We did it, so we're very, very, there's a very, the culture around open source is very tough. It's very critical if you don't do it right. So I think we did a good job, we used enough, we used a OSI approved. They've been sourced, licensed the Apache software, a V2 license. We hired someone who was well-respected in the DevREL world from a chef who understands the DevOps sort of culture methodologies. We staffed up our engineers who are going to be helping the free and open source users. So they're successful and we're betting that that will yield business results down the road. >> Lisa: And what are the two I see on your website, two primary use cases that you guys support. Can you dig into details on that? >> So the first one is sort of a workflow automation and a really simple example of that is you have a, something that happens in one cloud. So for example, you take a picture on your phone and you upload it and it goes to Amazon and there is a service that wants to identify what's in that picture. And once you put it on the line and the internship parlance, you could kick off a workflow from TensorFlow, which is artificial intelligence to identify the picture. And there isn't a good way for clouds to communicate from one to the other, without writing custom blue, which is really what, what we're helping to get rid of is there's a lot of blue written to put together cloud native applications. So that's a workflow, you know, triggering a server less function is the workflow. The other thing is actually breaking up data gravity. So I have a warehouse of data, in my data center, and I want to start replicating some portion of that. As it changes to a database as a service, we can based on an event flow, which is passive. We're not, we're not making, having a conversation like you would with an API where there's an event stream. That's like drinking from the fire hose and TriggerMesh is the nozzle. And we can direct that data to a DBaaS. We can direct that data to snowflake. We can direct that data to a cloud-based data lake on Microsoft Azure, or we can split it up, so some events could go to Splunk and all of the events can go to your data lake or some of those, those things can be used to trigger workloads on other systems. And that event driven architecture is really the design pattern of the individual clouds. We're just making it multi-cloud and on-prem. >> Lisa: Do you have a favorite customer example that you think really articulates that the value of that use case? >> Mark: Yeah I think a PNC is probably our, well for the, for the data flow one, I would say we have a regular to Oracle and one of their customers it was their biggest SMB customer of last year. The Oracle cloud is very, very important, but it's not as tool. It doesn't have the same level of tooling as a lot of the other ones. And to, to close that deal, their regulatory customer wanted to use Datadog. So they have hundreds and hundreds of metrics. And what TriggerMesh did was ingest the hundreds and hundreds of metrics and filter them and connect them to Datadog so that, they could, use Datadog to measure, to monitor workloads on Oracle cloud. So that, would be an example of the data flow on the workflow. PNC bank is, is probably our best example and PNC bank. They want to do. I talked about infrastructure code integration is code. They want to do policy as code. So they're very highly regulatory regulated. And what they used to do is they had policies that they applied against all their systems once a month, to determine how much they were in compliance. Well, theoretically if you do that once a month, it could be 30 days before you knew where you were out of compliance. What we did was, we provided them a way to take all of the changes within their systems and for them to a server less cluster. And they codified all of these policies into server less functions and TriggerMesh is triggering their policies as code. So upon change, they're getting almost real-time updates on whether or not they're in compliance or not. And that's a huge thing. And they're going to, they have, within their first division, we worked with, you know, tens of policies throughout PNC. They have thousands of policies. And so that's really going to revolutionize what they're able to do as far as compliance. And that's a huge use case across the whole banking system. >> That's also a huge business outcome. >> Yes. >> So Mark, where can folks go to learn more about TriggerMesh, maybe even read about more specifically about the announcement that you made this week. >> TriggerMesh.com is the best way to get an overview. The open source project is get hub.com/triggermesh/trigger mesh. >> Awesome Mark, thank you for joining Dave and me talking to us about TriggerMesh, what you guys are doing. The use cases that you're enabling customers. We appreciate your time and we wish you best of luck as you continue to forge into financial services and other industries. >> Thanks, it was great to be here. >> All right. For Dave Nicholson, I'm Lisa Martin coming to you live from Los Angeles at KubeCon and CloudNativeCon North America 21, stick around Dave and I, will be right back with our next guest.

hey everyone this is thecube's live coverage from los angeles of kubecon and cloud native con north america 21 lisa martin with dave nicholson we're going to be talking with the founder and ceo next of cloudnatics rohit seth rohit welcome to the program thank you very much lisa pleasure to meet you good to meet you too welcome so tell the the audience about cloudnatics what you guys do when you were founded and what was the gap in the market that you saw that said we need a solution so just to start uh cloud9x was started in 2019 by me and the reason for starting cloud netex was as i was starting to look at the cloud adoption and how enterprises are kind of almost blindly jumping on this cloud bandwagon i started reading what are the key challenges the market is facing and it started resonating with what i saw in google 15 years before when i joined google the first thing i noticed was of course the scale would just overwhelm anyone but at the same time how good they are utilized at that scale was the key that i was starting to look for and over the next couple of months i did all the scripting and such with my teams and found out that lower teens is the utilization of their computers servers and uh lower utilization means if you're spending a billion dollars you're basically wasting the major portion of that and a tech savvy company like google if that's a state of affair you can imagine what would be happening in other companies so in any case we actually now started work at that time started working on a technology so that more groups more business units could share the same machine in a efficient fashion and that's what led to the invention of containers over the next six years we rolled out containers across the whole google fleet the utilization went up at least three times right fast forward 15 years and you start reading 125 billion dollars are spent on a cloud and 60 billion dollars of waste someone would say 90 billion dollars a waste you know what i don't care whether 60 or 90 billion is a very large number and if tech savvy company google couldn't fix it on its own i bet you it it's not an easy problem for enterprises to fix it so we i started talking to several executives in the valley about is this problem for real or not the worst thing that i found was not only they didn't know how bad the problem was they actually didn't have any means to find out how bad the problem could be right one cfo just ran like headless chicken for about two months to figure out okay i know i'm spending this much but where is that spend going so i started kind of trading those waters and i started saying okay visibility is the first thing that we need to provide to the end customer saying that listen it doesn't need to be rocket science for you to figure out how much is your marketing spending how much your different business units so the first line of action is basically give them the visibility that they need to make the educated business decisions about how good or how bad they are doing their operations once they have the visibility the next thing is what to do if there is a waste there are a thousand different type of vms on aws alone people talk about complexity on multi-cloud hybrid cloud and that's all right but even on a single cloud you have thousand vms the heterogeneity of the vms with dynamic pricing that changes every so often is a killer and so and so rohit when you talk about driving levels of efficiency you're not just you're not just talking about abstraction versus bare metal utilization you're talking about even in environments that have used sort of traditional virtualization yes okay absolutely i think all clouds run in vms but within vms sometimes you have containers sometimes you don't have containers if you don't have containers there is no way for you to securely have a protagonist and antagonist job running on the same machines so containers basically came to the world just so that different applications could share the same resources in a meaningful fashion we are basically extending that landscape to to the enterprises so that that utilization benefit exists for everyone right so first of first order business for cloud natick is basically provide them the visibility on how well or bad they are doing the second is to give them the recommendation if you are not doing well what to do about it to do well and we can actually slice and dice the data based on what is important for you okay we don't tell you that these are the dimensions that you should be looking at of course we have our recommendations but we actually want you to figure out basically do you want to look at your marketing organization or your engineering organization or your product organization to see where they are spending money and you can slice and match that data according and we'll give you recommendations for those organizations but now you have the visibility now you have the recommendations but then what right if you ask a cubernities administrator to go and apply those recommendations i bet you the moment you have more than five cluster which is a kind of a very ordinary thing it'll take at least two hours just to figure out how to go from where you are to be able to log in and to be able to apply those recommendations and then changing back the ci cd pipelines and asking your developers to be cognizant about your resources next time is a month-long ordeal no one follows it that's why those recommendations falls on deaf ears most of the time what we do is we give you the choice you want to apply those recommendations manually or you can put the whole system on autopilot in which case once you have enough confidence in cloud native platform we will actually apply those recommendations for you dynamically on the fly as your workloads are increasing or decreasing in utilization and where are your customer conversations happening you mentioned the cfl you mentioned the billions in cloud waste where do you start having these conversations within an organization because clearly you mentioned marketing services you can give them that visibility across the organization who are you talking to within these customers so we start with mostly the cios ctos vp of engineering but it's very interesting we say it's a waste and i think the waste is most more of an effect than a cause the real cause is the complexity and who is having the complexity is the devops and the developers so in 99 of our customer interactions we basically start from cios and ctos but very soon we have these conversations over a week with developers and devops leads also sitting in the room saying that but this is a challenge on why i cannot do this so what we have done is to address the real cause and waste aspect of cloud computing we have we have what we call the management console through which we reduce the complexity of kubernetes operations themselves so think about how you can log into a crashing pod within two minutes rather than two hours right and this is where cloud native start differentiating from the rest of the competition out there because we provide you not only or do this recommendation do this right sizing of vm here or there but this is how you structurally fix the issue going forward right i'm not going to tell you that your containers are not going to crash loop their failures are regular part of distributed systems how you deal with them how you debug them and how you get it back up and running is a core integral part of how businesses get run that's what we provide in cloud natives platform a lot of this learning that we have is actually coming from our experience in hyperscalers we have a chief architect who is also from google he was a dl of a technology called borg and then we have sonic who was the head of products at mesosphere before so we understand what it takes for an enterprise who's primarily coming from on-prem or even the companies that are starting from cloud to scale in cloud often you hear this trillion dollar paradoxes that hey you're stupid if you don't start from cloud and you're stupid if you scale at cloud we are saying that if you're really careful about how you function on cloud it has a value prop that can actually take you to the web scalar heights without even blinking twice can you share an example of one of your favorite customer stories absolutely even by industry only where you've really shown them tremendous value in savings absolutely so a couple of discussions that happened that led like oh but we are we have already spent a team of four people trying to optimize our operations over the last year and we said that's fine uh you know what our onboarding exercise takes only 20 minutes right let's do the onboarding in about a week we will tell you if we could save you any money or not and put your best devops on this pov prove a value exercise to see if it actually help their daily life in terms of operations or not this particular customer only has 30 clusters so it's not very small but it's not very big in terms of what we are seeing in the market first thing the maximum benefit or the cost optimization that they could do over the past year using some of the tools and using their own top-class engineering shots were about seven to ten percent within a week we told them 38 without even having those engineers spend more than two hours in that week we gave them the recommendations right another two weeks because they did not want to put it on autopilot just because it's a new platform in production within next two hours they were able to apply i think at least close to 16 recommendations to their platform to get that 37 improvement in cost what are some examples of of recommendations um obviously you don't want to reveal too much of the secret sauce behind the scene but but but you know what are some what are some classic recommendations that are made so some of them could be as low-hanging fruit as or you have not right sized your vms right this is what i call a lot of companies you would find that oh you have not right side but for us that's the lowest hanging code you go in and you can tell them that whether you have right size that thing or not but in kubernetes in particular if you really look at how auto scaling up and how auto scaling down happens and particularly when you get a global federated view of the number of losses that's where our secret sources start coming and that's where we know how to load balance and how to scale vertically up or how to scale horizontally within the cluster right those kind of optimization we have not seen anywhere in the market so far and that's where the most of the value prop that our customers are seeing kind of comes out and it doesn't take uh too much time i think within a week we have enough data to to say that this service that has thousands of containers could benefit by about this much and just to kind of give you i wouldn't be able to go into the specific dollar numbers here but we are talking in at least a 5 million ish kind of a range of a spend for this cluster and think about it 37 of that if we could save that that kind of money is a real money that not only helps you save your bottom line but at that level you're actually impacting your top line of the business as well sure right that's our uh value crop that we are going to go in and completely automate you're not going to look for devops that don't exist anymore to hire one of the key challenges i'm pretty sure that you must have already heard 86 percent of businesses are not able to hire the devops and they want to hire 86 percent what happens when you don't have that devops that you want to have your existing devops want to move as fast cutting corners sometimes not because they don't know anywhere but just because there's so much pressure to do so much more they don't scale when things become brittle that's when um the fragility of the system comes up and when the demand goes up that's when the systems break but you're not prepared for that breakage just because you have not really done the all the things that you would have done if you had all the time that you needed to do the right thing it sounds like some of the microservices that are in containers that are that run the convention center here have just crashed i think it's gone hopefully the background noise didn't get picked up too much yeah but you're the so the the time to value the roi that you're able to deliver to customers is significant yes you talked about that great customer use case are there any kind of news or announcements anything that you want to kind of share here that folks can can be like looking forward to without the index absolutely so two things even though this is kubecon and everyone is focused on kubernetes kubernetes is still only about three to five percent of enterprise market okay we differentiate ourselves by saying that it doesn't matter whether you're running kubernetes or you're in running legacy vms we will come on board in your environment without you making a single line of change in less than 20 minutes and either we give you the value prop in one week or we don't all right that's number one number two we have a webinar coming on november 3rd uh please go to cloudnetix.com and subscribe or sign up for that webinar sonic and i will be presenting that webinar giving you the value proposition going through some use cases that oh we have seen with our customers so far so that we can actually educate the broader audience and let them know about this beautiful platform i think that my team has built up here all right cloudnatics.com rohit thank you for joining us sharing with us what you're doing at cloud natives why you founded the company and the tremendous impact and roi that you're able to give to your customers we appreciate learning more about the technology thank you so much and i really believe that cloud is here for stay for a long long time it's a trillion dollar market out there and if we do it right i do believe we will accelerate the adoption of cloud even further than what we have seen so far so thanks a lot lisa it's been a pleasure nice to meet you it's a pleasure we want to thank you for watching for dave nicholson lisa martin coming to you live from los angeles we are at kubecon cloudnativecon north america 21. dave and i will be right back with our next guest thank you you

(soft techno music) >> Good evening. Welcome back to the Kube. Live in Los Angeles. We are at KubeCon Cloud Native Con 2021. Lisa Martin with Dave Nicholson, rounding out our day. We're going to introduce you to a new company, a new company that's new to us. I should say, log DNA. Peter Choi joins us the VP of product. Peter, welcome to the program. >> Thanks for having me. >> (Lisa) Talk to us about log DNA. Who are you guys? What do you do? >> So, you know, log DNA is a log medicine platform. Traditionally, we've been focused on, you know, offering log analysis, log management capabilities to dev ops teams. So your classic kind of troubleshooting, debugging, getting into your systems. More recently, maybe in like the last year or so we've been focused on a lot of control functionality around log medicine. So what I mean by that is a lot of people typically think of kind of the analysis or the dashboards, but with the pandemic, we noticed that you see this kind of surge of data because all of the services are being used, but you also see a downward pressure on cost, right? Because all of a sudden you don't want to be spending two X on those digital experiences. So we've been focused really on kind of tamping down kind of controls on the volume of log data coming in and making sure that they have a higher kind of signal and noise ratio. And then, you know, I'll talk about it a little bit, but we've really been honing in on how can we take those capabilities and kind of form them more in a pipeline. So log management, dev ops, you know, focusing on log data, but moving forward really focused on that flow of data. >> (Dave) So, when you talk about the flow of data and logs that are being read, make this a little more real, bring it up, bring it up just to level in terms of data, from what? >> Yeah. >> What kind of logs? What things are generating logs? What's the relevant information that's being. Kept track of? >> Yeah, I mean, so from our perspective, we're actually agnostic to data source. So we have an assist log integration. We have kind of basic API's. We have, you know, agents for any sort of operating system. Funny enough people actually use those agents to install, log DNA on robots, right? And so we have a customer they're, you know, one of the largest E-commerce platforms on, in the, in the world and they have a warehouse robots division and they installed the agent on every single one of those robots. They're, you know, they're running like arm 64 processors and they will send the log data directly to us. Right? So to us, it's no different. A robot is no different from a server is no different from an application is no different from a router. We take in all that data. Traditionally though, to answer your question, I guess, in the simplest way, mostly applications, servers, firewalls, all the traditional stuff you'd expect kind of going into a log platform. >> So you mentioned a big name customer. I've got a guess as to who that is. I won't, I won't say, but talk to us about the observability pipeline. What is that? What are the benefits in it for customers? >> (Peter) Sure. So, like if we zoom out again, you know, you think about logs traditionally. I think a lot of folks say, okay, we'll ingest the logs. We'll analyze them. What we noticed is that there's a lot of value in the step before that. So I think in the earlier days it was really novel to say, Hey, we're going to get logs and we're going to put it into a system. We're going to analyze it. We're going to centralize. Right. And that had its merits. But I think over time it got a little chaotic. And so you saw a lot of the vendors over the last three years consolidating and doing more of a single pane of glass, all the pillars of observability and whatnot. But then the downside of that is you're seeing a lot of the teams that are using that then saying being constrained by single vendor for all the ways that you can access that data. So we decided that the control point being on the analysis side on, on the very far right side was constricting. So we said, okay, let's move the control point up into a pipeline where the logs are coming to a single point of ingress. And then what we'll do is we will offer views, but also allow you to stream into other systems. So we'll allow you to stream into like a SIM or a data warehouse or something, something like that. Right? So, and you know, we're still trying to like nail down the messaging. I'm sure our marketing person's going to roast me after this. But the simplest way to think of observability pipeline is it's the step before the analysis part, that kind of ingest processes and routes the data. >> (Dave) Yeah. This is the Kube, by the way, neither one of us is a weather reporter. (laughing) So, so the technical stuff is good with us. >> Yes. It is. What are, and talk to us about some of the key features and capabilities and maybe anything that's newly announced are going to be announced. >> Yeah. For sure. So what we recently announced early access on is our streaming capabilities. So it's something that we built in conjunction with IBM and with a couple of, you know, large major institutions that we were working with on the IBM cloud. And basically we realized as we were ingesting a log data, some of those consumers wanted to access subsets of that data and other systems such as Q radar or, you know, a security product. So we ended up taking, we filtered down a subset of that data and we stream it out into those systems. And so we're taking those capabilities and then bringing it into our direct product, you know, whatever you access via logging.com. That is what's essentially going to be the seed for the kind of observability pipeline moving forward. So when you start thinking about it, all of this stuff that I mentioned, where we say, we're focusing on control, like allowing you to exclude logs, allowing you to transform logs, you take those processing capabilities, you take the streaming capabilities, you put them together and all of a sudden that's the pipeline, right? So that's the biggest focus for us now. And then we also have supporting features such as, you know, control API's. We have index rate alerting so that you can get notified if you see aberrations in the amount of flow of data. We have things like variable retention. So when a certain subset of logs come in, if you want it store it for seven days or 30 days, you can go ahead and do that because we know that a large block of logs is going to have many different use cases and many different associated values, right? >> So let's pretend for a moment that a user, somebody who has spent their money on log DNA is putting together a Yelp review and they've given you five stars. >> Yup. >> What do they say about log DNA? Why did they give you that five star rating? >> Yeah. Absolutely. I think, you know, the most common one and it's funny it's Yelp because we actually religiously mine, our G2 crowd reviews. (all laughing) And so the thing that we hear most often is, it's ease of use, right? A lot of these tools. I mean, I'm sure, you know, you're talking to founders and product leaders every day with developers. Like the, the bar, the baseline is so low, you know, a lot of, a lot of organizations where like, we'll give them the, you know, their coders, they'll figure it out. We'll just give them docs and they'll figure it out. But we, we went a little bit extra in terms of like, how can we smooth that experience so that when you go to your computer and you type in QTPL, blah, blah, blah, two lines, and all of a sudden all your logs are shipping from your cluster to log DNA. So that's the constant theme for us in all of our views is, Hey, I showed up, I signed up and within 30 minutes I had everything going that I needed to get. >> (Lisa) So fast time to value. >> Yes. >> Which is critical these days. >> Absolutely. >> Talk to me. So here we are at, at KubeCon, the CNCF community is huge. I think I, the number I saw yesterday was 138,000 contributors. Lots of activity, because we're in person, which is great. We can have those hallway networking conversations that we haven't been able to have in a year and a half. What are some of the things that you guys have heard at the booth in terms of being able to engage with the community again? >> You know, the thing that we've heard most often is just like having a finger on the pulse. It's so hard to do that because you know, when we're all at our computers, we just go from zoom to zoom. And so it, it like, unless it punches you in the face, you're not aware of it. Right. But when you come here, you look around, you go, you can start to identify trends, you hear the conversations in the hallway, you see the sessions. It's just that, that sense of, it's almost like a Phantom limb that, that sense of community and being kind of connected. I think that's the thing that we've heard most often that people are excited. And, you know, I think a lot of us are just kind of treating this like a dry run. Like we're kind of easing our way back in. And so it, you know, it felt good to be back. >> Well, they've done a great job here, right? I mean, you have to show your proof of vaccination. They're doing temperature checks, or you can show your clear health pass. So they're making it. We were talking to the executive director of CNCF earlier today and you're making it, it's not rocket science. We have enough data to know that this can be done carefully and safely. >> (David) Don't forget the wristbands. >> That's right. And, and did you see the wristbands? >> (Peter) Oh yeah. >> Yeah, yeah that's great. >> Yep, it is great. >> I was, I was on the fence by the way. I was like, I was a green or yellow, depending on the person. >> (both) Yeah. >> Yeah. But giving, giving everybody the opportunity to socialize again and to have those, those conversations that you just can't have by zoom, because you have somebody you've seen someone and it jogs your memory and also the control of do I want to shake someone's hand or do I not. They've done a great job. And I think hopefully this is a good test in the water for others, other organizations to learn. This can be done safely because of the community. You can't replicate that on video. >> (Peter) Absolutely. And I'll tell you this one for us, this is our, this is our event. This is the event for us every single year. We, we it's the only event we care about at the end of the day. So. >> What are some of the things that you've seen in the last year, in terms of where, we were talking a lot about the, the adoption of Kubernetes, kind of, where is it in its maturation state, but we've seen so much acceleration and digital transformation in the last 18 months for every industry businesses rapidly pivoting multiple times to try to, to survive one and then figure out a new way to thrive in this, this new I'll call it the new. Now I'll borrow that from a friend at Citrix, the new now, not the new normal, the new now, what are some of the things that you've seen in the last year and a half from, from your customer base in terms of what have they been coming to you saying help? >> (Peter) You know, I think going back to the earlier point about time to value, that's the thing that a lot. So a lot of our customers are, you know, very big Kubernetes, you know, they're, they're big consumers of Kubernetes. I would say, you know, for me, when I do the, we do our, our QBRs with our top customers, I would say 80% of them are huge Kubernetes shops. Right. And the biggest bottleneck for them actually is onboarding new engineers because a lot of the, and you know, we have a customer, we have better mortgage. We have, IBM, we have Rappi is a customer of ours. They're like Latin American version of Instacart. They double their engineering base and you, you know, like 18 in 18 months. And so that's, you know, I think it was maybe from 1500 to 3000 developers or so, so their thing is like, we need to get people on board as soon as possible. We need to get them in these tools, getting access to, to, to their longs, to whatever they need. And so that's been the biggest thing that we've heard over and over again is A, how can we hire? And then B when we hire them, how do we onboard them as quickly as possible, so that they're ramped up and they're adding value. >> How do you help with that onboarding, making it faster, seamless so that they can get value faster? >> So for us, you know, we really lean in on our, our customer success teams. So they do, you know, they do trainings, they do best practices. Basically. We kind of think of ourselves given how much Kubernetes contradiction we have, we think of ourselves as cross pollinators. So a lot of the times we'll go into those decks and we'll try to learn just as much as we're trying to try to teach. And then we'll go and repeat that process through every single set of our customers. So a lot of the patterns that we'll see are, well, you know, what kinds of tools are you using for orchestration? What kind of tools are you using for deployment? How are you thinking about X, Y, and Z? And then, you know, even our own SRE teams will kind of get into the mix and, you know, provide tips and feedback. >> (Lisa) Customer centricity is key. We've heard that a lot today. We hear that from a lot of companies. It's one thing to hear it. It's another thing to see it. And it sounds like the Yelp review that you would have given, or, or what you're hearing through G2 crowd. I mean, that voice of the customer is valid. That's, that's the only validation. I think that really matters because analysts are paid. >> Yeah. >> But hearing that validation through the voice of the customer consistently lets you know, we're going in the right direction here. >> Absolutely. >> I think it's, it's interesting that ease of use comes up. You wonder if those are only anonymous reviews, you don't necessarily associate open source community with cutting edge, you know, we're the people on the pirate ship. >> (Peter) Yeah. And so when, when, when people start to finally admit, you know, some ease of use would be nice. I think that's an indication of maturity at a certain point. It's saying, okay, not everyone is going to come in and sit behind a keyboard and program things in machine language. Every time we want to do some simple tasks, let's automate, let's get some ease of use into this. >> And I'll tell you in the early days it drove me and our, our CEO talker. It drove us nuts that people would say easiest to be like, that's so shallow. It doesn't mean anything. Well, you know, all of that. However, but to your point, if we don't meet the use case, if we don't have the power behind it, the ease of use is abstracting away. It's like an iceberg, right. It's abstracting away a lot. So we can't even have the ease of use conversation unless we're able to meet the use case. So, so what we've been doing is digging into that more, be like, okay, ease of use, but what were you trying to do? What, what is it that we enabled? Because ease of use, if it's a very shallow set of use cases is not as valid as ease of use for petabytes of data for an organization like IBM. Right? >> That's a great, I'm glad that you dug into that because ease of use is one of those things that you'll see it in marketing materials, but to your point, you want to know what does this actually mean? What are we delivering? >> Right. >> And now, you know what you're delivering with Peter, thank you for sharing with us about logged in and what you guys are doing, how you're helping your community of customers and hearing the voice of the customer through G2 and others. Good work. >> Thank you. And by the way, I'll be remiss if I, if I don't say this, if you're interested in learning more about some of the stuff that we're working on, just go to logging in dot com. We've got, I think we've got a banner for the early access programs that I mentioned earlier. So, you know, at the end of the day, to your point about customer centricity, everything we prioritize is based on our customers, what they need, what they tell us about. And so, you know, whatever engagement that we get from the people at the show and prospects, like that's how we drive a roadmap. >> (Lisa) Yup. That's why we're all here. Log dna.com. Peter, thank you for joining Dave and me today. We appreciate it. >> Thanks for having me. >> Our pleasure for Dave Nicholson. I'm Lisa Martin signing off from Los Angeles today. The Kubes coverage of KubeCon clouding of con 21 continues tomorrow. We'll see then. (soft techno music)

>>Mhm Welcome back to Los Angeles. The Cubans live, I can't say that enough. The Cubans live. We're at cu con cloud Native Con 21. We've been here all day yesterday and today and tomorrow talking with lots of gas. Really uncovering what's going on in the world of kubernetes, lisa martin here with Dave Nicholson. We've got some folks. Next we're gonna be talking about a customer use case, which is always one of my favorite things to talk about. Please welcome Michael Coletti, the principal platform engineer at CHG Healthcare and then cat from a christian VP of products from port works by pure storage. Guys, welcome to the program, Thank you. Happy to be here. Yeah. So Michael, first of all, let's go ahead and start with you, give the audience an overview of CHG healthcare. >>Yeah, so CHG Healthcare were a staffing company so we sure like a locum pen and so our clients are doctors and hospitals, so we help staff hospitals with temporary doctors or even permanent placing. So we deal with a lot of doctors, a lot of nursing and we're were a combination of multiple companies to see if she is the parents. So and uh yeah, we're known in the industry is one of the leaders in this, this field and providing uh hospitals with high quality uh doctors and nurses and uh you know, our customer services like number one and one of these are Ceos really focused on is now how do we make that more digital, how we provide that same level of quality of service, but a digital experience as rich for >>I can imagine there was a massive need for that in the last 18 months alone. >>Covid definitely really raised that awareness out for us and the importance of that digital experience and that we need to be out there in the digital market. >>Absolutely. So your customer report works by pure storage, we're gonna get into that. But then can talk to us about what's going on. The acquisition of port works by peer storage was about a year ago I talked to us about your VP of product, what's going on? >>Yeah, I mean, you know, first of all, I think I could not say how much of a great fit for a port works to be part of your storage. It's uh uh Pure itself is a very fast moving large start up that's a dominant leader in a flash and data center space. And you know, pure recognizes the fact that Cuban it is is the new operating system of the cloud is now how you know, it's kind of virtualizing the cloud itself and there is a, you know, a big burgeoning need for data management in communities and how you can kind of orchestrate work lords between your on prem data centers in the cloud and back. So port books fits right into the story as complete vision of data management for our customers and uh spend phenomenal or business has grown as part of being part of Pure and uh you know, we're looking at uh launching some new products as well and it's all exciting times. >>So you must have been pretty delighted to be acquired as a startup by essentially a startup because because although pure has reached significant milestones in the storage business and is a leader in flash storage still, that, that startup mindset is there, that's unique, that's not, that's not the same as being acquired by a company that's been around for 100 years seeking to revitalize >>itself. Can >>you talk a little bit about that >>aspect? So I think it will uh, Purest culture is highly innovation driven and it's a very open flat culture. Right? I mean everybody impure is accessible, it can easily have a conversation with folks and everybody has his learning mindset and Port works is and has always been in the same way. Right? So when you put these teams together, if we can create wonders, I mean we, right after that position, just within a few months we announced an integrated solution that Port works orchestrates volumes and she file shares in Pure flash products and then delivers as an integrated solution for our customers. And Pure has a phenomenal uh, cloud based monitoring and management system called Pure one that we integrated well into. Now we're bringing the power of all of the observe ability that Purest customers are used to for all of the partners customers and having super happy, you know, delivering that capability to our customers and our customers are delighted now they can have a complete view all the way from community is an >>app to the >>flash and I don't think any one company on the planet can even climb, they can do that. >>I think, I think it's fair to acknowledge that pure one was observe ability before observe ability was a word. Exactly one used regularly. So that's very interesting. >>I could talk to us about obviously you are a customer CHD as a customer of court works now Port works by peer storage. Talk to us about the use case, what what was the compelling? It was their compelling event and from a storage perspective that that led you to Port works in the >>first so we be, they began this our Ceo basically in the vision, we we need to have a digital presence, we need and hazards and this was even before Covid, so they brought me on board and my my manager read uh glass or he we basically had this task to how are we going to get out into the cloud, how we're going to make that happen And we we chose to follow very much cloud native strategy and the platform of choice. I mean it just made sense with kubernetes and so when we were looking at kubernetes, we're starting to figure out how we're doing, we knew that data is going to be a big factor, you know, um being to provide data, we're very much focused on an event driven, were really pushing to event driven architecture. So we leverage Kafka on top of kubernetes, but at the time we were actually leveraging Kafka with M S K down out in a W S and that was just a huge cost to us. So I came on board, I had experienced with poor works prior company before that and I basically said we need to figure out a great storage away overlay. And the only way to do is we gotta have high performance storage, we've got to have secure, we gotta be able to back up and recover that storage and the poor works was the right match and that allowed us to have a very smooth transition off of M S K onto kubernetes, saving us, it's a significant amount of money per month and just leverage that already existing hardware that are existing, compute memory and just in the and move right to port works, >>leveraging your existing investments. >>Exactly which is key. Very, very key. So, >>so been kept, how common are the challenges that when you guys came together with the HD, how common are the challenges? It's actually, >>that's a great question, you know, this is, I'll tell you the challenges that Michael and his team are running into is what we see a lot in the, in the industry where people pay a ton of money, you know, to, you know, to to other vendors or especially in some cases use some cloud native services, but they want to have control over the data. They want to control the cost and they want higher performance and they want to have, you know, there's also governance and regulatory things that they need to control better. So they want to kind of bring these services and have more control over them. Right? So now we will work very well with all of our partners including the cloud providers as well as uh, you know, an from several vendors and everybody but different customers are different kinds of needs and port works gives them the flexibility if you are a customer who want, you know, have a lot of control over your applications, the performance of the agency and want to control cars very well in leveraging existing investments board works can deliver that for you in your data center right now you can integrate it with pure slash and you get a complete solution or you won't run it in cloud and you still want to have leverage the agility of the cloud and scale for books delivers a solution for you as well. So it kind of not only protects their investment in future proves their architecture, you get future proving your architecture completely. So if you want to tear the cloud or burst the cloud, you have a great solution that you can continue to leverage >>when you hear a future proof and I'm a marketer. So I always go, I love to know what it means to different people, what does that mean to you in your environment? >>My environment. So a future proof means like one of the things we've been addressing lately, that's just a real big challenge and I'm sure it's a challenge in the industry, especially Q and A's is upgrading our clusters ability to actually maintain a consistent flow with how fast kubernetes is growing, you know, they they're out I think yes, we leverage eks so it's like 1 21 or 1 22 now, uh that effort to upgrade a cluster, it can be a daunting one with port works. We actually were able to make that to where we could actually spin up a brand new cluster and with port work shift, all our application services, data migrated completely over poor works, handles all that for us and stand up that new cluster in less than a day. And that effort, it would take us a week, two weeks to do so not even man hours the time spent there, but just the reliability of being able to do that and the cost, you know, instead of standing up a new cluster and configuring it and doing all that and spending all that time, we can just really, we move to what we call blue green cut over strategy and port works is an essential piece of that. >>So is it fair to say that there are a variety of ways that people approach port works from a, from a value perspective in terms of, I I know that one area that you are particularly good in is the area of backups in this environment, but then you get data management and there's a third kind of vector there. What is the third vector? >>Yeah, it's all of the data services. Data services, like for example, database as a service on any kubernetes cluster paid on your cloud or you're on from data centers, which >>data, what kind of databases >>you were talking about? Anything from Red is Kafka Postgres, my sequel, you know, council were supporting, we just announced something called port books, data services offering that essentially delivers all these databases as a service on any kubernetes cluster uh that that a customer can point to unless than kind of get the automated management of the database on day one to day three, the entire life cycle. Um you know, through regular communities, could curdle experience through Api and SDK s and a nice slick ui that they can, you know, just role based access control and all of that, that they can completely control their data and their applications through it. And, you know, that's the third vector of potatoes Africans >>like a question for you. So what works has been a part of peer storage? You've known it since obviously for several years before you were a c h G, you brought up to see H G, you now know it a year into being acquired by a fast paced startup. Talk to me about the relationship and some of the benefits that you're getting with port works as a part of pure storage. >>Well, I mean one of the things, you know, when, when I heard about the accusation, my first thing was I was a little bit concerned is that relationship going to change and when we were acquiring, when we're looking at a doctor and Poor works, One thing I would tell my management is poor works is not just a vendor that wants to throw a solution on you and provide some capability there, partner, they want to partner with you and your success in your journey and this whole cloud native journey to provide this rich digital experience for not only our platform engineering team, but our dev teams, but also be able to really accelerate the development of our services so we can provide that digital portal for our end users and that didn't change. If anything that accelerated that that relationship did not change. You know, I came to the cat with an issue we just, we're dealing with, he immediately got someone on the phone call with me and so that has not changed. So it's really exciting to see that now that they've been acquired that they still are very much invested in the success of their customers and making sure we're successful. You know, it's not all of a sudden I was worried I was gonna have to do a whole different support process and it's gonna go into a black hole didn't happen. They still are very much involved with their customers. And >>that sounds kind of similar to what you talked about with the cultural alignment I've known here for a long time and they're very customer centric. Sounds like one of the areas in which there was a very strong alignment with port works. >>Absolutely important works has always taken pride in being customer. First company. Our founders are heavily customer focused. Uh, you know, they are aligned. They want, they have always aligned uh, the portraits business to our customers needs. Uh Pure is a company that's men. I actually focused on customers, right? I mean, that's all, you know, purist founder cause and everybody care about and so, you know, bringing these companies together and being part of the pure team. I kind of see how synergistic it is. And you know, we have, you know, that has enabled us to serve our customers customers even better than before. >>So, I'm curious about the two of you personally, in terms of your histories, I'm going to assume that you didn't both just bounce out of high school into the world of kubernetes, right? So like lisa and I your spanning the generations between the world of, say, virtualization based on X 86 architecture and virtualization where you can have microservices, you have a full blown operating system that you're working with, that kind of talk about, you know, Michael with you first talk about what that's been like navigating that change. We were in the midst of that, Do you have advice for others that are navigating that change? >>Don't be afraid of it, you know, a lot of people want to, you know, I call it, we're moving from where we're uh naming, we still have cats and dogs, they have a name, the VMS either whether or not their physical boxes or their VMS to where it's more like it's a cattle, you know, it's like we don't own the Os and not to be afraid afraid of that because change is really good. You know, the ability for me to not have to worry about patching and operating system is huge, you know, where I can rely on someone like the chaos and and the version and allow them to, if CV comes out, they let me know I go and I use their tools to be able to upgrade. So I don't have to literally worry about owning that Os and continues the same thing. You know, you, you, you know, it's all about being fault tolerant, right? And being able to be changed where you can actually brought a new version of a container, a base image with a lot of these without having to go and catch a bunch of servers, I mean patch night was held, I'm sorry if I could say that, but it was a nightmare, you know, but this whole world has just been a game changer >>with that. So Van cut from your perspective, you were coming at it, going into a startup, looking at the landscape in the future and seeing opportunity, um what what what's that been like for you? I guess the question for you is more something lisa and I talk about this concept of peak kubernetes, where are we in the wave, is this just is this just the beginning, are we in the thick of it? >>Yeah, I think I would say we're kind of transitioning from earlier doctors too early majority face in the whole, you know, um crossing the chasm analogy. Right, so uh I would say we're still the early stages of this big wave that's going to transform how infrastructure is built, apps are, apps are built and managed and run in production. Um I think some of the uh pieces, the key pieces are falling in place and maturing, uh there are some other pieces like observe ability and security, uh you know, kind of edge use cases need to be, you know, they're kind of going to get a lot more mature and you'll see that the cloud as we know today and the apps as we know today, they're going to be radically different and you know, if you're not building your apps and your business on this modern platform, on this modern infrastructure, you're gonna be left behind. Um, you know, I, my wife's birthday was a couple of days ago. I was telling this story a couple of friends is that I r I used another flowers delivery website. Uh they missed delivering the flowers on the same day, right? So when they told me all kinds of excuses, then I just went and looked up, you know, like door dash, which delivers uh, you know, and then, you know, like your food, but there's also flower delivery, indoor dash and I don't do it, I door dash flowers to her and I can track the flower does all the way she did not eat them, okay, You need them. But my kids love the chocolates though. So, you know, the case in point is that you cannot be, you know, building a modern business without leveraging the moral toolchain and modern toolchain and how the business is going to be delivered. That that thing is going to be changing dramatically. And those kind of customer experience, if you don't deliver, uh, you're not gonna be successful in business and communities is the fundamental technology that enables these containers. It's a fundamental piece of technology that enables building new businesses, you know, modernizing existing businesses and the five G is gonna be, there's gonna be new innovations that's going to get unleashed. And uh, again, communities and containers enable us to leverage those. And so we're still scratching the surface on this, it's big now, it's going to be much, much bigger as we go to the next couple of years. >>Speaking of scratching the surface, Michael, take us out in the last 30 seconds or so with where CHG healthcare is on its digital transformation. How is port works facilitating that? >>So we're right in the thick of it. I mean we are we still have what we call the legacy, we're working on getting those. But I mean we're really moving forward um to provide that rich experience, especially with inventing driven platforms like Kafka and Kubernetes and partnering with port works is one of the key things for us with that and a W s along with that. But we're, and I remember I heard a talk and I can't, I can't remember me but he he talked about how, how kubernetes just sort of like 56 K. Modem, You're hearing it, see, but it's got to get to the point where it's just there, it's just the high speed internet and Kelsey Hightower, That's who Great. Yeah, and I really like that because that's true, you know, and that's where we're on that transition, where we're still early, it's still that 50. So you still want to hear a note, you still want to do cube Cto, you want to learn it the hard way and do all that fun stuff, but eventually it's gonna be where it's just, it's just there and it's running everything like five G. I mean stripped down doing Micro K. It's things like that, you know, we're gonna see it in a lot of other areas and just proliferate and really accelerate uh the industry and compute and memory and, and storage and >>yeah, a lot of acceleration guys, thank you. This has been a really interesting session. I always love digging into customer use cases how C H. G is really driving its evolution with port works Venkat. Thanks for sharing with us. What's going on with port works a year after the acquisition. It sounds like all good stuff. >>Thank you. Thanks for having us. It's been fun, our >>pleasure. Alright for Dave Nicholson. I'm lisa martin. You're watching the cube live from Los Angeles. This is our coverage of Yukon cloud native Con 21 mhm

>> Welcome back to theCUBE's coverage of KubeCon + CloudNativeCon 21 live form Los Angeles. Lisa Martin, with Dave Nicholson. And we've got a CUBE alum back with us. Webb Brown is back. The co-founder and CEO of Kubecost. Welcome back! >> Thank you so much. It's great to be back. It's been right at two years, a lot's happening in our community and ecosystem as well as with our open source project and company. So awesome with that. >> Give the audience an overview in case they're not familiar with Kubecost. And then talk to us about this explosive growth that you've seen since we last saw you in person. >> Yeah, absolutely. So Kubecost provides cost management solutions purpose-built for teams throwing in Kubernetes and Cloud Native. Right? So everything we do is built on open source. All of our products can be installed in minutes. We give teams visibility into spend, then help them optimize it and govern it over time. So it's been a busy two years since we last talked, we have grown the team about, you know, 5 x, so like right around 20 people today. We now have thousands of mostly medium and large sized enterprises using the product. You know, that's north of a 10 x growth since we launched just before, you know, KubeCon San Diego, now managing billions of dollars of spin and, you know, I feel like, we're just getting started. So it's an incredibly exciting time for us as a company and also just great to be back in person with our friends in the community. >> This community is such a strong community. And it's great to see people back here. I agree. >> Absolutely, absolutely. >> So Kubecost, obviously you talk about cost optimization, but it's, you really, you're an insight engine in the sense that if you're looking at costs, you have to measure that against what you're getting for that cost. >> Absolutely. So what are some of the insights that your platform or that your tool set offers. >> Yeah, absolutely, so, you know, we think about our product is first and foremost, like visibility and monitoring and then insights and optimization and then governance. You know, if you talk to most teams today, they're still kind of getting that visibility, but once you do it quickly leads in how do we optimize? And then we're going to give you insights at every part of the stack, right? So like at the infrastructure layer, thinking about things like Spot and RIS and savings plans, et cetera. At the Kubernetes orchestration layer, thinking about things like auto scaling and, you know, setting requests and limits, et cetera, all the way up to like the application layer with all of that being purpose-built for, you know, Cloud Native Kubernetes. So the way we work as you deploy our product in your environment, anywhere you're running Kubernetes, 1.11 or above we'll run. And we're going to start dynamically generating these insights in minutes and they're real time. And again, they scaled to the largest Kubernetes clusters in the world. >> And you said, you've had a thousand or so customers in the medium to large enterprise. These are large organizations, probably brand names, I imagine we are familiar with that are leaning on Kubecost to help get that visibility that before they did not have the ability to get. >> Absolutely, absolutely. So definitely our users of our thousands of users, skews heavily towards, you know, medium and large side enterprise. Working with some amazing companies like Adobe, who, you know, just have such high scale and like complex and sophisticated infrastructure. So, you know, I think this is very natural in what we expect, which is like, as you start spending more resources, you know, missing visibility, having unoptimized infrastructure starts to be more costly. >> Absolutely. >> And we typically see as once that gets into like the multiple head count, right? And it starts to, you know, spend some, may make sense to spend some time optimizing and monitoring and, you know, putting the learning in place. So you can manage it more effectively as time goes on. >> Do you have any metrics or any X factor ranges of the costs that you've actually saved customers? >> Yeah. I mean, we've saved multiple customers in them, like many of millions of dollars at this point, >> So we're talking big. >> Really big. So yeah, we're now managing more than $2 billion of spin. So like some really big savings on a per customer base, but it's really common where we're saving, you know, north of 30%, sometimes up to 70% on your Kubernetes and related spin. And so we're giving you insights into your Kubernetes cluster and again, the full stack there, but also giving you visibility and insights into external things like external disk or cloud storage buckets or, you know, cloud sequel that, that sort of stuff, external cloud services. >> Taking those blinders off >> Exactly. And giving you that unified, you know, real time picture again, that accurately reflects everything that's going on in your system. >> So when these insights are produced or revealed, are the responses automated? or are they then manually applied? >> Yeah. Yeah. That's a great question. We support both and we support both in different ways By default, when you deploy Kubecost, and again it's, today it's Helm Install. It can be running in your cluster in, you know, minutes or less, it's deployed in read only mode. And by the way, you don't share any data externally, it's all in your local environment. So we started generating these insights, you know, right when you install in your environment. >> Let me ask you about, I'm sorry to interrupt, but when you say you're generating an insight, are you just giving an answer and guidance? or you're providing the reader background on what leads to that insight? >> Yeah. You know, is that a philosophical question of, do you need to provide the user rationale for the insight? >> Yeah, absolutely. And I think we're doing this today and we'll do more, but one example is, you know, if you just look at this notion of setting requests and limits for your applications in Kubernetes, you know, if you, in simple forms, if you set a request too high, you're potentially wasting money because the Kubernetes scheduler is presenting that resource for you. If you set it too low, you're at risk of being CPU throttled, right? So communicating that symbiotic relationship and the risk on either side really helps the team understand why do I need to strike this balance, right? It's not just cost it's performance and reliability as well. So absolutely given that background and again, out of the box we're read only, but we also have automation in our product with our cluster controller. So you can dynamically do things like right-size your infrastructure, or, you know, move workloads to Spot, et cetera. But we also have integrations with a bunch of tooling in this ecosystem. So like Prometheus native, you know, Alert Manager native, just launched an integration with Spinnaker and Armory where you can like dynamically at the time of deployment, you know, right size and have insights. So you can expect to see more from us there. But we very much think about automation is twofold. One, you know, building trust in Kubecost and our insights and adopting them over time. But then two is meeting you where you are with your existing tooling, whether it's your CICB pipeline, observability or, you know, existing kind of workflow automation system. >> Meeting customers where they are is, is critical these days. >> Absolutely. I think, especially in this market, right? where we have the potential to have so much interoperability and all these things working in harmony and also, you know, there's, there's a lot of booths back here, right? So we, you know, we have complex tech stacks and, you know, in certain cases we feel like when we bring you to our UI or API's or, you know, automation or COI's, we can do things more effective. But oftentimes when we bring that data to you, we can be more effective again, that's, you know, coming, bringing your data to Chronosphere or Prometheus or Grafana, you know, all of the tooling that you're already using on a daily, regular basis. >> Bringing that data into the tool is just another example of the value in data that the organizations can actually harness that value and unlock it. >> Webb: Yeah. >> There's so much potential there for them to be more competitive, for them to be able to develop products and services faster. >> Absolutely. Yeah, I think you're just seeing the coming of age with, you know, cost metrics into that equation. We now live in a world with Kubernetes as this amazing innovation platform where as an engineer, I can go spin up some pretty costly resources, really fast, and that's a great thing for innovation, right? But it also kind of pushes some of the accountability or awareness down to the individual >> Webb: IC who needs to be aware, you know, what, you know, things generally cost at a minimum in like a directional way, so they can make informed decisions again, when they think about this cost performance, reliability, trade-off. >> Lisa: Where are your customer conversations? Are your target users, DevOps folks? I was just wondering where finance might be in this whole game. >> Yeah, it's a great question. Given the fact that we are kind of open source first and started with open source, we, you know, 95% of the time when we start working with an infrastructure engineering team or dev ops team. They've already installed our product. They're already familiar with what we're doing, but then increasingly and increasingly fast, you know, finance is being brought into the equation and, you know, management is being brought into the equation. And I think it's a function of what we were talking about where, you know, 70% of teams grew their Kubernetes spend over the last year, you know, 20% of them more than doubled. So, you know, these are starting to be real, you know, expense items where finance is increasingly aware of what's going on. So yeah, they're coming into the picture, but it's simply thought that you starting with, and, and working with the infrastructure team, that's actually kind of putting some of these insights into action or hooking us into their pipelines or something. >> When you think of developers going out and grabbing resources, and you think of a, an insight tool that looks at controlling cost, that could seem like an inhibitor. But really if you're talking about how to efficiently use whatever resources you have to be able to have access to in terms of dollars, you could sell this to the developers on that basis. It's like, look, you have these 10 things that you want to be able to do. If you don't optimize using a tool like this, you're only going to be able to do 4 of them. >> Without a doubt. Yeah. And you know, us as our founding team, all engineers, you know, we were the ones getting those questions of, you know, how have we already spent, you know, our budget on just this project? We have these three others we want to do, right? Or why are costs going up as quickly as they are? You know, what are we spending on this application, instead of that kind of being a manual lift, like, let me go do a bunch of analysis or come back with answers. It's tools to where not only can management answer those questions themselves, but like engineering teams can make informed opportunity costs and optimizations decisions itself, whether it's tooling and automation doing it for them or them applying things, you know, directly. >> Lisa: So a lot of growth. You talked about the growth on employees, the growth in revenue, what lies ahead for Kubecost? What are some of the things that are coming on the horizon that you're really excited about? >> Yeah, we very much feel like we're just getting started you know, just like we feel this ecosystem and community is, right? Like there's been tons of progress all around, but like, wow, it's still early days. So, you know, we, we did raise, you know, five and a half million dollars from, you know, First Round who is an amazing group to work with at the end of last year. So by growing the engineering team were able to do a lot more. We got a bunch of really big things coming across all parts of our product. You can think about one thing we're really excited that's in limit availability right now is our first hosted solution. It's our first SaaS solution. And this is critically important to us in that we want to give teams the option to, if you want to own and control your data and never egress anything outside of your cluster, you can do that with our deploy product. You can do that with our open source. You can truly lock down namespace to egress and never send a byte out. Or if you'd like the convenience of us to manage it for you and be kind of stewards of your data, we're going to offer, you know, a great offering there too. So that's unlimited availability day. We're going to have a lot more announcements coming there, but we see those being at feature parity, you know, between like our enterprise offerings and our hosted solution and just, you know, a lot more coming with, you know, visibility, some more like GPU insights, you know, metrics coming quickly, a lot more with automation coming and then more integrations for governance. Again, kind of talked about Spinnaker and things like that. A lot more really interesting ones coming. >> So five and a half million raised in the last round of funding. Where are you going to be applying that? What are some of the growth engines that you want to tune with that money? >> Yeah, so, you know, first and foremost, it was really growing the engineering team, right? So we've, you know, like 4 x the engineering team in the last year, and just have an amazing group of engineers. We want to continue to do that. >> Webb: We're kind of super early on the like, you know, marketing and sales side. We're going to start thinking about that more and more, you know, our approach first off was like, we want to solve a really valuable problem and doing it in a way that is super compelling. And we think that when you do that, you know, good things happen. I think that's some of our Google background, which is like, you build a great search engine and like, you know, good things generally happen. So we're just super focused on, again, working with great users, you know, building great products that meet them where they are and solve problems that are really important to them. >> Lisa: Awesome. Well, congratulations on all the trajectory of success since we last saw you in person. >> Thank you. >> Great to have you back on the show, looking forward to, so folks can go to www.kubecost.com to learn more and see some of those announcements coming down the pike. >> Absolutely, yeah. >> Don't you make it two years before you come back. >> Webb: I would love to be back. I hope we're back bigger than ever, you know, next year, but it has been such a pleasure, you know, last time and this time, thank you so much for having me, you know, I love being part of the show and the community at large. >> It's a great community and we appreciate you sharing all your insights. >> Thank you so much. >> All right. For Dave Nicholson, I'm Lisa Martin coming to you live from Los Angeles. This is theCUBE's coverage of KubeCon and CloudNativeCon 21. We back with our next guest shortly. We'll see you there.

(upbeat soft intro music) >> Hey everyone. Welcome back to theCube's live coverage from Los Angeles of KubeCon and CloudNativeCon 2021. Lisa Martin with Dave Nicholson, Dave and I are pleased to welcome our next guest remotely. Steven Huels joins us, the senior director of Cloud Services at Red Hat. Steven, welcome to the program. >> Steven: Thanks, Lisa. Good to be here with you and Dave. >> Talk to me about where you're seeing traction from an AI/ML perspective? Like where are you seeing that traction? What are you seeing? Like it. >> It's a great starter question here, right? Like AI/ML is really being employed everywhere, right? Regardless of industry. So financial services, telco, governments, manufacturing, retail. Everyone at this point is finding a use for AI/ML. They're looking for ways to better take advantage of the data that they've been collecting for these years. It really, it wasn't all that long ago when we were talking to customers about Kubernetes and containers, you know, AI/ML really wasn't a core topic where they were looking to use a Kubernetes platform to address those types of workloads. But in the last couple of years, that's really skyrocketed. We're seeing a lot of interest from existing customers that are using Red Hat open shift, which is a Kubernetes based platform to take those AI/ML workloads and take them from what they've been doing for additionally, for experimentation, and really get them into production and start getting value out of them at the end of it. >> Is there a common theme, you mentioned a number of different verticals, telco, healthcare, financial services. Is there a common theme, that you're seeing among these organizations across verticals? >> ^There is. I mean, everyone has their own approach, like the type of technique that they're going to get the most value out of. But the common theme is really that everyone seems to have a really good handle on experimentation. They have a lot of very brig data scientists, model developers that are able to take their data and out of it, but where they're all looking to get, get our help or looking for help, is to put those models into production. So ML ops, right. So how do I take what's been built on, on somebody's machine and put that into production in a repeatable way. And then once it's in production, how do I monitor it? What am I looking for as triggers to indicate that I need to retrain and how do I iterate on this sequentially and rapidly applying what would really be traditional dev ops software development, life cycle methodologies to ML and AI models. >> So Steve, we're joining you from KubeCon live at the moment. What's, what's the connection with Kubernetes and how does Kubernetes enable machine learning artificial intelligence? How does it enable it and what are some of the special considerations to in mind? >> So the immediate connection for Red Hat, is Red Hat's open shift is basically an enterprise grade Kubernetics. And so the connection there is, is really how we're working with customers and how customers in general are looking to take advantage of all the benefits that you can get from the Kubernetes platform that they've been applying to their traditional software development over the years, right? The, the agility, the ability to scale up on demand, the ability to have shared resources, to make specialized hardware available to the individual communities. And they want to start applying those foundational elements to their AI/Ml practices. A lot of data science work traditionally was done with high powered monolithic machines and systems. They weren't necessarily shared across development communities. So connecting something that was built by a data scientist, to something that then a software developer was going to put into production was challenging. There wasn't a lot of repeatability in there. There wasn't a lot of scalability, there wasn't a lot of auditability and these are all things that we know we need when talking about analytics and AI/ML. There's a lot of scrutiny put on the auditability of what you put into production, something that's making decisions that impact on whether or not somebody gets a loan or whether or not somebody is granted access to systems or decisions that are made. And so that the connection there is really around taking advantage of what has proven itself in kubernetes to be a very effective development model and applying that to AI/ML and getting the benefits in being able to put these things into production. >> Dave: So, so Red Hat has been involved in enterprises for a long time. Are you seeing most of this from a Kubernetes perspective, being net new application environments or are these extensions of what we would call legacy or traditional environments. >> They tend to be net new, I guess, you know, it's, it's sort of, it's transitioned a little bit over time. When we first started talking to customers, there was desire to try to do all of this in a single Kubernetes cluster, right? How can I take the same environment that had been doing our, our software development, beef it up a little bit and have it applied to our data science environment. And over time, like Kubernetes advanced rights. So now you can actually add labels to different nodes and target workloads based on specialized machinery and hardware accelerators. And so that has shifted now toward coming up with specialized data science environments, but still connecting the clusters in that's something that's being built on that data science environment is essentially being deployed then through, through a model pipeline, into a software artifact that then makes its way into an application that that goes live. And, and really, I think that that's sensible, right? Because we're constantly seeing a lot of evolution in, in the types of accelerators, the types of frameworks, the types of libraries that are being made available to data scientists. And so you want the ability to extend your data science cluster to take advantage of those things and to give data scientists access to that those specialized environments. So they can try things out, determine if there's a better way to, to do what they're doing. And then when they find out there is, be able to rapidly roll that into your production environment. >> You mentioned the word acceleration, and that's one of the words that we talk about when we talk about 2020, and even 2021, the acceleration in digital transformation that was necessary really a year and a half ago, for companies to survive. And now to be able to pivot and thrive. What are you seeing in terms of customers appetites for, for adopting AI/ML based solutions? Has it accelerated as the pandemic has accelerated digital transformation. >> It's definitely accelerated. And I think, you know, the pandemic probably put more of a focus for businesses on where can they start to drive more value? How can they start to do more with less? And when you look at systems that are used for customer interactions, whether they're deflecting customer cases or providing next best action type recommendations, AI/ML fits the bill there perfectly. So when they were looking to optimize, Hey, where do we put our spend? What can help us accelerate and grow? Even in this virtual world we're living in, AI/ML really floated to the top there, that's definitely a theme that we've seen. >> Lisa: Is there a customer example that you think that you could mention that really articulates the value over that? >> You know, I think a lot of it, you know, we've published one specifically around HCA health care, and this had started actually before the pandemic, but I think especially, it's applicable because of the nature of what a pandemic is, where HCA was using AI/ML to essentially accelerate diagnosis of sepsis, right. They were using it for, for disease diagnoses. That same type of, of diagnosis was being applied to looking at COVID cases as well. And so there was one that we did in Canada with, it's called 'how's your flattening', which was basically being able to track and do some predictions around COVID cases in the Canadian provinces. And so that one's particularly, I guess, kind of close to home, given the nature of the pandemic, but even within Red Hat, we started applying a lot more attention to how we could help with customer support cases, right. Knowing that if folks were going to be out with any type of illness. We needed to be able to be able to handle that case, you know, workload without negatively impacting work-life balance for, for other associates. So we looked at how can we apply AI/ML to help, you know, maintain and increase the quality of customer service we were providing. >> it's a great use case. Did you have a keynote or a session, here at KubeCon CloudNative? >> I did. I did. And it really focused specifically on that whole ML ops and model ops pipeline. It was called involving Kubernetes and bracing model ops. It was for a Kubernetes AI day. I believe it aired on Wednesday of this week. Tuesday, maybe. It all kind of condenses in the virtual world. >> Doesn't it? It does. >> So one of the questions that Lisa and I have for folks where we sit here, I don't know, was it year seven or so of the Dawn of Kubernetes, if I have that, right. Where do you think we are, in this, in this wave of adoption, coming from a Red Hat perspective, you have insight into, what's been going on in enterprises for the last 20 plus years. Where are we in this wave? >> That's a great question. Every time, like you, it's sort of that cresting wave sort of, of analogy, right? That when you get to top one wave, you notice the next wave it's even bigger. I think we've certainly gotten to the point where, where organizations have accepted that Kubernetes can, is applicable across all the workloads that they're looking to put in production. Now, the focus has shifted on optimizing those workloads, right? So what are the things that we need to run in our in-house data centers? What are things that we need, or can benefit from using commodity hardware from one of the hyperscalers, how do we connect those environments and more effectively target workloads? So if I look at where things are going to the future, right now, we see a lot of things being targeted based on cluster, right? We say, Hey, we have a data science cluster. It has characteristics because of X, Y, and Z. And we put all of our data science workloads into that cluster. In the future, I think we want to see more workload specific, type of categorization of workloads so that we're able to match available hardware with workloads rather than targeting a workload at a specific cluster. So a developer or data scientist can say, Hey, my particular algorithm here needs access to GPU acceleration and the following frameworks. And then it, the Kubernetes scheduler is able to determine of the available environments. What's the capacity, what are the available resources and match it up accordingly. So we get into a more dynamic environment where the developers and those that are actually building on top of these platforms actually have to know less and less about the clusters they're running on. It just have to know what types of resources they need access to. >> Lisa: So sort of democratizing that. Steve, thank you for joining Dave and me on the program tonight, talking about the traction that you're seeing with AI/ML, Kubernetes as an enabler, we appreciate your time. >> Thank you. >> Thanks Steve. >> For Dave Nicholson. I'm Lisa Martin. You're watching theCube live from Los Angeles KubeCon and CloudNativeCon 21. We'll be right back with our next guest. (subtle music playing) >> Lisa: I have been in the software and technology industry for over 12 years now. So I've had the opportunity as a marketer to really understand and interact with customers across the entire buyer's journey. Hi, I'm Lisa Martin and I'm a host of theCube. Being a host on the cube has been a dream of mine for the last few years. I had the opportunity to meet Jeff and Dave and John at EMC World a few years ago and got the courage up to say, Hey, I'm really interested in this. I love talking with customers...

welcome back to la we are live in los angeles at kubecon cloudnativecon 21 lisa martin and dave nicholson we've been talking to folks all day great to be here in person about 2 700 folks are here the kubernetes the community the cncf community is huge 138 000 folks great to see some of them in person back collaborating once again dave and i are pleased to welcome our next guest we have suresh ragaram co-founder and ceo of platform 9. sarish welcome to the program thank you for having me it's a pleasure to be here give our audience an overview of platform 9 who are you guys what do you do when were you founded all that good stuff so we are about seven years old we were founded with a mission to make it easy to run private hybrid and edge clouds my co-founders and i were early engineers at vmware and what we realized is that it's really easy to go use the public cloud because the public clouds have this innovation which is they have a control plane which serves as a it serves as a foundation for them to launch a lot of services and make that really simple and easy to use but if you need to get that experience in a private cloud or a hybrid cloud or in the edge nobody gives you that cloud control plane you get it from amazon in amazon get it from azure in azure google and google who gives you a sas cloud control plane to run private clouds or edge clouds or hybrid clouds nobody and this is uh this is what we do so this is we make it easy to run these clouds using technologies like kubernetes with our our sas control plane now is it limited to kubernetes because when you you you mentioned your background at vmware uh is this a control plane for what people would think of as private clouds using vmware style abstraction or is this primarily cloud native so when we first started actually docker did not exist like okay so at the time our first product to market was actually an infrastructure service product and at the time we looked at what is what is out there we knew vmware vsphere was out there it's a vmware technology there was apache cloud stack and openstack and we had look the open ecosystem around vms and infrastructure as a service is openstack so we chose open source as the lingua franca for the service endpoint so our control plane we deliver openstack as a service that was our first product when kubernetes when the announcement of communities came out from google we knew at that time we're going to go launch because we'd already been studying lxc and and docker we knew at the time we're going to standardize on kubernetes because we believe that an open ecosystem was forming around that that was a big bet for us you know this this this foundation and this this community is proof that that was a good bet and today that's actually a flap flagship product it's our you know the biggest biggest share of revenue biggest share of install base uh but we do have more than one product we have openstack as a service we have bare metal as a service we have containers as a service with kubernetes i want to ask you some of the the i'm looking at your website here platform9.com some of the three marketing messages i want you to break these down for me simplify day two ops multi-cloud ready on day one and we know so many businesses are multi-cloud and percentage is only going up and faster time to market talk to me about this let's start with simplified day two ops how do you enable that so you know one of the biggest if you talk to anyone who runs like a large vmware environment and you ask them when was the last time you did an upgrade or for that matter somebody who's running like a large-scale kubernetes environment or an openstack environment uh probably in a private cloud deployment awesome when was the last time you did an upgrade how did that go when was the last time you had an outage who did you call how did that go right and you'll hear an outpouring of emotion okay same thing you go ask people when you use kubernetes in the public cloud how do these things work and they'll say it's pretty easy it's not that hard and so the question the idea of platform 9 is why is there such a divide there's this you know we talk about digital divide there is a cloud divide the public clouds have figured out something that the rest of the industry has not and people suffer with private clouds there's a lot of demand for private clouds very few people can make it work because they try to do it with a lot of like handheld tools and you know limited automation skills and scripting what you need is you need the automation that makes sure that ongoing troubleshooting 24x7 alerting upgrades to new versions are all fully managed when amazon doesn't upgrade to a new version people don't have to worry about it they don't have to stay up at night they don't deal with outages you shouldn't have to deal with that in your private cloud so those are the kinds of problems right the troubleshooting the upgrades the the remediation when things go wrong that are taken for granted in the public cloud that we bring to the customers who want to run them in private or hybrid or edge cloud environments how do you help customers and what does future proofing mean like how do you help customers future proof their cloud native journey what does that mean to platform 9 and what does that mean to your customers i'll give you one of my favorite stories is actually one of our early customers is snapfish it's a photo sharing company it's a consumer company right when they got started with us they were coming off of vmware they wanted to run an openstack environment they started nearly four years ago and they started using us with openstack and vms and infrastructure as a service fast forward to today 85 percent of the usage on us is containers and they didn't have to hire openstack experts nor do they have to hire kubernetes experts but their application development teams got went from moving from a somewhat legacy vmware style id environment to a modern self-service developer experience with openstack and then to containers and kubernetes and we're gonna we're gonna work on the next generation of innovation with serverless technologies simplifying you know building modern more elastic applications and so our control plane the beauty of our model is our control plane adds value it added value with openstack it added value with kubernetes it'll add value with what's next around the evolution of serverless technologies right it's evergreen and our customers get the benefit of all of that so when you talk about managing environments that are on premises and in clouds i assume you're talking hyperscale clouds like aws azure gcp um what kind of infrastructure needs to be deployed and when i say infrastructure that's can be software what needs to be deployed in say aws for this to work what does it look like so some 30 of our users use us on in the public cloud and the majority of that actually happens in aws uh because they're the number one cloud and we really give people three choices right so they can choose to use and consume aws the way they want to so we have a small minority of customers that actually provisions bare metal servers in aws that's a small minority because the specific use cases they're trying to do and they try to deploy like kubernetes on bare metal but the bare metal happens to be running on aws okay that's a small minority a larger majority of our users in aws or some hyperscale cloud brings their vpc under management so they come in get started sign up with platform 9 in their platform 9 control plane they go and say i want to plug in this vpc and i want to give you this much authorization to this vpc and in that vpc we essentially can impersonate them and on their behalf provision nodes and provision clusters using our communities open source kubernetes upstream cncf kubernetes but we also have customers that said hey i already have some clusters with eks i really like what the rest of your platform allows me to do and i think it's a better platform for me to use for a variety of reasons can you bring my eks clusters under management and then help me provision new new clusters on top and the answer is you can so you can choose to bring your bare metal you can choose to bring your vpc and just provision like virtual machine and treat them as nodes for communities clusters or you can bring pre-built kubernetes clusters and manage them using our management uh product what are your routes to market so we have three routes to market um we have a completely self-serve completely free forever uh experience where people can just go sign up log in get access to the control plane and be up and running within minutes right they can plug in their server hardware on premises at the edge in the cloud their vpcs and they can be up and running from there they can choose to upgrade upsell into a grow into an uh growth tier or you know choose to request for more support and a higher touch experience and work with our sales team and get into an enterprise tier and our that is our second go to market which is a direct go to market uh companies in the retail space companies tech companies uh companies in fintech companies that are investing in digital transformation a big way have lots of software developers and are adopting these technologies in a big way but want private or hybrid or edge clouds that's the second go to market the third and and in the last two years this is new to us really exciting go to market to us is a partner partner let go to market where partners like rackspace have oem platform line so we have a partnership d partnership with rackspace all of rackspace's customers and they install base essentially including customers who are consuming public cloud services wire rackspace get access to platform 9 and rackspace working together with rackspace's ability to kind of service the whole mile uh and also uh we have a very important partnership with maveneer in the 5g space so 5g we think is a large opportunity and there's a there's a joint product there called maven webscape platform to run 5g networks on our community stack so platform nine why what does that mean harry potter harry potter so it's platform nine and three quarters okay we had this realization my cofounders and i were at vmware for 10 for 10 15 years and we were struggling with this problem of why is the public cloud so easy to use why is it so hard to run a private cloud and even today i think not many people realize uh and that's the analogy to platform nine and three quarters it's like it's right in the middle of king's cross station you go through it and you enter the whole new world of magic that that secret door that platform nine and three quarters is a sas control plane that is a secret sauce that amazon has and azure has and google has and we're bringing that for anybody who wants to use it on any infrastructure of their choice where can customers go to learn more about platform nine so platform nine dot com uh follow us on twitter platform line says or on linkedin you know and if any of our viewers are here at kubecon they can stop by your booth what are some of the things that you're featuring there we are at the booth we have our product managers we have our support engineers we have the people that are actually doing the real work behind the product right there we're talking about our roadmap we're talking about the product demos we're doing like specific show talks on specific deep dives in our product and we're also talking about some some really cool things that are coming up in the garage uh in the in the next six months can you leave us with any teasers about what some of the cool things are that are coming up in the garage yeah one one one thing that is a really big deal is um uh is the ability to manage kubernetes clusters as as as cattle right kubernetes makes node management and app management lets you treat them as cattle instead of pets but kubernetes clusters themselves our customers tell us like even in amazon eks and others these clusters themselves become pets and they become hard to manage so we have a really really interesting capability to manage these as more as you know from infrastructure code with githubs uh as cattle we actually have an announcement that i'm not able to share at this point which is coming out in two weeks uh in the ed space so you'll have to stay tuned for that so folks can go to platformnine.com.com check out that announcement two weeks two weeks from now by the end of october that's right awesome sharers thank you so much for joining us i love the fact that you asked that question because i kept thinking platform nine where do i know that from and i just googled harry potter that's right from nine and five dying because i didn't automatically make the correlation because my son and i are the most unbelievable potterheads ever yeah well so we have that in common that's fantastic awesome thank you for joining us sharing what platform mine is some of the exciting stuff coming out and two weeks learn to hear some great news about the edge absolutely awesome thank you for joining us my pleasure thank you for having me uh our pleasure as well for dave nicholson i'm lisa martin live in los angeles thecube is covering kubecon cloudnativecon21 stick around we'll be right back with our next guest