>>Hello everyone and welcome back to Motor City, Michigan. We're live from the Cube and my name is Savannah Peterson. Joined this afternoon with my co-host John Ferer. John, how you doing? Doing >>Great. This next segment's gonna be awesome about application modernization, scaling pluses. This is what's gonna, how are the next generation software revolution? It's gonna be >>Fun. You know, it's kind of been a theme of our day today is scale. And when we think about the complex orchestration platform that is Kubernetes, everyone wants to scale faster, quicker, more efficiently, and our guests are here to tell us all about that. Please welcome to Char and Andy, thank you so much for being here with us. You were on the Red Hat OpenShift team. Yeah. I suspect most of our audience is familiar, but just in case, let's give 'em a quick one-liner pitch so everyone's on the same page. Tell us about OpenShift. >>I, I'll take that one. OpenShift is our ES platform is our ES distribution. You can consume it as a self-managed platform or you can consume it as a managed service on on public clouds. And so we just call it all OpenShift. So it's basically Kubernetes, but you know, with a CNCF ecosystem around it to make things more easier. So maybe there's two >>Lights. So what does being at coupon mean for you? How does it feel to be here? What's your initial takes? >>Exciting. I'm having a fantastic time. I haven't been to coupon since San Diego, so it's great to be back in person and see old friends, make new friends, have hallway conversations. It's, it's great as an engineer trying to work in this ecosystem, just being able to, to be in the same place with these folks. >>And you gotta ask, before we came on camera, you're like, this is like my sixth co con. We were like, we're seven, you know, But that's a lot of co coupons. It >>Is, yes. I mean, so what, >>Yes. >>Take us status >>For sure. Where we are now. Compare and contrast co. Your first co con, just scope it out. What's the magnitude of change? If you had to put a pin on that, because there's a lot of new people coming in, they might not have seen where it's come from and how we got here is maybe not how we're gonna get to the next >>Level. I've seen it grow tremendously since the first one I went to, which I think was Austin several years ago. And what's great is seeing lots of new people interested in contributing and also seeing end users who are trying to figure out the best way to take advantage of this great ecosystem that we have. >>Awesome. And the project management side, you get the keys to the Kingdom with Red Hat OpenShift, which has been successful. Congratulations by the way. Thank you. We watched that grow and really position right on the wave. It's going great. What's the update on on the product? Kind of, you're in a good, good position right now. Yeah, >>No, we we're feeling good about it. It's all about our customers. Obviously the fact that, you know, we have thousands of customers using OpenShift as the cloud native platform, the container platform. We're very excited. The great thing about them is that, I mean you can go to like OpenShift Commons is kind of a user group that we run on the first day, like on Tuesday we ran. I mean you should see the number of just case studies that our customers went through there, you know? And it is fantastic to see that. I mean it's across so many different industries, across so many different use cases, which is very exciting. >>One of the things we've been reporting here in the Qla scene before, but here more important is just that if you take digital transformation to the, to its conclusion, the IT department and developers, they're not a department to serve the business. They are the business. Yes. That means that the developers are deciding things. Yeah. And running the business. Prove their code. Yeah. Okay. If that's, if that takes place, you gonna have scale. And we also said on many cubes, certainly at Red Hat Summit and other ones, the clouds are distributed computer, it's distributed computing. So you guys are focusing on this project, Andy, that you're working on kcp. >>Yes. >>Which is, I won't platform Kubernetes platform for >>Control >>Planes. Control planes. Yes. Take us through, what's the focus on why is that important and why is that relate to the mission of developers being in charge and large scale? >>Sure. So a lot of times when people are interested in developing on Kubernetes and running workloads, they need a cluster of course. And those are not cheap. It takes time, it takes money, it takes resources to get them. And so we're trying to make that faster and easier for, for end users and everybody involved. So with kcp, we've been able to take what looks like one normal Kubernetes and partition it. And so everybody gets a slice of it. You're an administrator in your little slice and you don't have to ask for permission to install new APIs and they don't conflict with anybody else's APIs. So we're really just trying to make it super fast and make it super flexible. So everybody is their own admin. >>So the developer basically looks at it as a resource blob. They can do whatever they want, but it's shared and provisioned. >>Yes. One option. It's like, it's like they have their own cluster, but you don't have to go through the process of actually provisioning a full >>Cluster. And what's the alternative? What's the what's, what's the, what's the benefit and what was the alternative to >>This? So the alternative, you spin up a full cluster, which you know, maybe that's three control plane nodes, you've got multiple workers, you've got a bunch of virtual machines or bare metal, or maybe you take, >>How much time does that take? Just ballpark. >>Anywhere from five minutes to an hour you can use cloud services. Yeah. Gke, E Ks and so on. >>Keep banging away. You're configuring. Yeah. >>Those are faster. Yeah. But it's still like, you still have to wait for that to happen and it costs money to do all of that too. >>Absolutely. And it's complex. Why do something that's been done, if there's a tool that can get you a couple steps down the path, which makes a ton of sense. Something that we think a lot when we're talking about scale. You mentioned earlier, Tohar, when we were chatting before the cams were alive, scale means a lot of different things. Can you dig in there a little bit? >>Yeah, I >>Mean, so when, when >>We talk about scale, >>We are talking about from a user perspective, we are talking about, you know, there are more users, there are more applications, there are more workloads, there are more services being run on Kubernetes now, right? So, and OpenShift. So, so that's one dimension of this scale. The other dimension of the scale is how do you manage all the underlying infrastructure, the clusters, the name spaces, and all the observability data, et cetera. So that's at least two levels of scale. And then obviously there's a third level of scale, which is, you know, there is scale across not just different clouds, but also from cloud to the edge. So there is that dimension of scale. So there are several dimensions of this scale. And the one that again, we are focused on here really is about, you know, this, the first one that I talk about is a user. And when I say user, it could be a developer, it could be an application architect, or it could be an application owner who wants to develop Kubernetes applications for Kubernetes and wants to publish those APIs, if you will, and make it discoverable and then somebody consumes it. So that's the scale we are talking about >>Here. What are some of the enterprise, you guys have a lot of customers, we've talked to you guys before many, many times and other subjects, Red Hat, I mean you guys have all the customers. Yeah. Enterprise, they've been there, done that. And you know, they're, they're savvy. Yeah. But the cloud is a whole nother ballgame. What are they thinking about? What's the psychology of the customer right now? Because now they have a lot of choices. Okay, we get it, we're gonna re-platform refactor apps, we'll keep some legacy on premises for whatever reasons. But cloud pretty much is gonna be the game. What's the mindset right now of the customer base? Where are they in their, in their psych? Not the executive, but more of the the operators or the developers? >>Yeah, so I mean, first of all, different customers are at different levels of maturity, I would say in this. They're all on a journey how I like to describe it. And in this journey, I mean, I see a customers who are really tip of the sphere. You know, they have containerized everything. They're cloud native, you know, they use best of tools, I mean automation, you know, complete automation, you know, quick deployment of applications and all, and life cycle of applications, et cetera. So that, that's kind of one end of this spectrum >>Advanced. Then >>The advances, you know, and, and I, you know, I don't, I don't have any specific numbers here, but I'd say there are quite a few of them. And we see that. And then there is kind of the middle who are, I would say, who are familiar with containers. They know what app modernization, what a cloud application means. They might have tried a few. So they are in the journey. They are kind of, they want to get there. They have some other kind of other issues, organizational or talent and so, so on and so forth. Kinds of issues to get there. And then there are definitely the quota, what I would call the lag arts still. And there's lots of them. But I think, you know, Covid has certainly accelerated a lot of that. I hear that. And there is definitely, you know, more, the psychology is definitely more towards what I would say public cloud. But I think where we are early also in the other trend that I see is kind of okay, public cloud great, right? So people are going there, but then there is the so-called edge also. Yeah. That is for various regions. You, you gotta have a kind of a regional presence, a edge presence. And that's kind of the next kind of thing taking off here. And we can talk more >>About it. Yeah, let's talk about that a little bit because I, as you know, as we know, we're very excited about Edge here at the Cube. Yeah. What types of trends are you seeing? Is that space emerges a little bit more firmly? >>Yeah, so I mean it's, I mean, so we, when we talk about Edge, you're talking about, you could talk about Edge as a, as a retail, I mean locations, right? >>Could be so many things edges everywhere. Everywhere, right? It's all around us. Quite literally. Even on the >>Scale. Exactly. In space too. You could, I mean, in fact you mentioned space. I was, I was going to >>Kinda, it's this world, >>My space actually Kubernetes and OpenShift running in space, believe it or not, you know, So, so that's the edge, right? So we have Industrial Edge, we have Telco Edge, we have a 5g, then we have, you know, automotive edge now and, and, and retail edge and, and more, right? So, and space, you know, So it's very exciting there. So the reason I tag back to that question that you asked earlier is that that's where customers are. So cloud is one thing, but now they gotta also think about how do I, whatever I do in the cloud, how do I bring it to the edge? Because that's where my end users are, my customers are, and my data is, right? So that's the, >>And I think Kubernetes has brought that attention to the laggards. We had the Laed Martin on yesterday, which is an incredible real example of Kubernetes at the edge. It's just incredible story. We covered it also wrote a story about it. So compelling. Cuz it makes it real. Yes. And Kubernetes is real. So then the question is developer productivity, okay, Things are starting to settle in. We've got KCP scaling clusters, things are happening. What about the tool chains? And how do I develop now I got scale of development, more code coming in. I mean, we are speculating that in the future there's so much code in open source that no one has to write code anymore. Yeah. At some point it's like this gluing things together. So the developers need to be productive. How are we gonna scale the developer equation and eliminate the, the complexity of tool chains and environments. Web assembly is super hyped up at this show. I don't know why, but sounds good. No one, no one can tell me why, but I can kind of connect the dots. But this is a big thing. >>Yeah. And it's fitting that you ask about like no code. So we've been working with our friends at Cross Plain and have integrated with kcp the ability to no code, take a whole bunch of configuration and say, I want a database. I want to be a, a provider of databases. I'm in an IT department, there's a bunch of developers, they don't wanna have to write code to create databases. So I can just take, take my configuration and make it available to them. And through some super cool new easy to use tools that we have as a developer, you can just say, please give me a database and you don't have to write any code. I don't have to write any code to maintain that database. I'm actually using community tooling out there to get that spun up. So there's a lot of opportunities out there. So >>That's ease of use check. What about a large enterprise that's got multiple tool chains and you start having security issues. Does that disrupt the tool chain capability? Like there's all those now weird examples emerging, not weird, but like real plumbing challenges. How do you guys see that evolving with Red >>Hat and Yeah, I mean, I mean, talking about that, right? The software, secure software supply chain is a huge concern for everyone after, especially some of the things that have happened in the past few >>Years. Massive team here at the show. Yeah. And just within the community, we're all a little more aware, I think, even than we were before. >>Before. Yeah. Yeah. And, and I think the, so to step back, I mean from, so, so it's not just even about, you know, run time vulnerability scanning, Oh, that's important, but that's not enough, right? So we are talking about, okay, how did that container, or how did that workload get there? What is that workload? What's the prominence of this workload? How did it get created? What is in it? You know, and what, what are, how do I make, make sure that there are no unsafe attack s there. And so that's the software supply chain. And where Red Hat is very heavily invested. And as you know, with re we kind of have roots in secure operating system. And rel one of the reasons why Rel, which is the foundation of everything we do at Red Hat, is because of security. So an OpenShift has always been secure out of the box with things like scc, rollbacks access control, we, which we added very early in the product. >>And now if you kind of bring that forward, you know, now we are talking about the complete software supply chain security. And this is really about right how from the moment the, the, the developer rights code and checks it into a gateway repository from there on, how do you build it? How do you secure it at each step of the process, how do you sign it? And we are investing and contributing to the community with things like cosign and six store, which is six store project. And so that secures the supply chain. And then you can use things like algo cd and then finally we can do it, deploy it onto the cluster itself. And then we have things like acs, which can do vulnerability scanning, which is a container security platform. >>I wanna thank you guys for coming on. I know Savannah's probably got a last question, but my last question is, could you guys each take a minute to answer why has Kubernetes been so successful today? What, what was the magic of Kubernetes that made it successful? Was it because no one forced it? Yes. Was it lightweight? Was it good timing, right place at the right time community? What's the main reason that Kubernetes is enabling all this, all this shift and goodness that's coming together, kind of defacto unifies people, the stacks, almost middleware markets coming around. Again, not to use that term middleware, but it feels like it's just about to explode. Yeah. Why is this so successful? I, >>I think, I mean, the shortest answer that I can give there really is, you know, as you heard the term, I think Satya Nala from Microsoft has used it. I don't know if he was the original person who pointed, but every company wants to be a software company or is a software company now. And that means that they want to develop stuff fast. They want to develop stuff at scale and develop at, in a cloud native way, right? You know, with the cloud. So that's, and, and Kubernetes came at the right time to address the cloud problem, especially across not just one public cloud or two public clouds, but across a whole bunch of public clouds and infrastructure as, and what we call the hybrid clouds. I think the ES is really exploded because of hybrid cloud, the need for hybrid cloud. >>And what's your take on the, the magic Kubernetes? What made it, what's making it so successful? >>I would agree also that it came about at the right time, but I would add that it has great extensibility and as developers we take it advantage of that every single day. And I think that the, the patterns that we use for developing are very consistent. And I think that consistency that came with Kubernetes, just, you have so many people who are familiar with it and so they can follow the same patterns, implement things similarly, and it's just a good fit for the way that we want to get our software out there and have, and have things operate. >>Keep it simple, stupid almost is that acronym, but the consistency and the de facto alignment Yes. Behind it just created a community. So, so then the question is, are the developers now setting the standards? That seems like that's the new way, right? I mean, >>I'd like to think so. >>So I mean hybrid, you, you're touching everything at scale and you also have mini shift as well, right? Which is taking a super macro micro shift. You ma micro shift. Oh yeah, yeah, exactly. It is a micro shift. That is, that is fantastic. There isn't a base you don't cover. You've spoken a lot about community and both of you have, and serving the community as well as your engagement with them from a, I mean, it's given that you're both leaders stepping back, how, how Community First is Red Hat and OpenShift as an organization when it comes to building the next products and, and developing. >>I'll take and, and I'm sure Andy is actually the community, so I'm sure he'll want to a lot of it. But I mean, right from the start, we have roots in open source. I'll keep it, you know, and, and, and certainly with es we were one of the original contributors to Kubernetes other than Google. So in some ways we think about as co-creators of es, they love that. And then, yeah, then we have added a lot of things in conjunction with the, I I talk about like SCC for Secure, which has become part security right now, which the community, we added things like our back and other what we thought were enterprise features needed because we actually wanted to build a product out of it and sell it to customers where our customers are enterprises. So we have worked with the community. Sometimes we have been ahead of the community and we have convinced the community. Sometimes the community has been ahead of us for other reasons. So it's been a great collaboration, which is I think the right thing to do. But Andy, as I said, >>Is the community well set too? Are well said. >>Yes, I agree with all of that. I spend most of my days thinking about how to interact with the community and engage with them. So the work that we're doing on kcp, we want it to be a community project and we want to involve as many people as we can. So it is a heavy focus for me and my team. And yeah, we we do >>It all the time. How's it going? How's the project going? You feel good >>About it? I do. It is, it started as an experiment or set of prototypes and has grown leaps and bounds from it's roots and it's, it's fantastic. Yeah. >>Controlled planes are hot data planes control planes. >>I >>Know, I love it. Making things work together horizontally scalable. Yeah. Sounds like cloud cloud native. >>Yeah. I mean, just to add to it, there are a couple of talks that on KCP at Con that our colleagues s Stephan Schemanski has, and I, I, I would urge people who have listening, if they have, just Google it, if you will, and you'll get them. And those are really awesome talks to get more about >>It. Oh yeah, no, and you can tell on GitHub that KCP really is a community project and how many people are participating. It's always fun to watch the action live to. Sure. Andy, thank you so much for being here with us, John. Wonderful questions this afternoon. And thank all of you for tuning in and listening to us here on the Cube Live from Detroit. I'm Savannah Peterson. Look forward to seeing you again very soon.

>>Hey everybody. Welcome back. Good afternoon. Lisa Martin here with John Feer live in Detroit, Michigan. We are at Coon Cloud Native Con 2020s North America. John Thank is who. This is nearing the end of our second day of coverage and one of the things that has been breaking all day on this show is news. News. We have more news to >>Break next. Yeah, this next segment is a company we've been following. They got some news we're gonna get into. Managing Kubernetes life cycle has been a huge challenge when you've got large organizations, whether you're spinning up and scaling scale is the big story. Kubernetes is the center of the conversation. This next segment's gonna be great. It >>Is. We've got two guests from Specter Cloud here. Please welcome. It's CEO Chenery Fu and co-founder and it's c g a co-founder Sta Mallek. Guys, great to have you on the program. Thank >>You for having us. My pleasure. >>So Timary, what's going on? What's the big news? >>Yeah, so we just announced our Palace three this morning. So we add a bunch, a new functionality. So first of all we have a Nest cluster. So enable enterprise to easily provide Kubernete service even on top of their existing clusters. And secondly, we also support seamlessly migration for their existing cluster. We enable them to be able to migrate their cluster into our CNC for upstream Kubernete distro called Pallet extended Kubernetes, GX K without any downtime. And lastly, we also add a lot of focus on developer experience. Those additional capability enable developer to easily onboard and and deploy the application for. They have test and troubleshooting without, they have to have a steep Kubernetes lending curve. >>So big breaking news this morning, pallet 3.0. So you got the, you got the product. This is a big theme here. Developer productivity, ease of use is the top story here. As developers are gonna increase their code velocity cuz they're under a lot of pressure. This infrastructure's getting smarter. This is a big part of managing it. So the toil is now moving to the ops. Steves are now dev teams. Security, you gotta enable faster deployment of apps and code. This is what you guys solve while you getting this right. Is that, take us through that specific value proposition. What's the, what are the key things on in this news release? Yeah, >>You're exactly right. Right. So we basically provide our solution to platform engineering ship so that they can use our platform to enable Kubernetes service to serve their developers and their application ship. And then in the meantime, the developers will be able to easily use Kubernetes or without, They have to learn a lot of what Kubernetes specific things like. So maybe you can get in some >>Detail. Yeah. And absolutely the detail about it is there's a big separation between what operations team does and the development teams that are using the actual capabilities. The development teams don't necessarily to know the internals of Kubernetes. There's so much complexity when it comes, comes into it. How do I do things like deployment pause manifests just too much. So what our platform does, it makes it really simple for them to say, I have a containerized application, I wanna be able to model it. It's a really simple profile and from there, being able to say, I have a database service. I wanna attach to it. I have a specific service. Go run it behind the scenes. Does it run inside of a Nest cluster? Which we'll talk into a little bit. Does it run into a host cluster? Those are happen transparently for >>The developer. You know what I love about this? What you guys are doing in the news, it really points out what I love about DevOps. Because cloud, let's face a cloud early adopters, we're all the hardcore cloud folks as it goes mainstream. With Kubernetes, you start to see like words like platform engineering. I mean I love that term. That means as a platform, it's been around for a while. For people who are building their own stuff, that means it's gonna scale and enable people to enable value, build on top of it, move faster. This platform engineering is becoming now standard in enterprises. It wasn't like that before. What's your eyes reactions that, How do you see that evolving faster? Or do you believe that or what's your take on >>It? Yeah, so I think it's starting from the DevOps op team, right? That every application team, they all try to deploy and manage their application under their own ING infrastructure. But very soon all these each application team, they start realize they have to repeatedly do the same thing. So these will need to have a platform engineering team to basically bring some of common practice to >>That. >>And some people call them SREs like and that's really platform >>Engineering. It is, it is. I mean, you think about like Esther ability to deploy your applications at scale and monitoring and observability. I think what platform engineering does is codify all those best practices. Everything when it comes about how you monitor the actual applications. How do you do c i CD your backups? Instead of not having every single individual development team figuring how to do it themselves. Platform engineer is saying, why don't we actually build policy that we can provide as a service to different development teams so that they can operate their own applications at scale. >>So launching Pellet 3.0 today, you also had a launch in September, so just a few weeks ago. Talk about what these two announcements mean from Specter Cloud's perspective in terms of proof points, what you're delivering to the end users and the value that they're getting from that. >>Yeah, so our goal is really to help enterprise to deploy and around Kubernetes anywhere, right? Whether it's in cloud data center or even at Edge locations. So in September we also announce our HV two capabilities, which enable very easy deployment of Edge Kubernetes, right at at at any any location, like a retail stores restaurant, so on and so forth. So as you know, at Edge location, there's no cloud endpoint there. It's not easy to directly deploy and manage Kubernetes. And also at Edge location there's not, it's not as secure as as cloud or data center environment. So how to make the end to end system more secure, right? That it's temper proof, that is also very, very important. >>Right. Great, great take there. Thanks for explaining that. I gotta ask cuz I'm curious, what's the secret sauce? Is it nested clusters? What's, what's the core under the hood here on 3.0 that people should know about it's news? It's what's, what's the, what's that post important >>To? To be honest, it's about enabling developer velocity. Now how do you enable developer velocity? It's gonna be able for them to think about deploying applications without worrying about Kubernetes being able to build this application profiles. This NEA cluster that we're talking about enables them, they get access to it in complete cluster within seconds. They're essentially having access to be able to add any operations, any capabilities without having the ability to provision a cluster on inside of infrastructure. Whether it's Amazon, Google, or OnPrem. >>So, and you get the dev engine too, right? That that, that's a self-service provisioning in for environments. Is that, Yeah, >>So the dev engine itself are the capabilities that we offer to developers so that they can build these application profiles. What the application profiles, again they define aspects about, my application is gonna be a container, it's gonna be a database service, it's gonna be a helm chart. They define that entire structure inside of it. From there they can choose to say, I wanna deploy this. The target environment, whether it becomes an actual host cluster or a cluster itself is irrelevant to them. For them it's complete transparent. >>So transparency, enabling developer velocity. What's been some of the feedback so far? >>Oh, all developer love that. And also same for all >>The ops team. If it's easy and goods faster and the steps >>Win-win team. Yeah, Ops team, they need a consistency. They need a governance, they need visibility, but in the meantime, developers, they need the flexibility then theys or without a steep learning curve. So this really, >>So So I hear a lot of people say, I got a lot of sprawl, cluster sprawl. Yeah, let's get outta hand does, let's solve that. How do you guys solve that problem? Yeah, >>So the Neste cluster is a profit answer for that. So before you nest cluster, for a lot of enterprise to serving developers, they have to either create a very large TED cluster and then isolated by namespace, which not ideal for a lot of situation because name stay namespace is not a hard isolation and also a lot of global resource like CID and operator does not work in space. But the other way is you give each developer a separate, a separate ADE cluster, but that very quickly become too costly. Cause not every developer is working for four, seven, and half of the time your, your cluster is is a sit there idol and that costs a lot of money. So you cluster, you'll be able to basically do all these inside the your wholesale cluster, bring the >>Efficiency there. That is huge. Yeah. Saves a lot of time. Reduces the steps it takes. So I take, take a minute, my last question to you to explain what's in it for the developer, if they work with Spec Cloud, what is your value? What's the pitch? Not the sales pitch, but like what's the value pitch that >>You give them? Yeah, yeah. And the value for us is again, develop their number of different services and teams people are using today are so many, there are so many different languages or so many different libraries there so many different capabilities. It's too hard for developers to have to understand not only the internal development tools, but also the Kubernetes, the containers of technologies. There's too much for it. Our value prop is making it really easy for them to get access to all these different integrations and tooling without having to learn it. Right? And then being able to very easily say, I wanna deploy this into a cluster. Again, whether it's a Nest cluster or a host cluster. But the next layer on top of that is how do we also share those abilities with other teams. If I build my application profile, I'm developing an application, I should be able to share it with my team members. But Henry saying, Hey Tanner, why don't you also take a look at my app profile and let's build and collaborate together on that. So it's about collaboration and be able to move >>Really fast. I mean, more develops gotta be more productive. That's number one. Number one hit here. Great job. >>Exactly. Last question before we run out Time. Is this ga now? Can folks get their hands on it where >>Yes. Yeah. It is GA and available both as a, as a SaaS and also the store. >>Awesome guys, thank you so much for joining us. Congratulations on the announcement and the momentum that Specter Cloud is empowering itself with. We appreciate your insights on your time. >>Thank you. Thank you so much. Right, pleasure. >>Thanks for having us. For our guest and John Furrier, Lisa Martin here live in Michigan at Co con Cloud native PON 22. Our next guests join us in just a minute. So stick around.

>>Hello and welcome back to the live coverage of the Cube here. Live in Detroit, Michigan for Cub Con, our seventh year covering all seven years. The cube has been here. M John Fur, host of the Cube, co-founder of the Cube. I'm here with Lisa Mart, my co-host, and our new host, Savannah Peterson. Great to see you guys. We're wrapping up day one of three days of coverage, and our guest analyst is Sario Wall, who's the cube analyst who's gonna give us his report. He's been out all day, ear to the ground in the sessions, peeking in, sneaking in, crashing him, getting all the data. Great to see you, Sarvi. Lisa Savannah, let's wrap this puppy up. >>I am so excited to be here. My first coupon with the cube and being here with you and Lisa has just been a treat. I can't wait to hear what you have to say in on the report side. And I mean, I have just been reflecting, it was last year's coupon that brought me to you, so I feel so lucky. So much can change in a year, folks. You never know where you're be. Wherever you're sitting today, you could be living your dreams in just a few >>Months. Lisa, so much has changed. I mean, just look at the past this year. Events we're back in person. Yeah. Yep. This is a big team here. They're still wearing masks, although we can take 'em off with a cube. But mask requirement. Tech has changed. Conversations are upleveling, skill gaps still there. So much has changed. >>So much has changed. There's so much evolution and so much innovation that we've also seen. You know, we started out the keynote this morning, standing room. Only thousands of people are here. Even though there's a mass requirement, the community that is CNCF Co Con is stronger than I, stronger than I saw it last year. This is only my second co con. But the collaboration, what they've done, their devotion to the maintainers, their devotion to really finding mentors for mentees was really a strong message this morning. And we heard a >>Lot of that today. And it's going beyond Kubernetes, even though it's called co con. I also call it cloud native con, which I think we'll probably end up being the name because at the end of day, the cloud native scaling, you're starting to see the pressure points. You're start to see where things are breaking, where automation's coming in, breaking in a good way. And we're gonna break it all down Again. So much going on again, I've overs gonna be in charge. Digital is transformation. If you take it to its conclusion, then you will see that the developers are running the business. It isn't a department, it's not serving the business, it is the business. If that's the case, everything has to change. And we're, we're happy to have Sarib here with us Cube analysts on the badge. I saw that with the press pass. Well, >>Thank you. Thanks for getting me that badge. So I'm here with you guys and >>Well, you got a rapport. Let's get into it. You, I >>Know. Let's hear what you gotta say. I'm excited. >>Yeah. Went around, actually attend some sessions and, and with the analysts were sitting in, in the media slash press, and I spoke to some people at their booth and the, there are a few, few patterns, you know, which are, some are the exaggeration of existing patterns or some are kind of new patterns emerging. So things are getting complex in open source. The lawn more projects, right. They have, the CNCF has graduated some projects even after graduation, they're, they're exploring, right? Kubernetes is one of those projects which has graduated. And on that front, just a side note, the new projects where, which are entering the cncf, they're the, we, we gotta see that process and the three stages and all that stuff. I tweeted all day long, if you wanna know what it is, you can look at my tweets. But when I will look, actually write right on that actually after, after the show ends, what, what I saw there, these new projects need to be curated properly. >>I think they need to be weed. There's a lot of noise in these projects. There's a lot of overlap. So the, the work is cut out for CNCF folks, by the way. They're sort of managerial committee or whatever you call that. The, the people who are leading it, they're try, I think they're doing their best and they're doing a good job of that. And another thing actually, I really liked in the morning's keynote was that lot of women on the stage and minorities represented. I loved it, to be honest with you. So believe me, I'm a minority even though I'm Indian, but from India, I'm a minority. So people who have Punjab either know that I'm a minority, so I, I understand their pain and how hard it is to, to break through the ceiling and all that. So I love that part as well. Yeah, the >>Activity is clear. Yeah. From day one. It's in the, it's in the dna. I mean, they'll reject anything that the opposite >>Representation too. I mean, it's not just that everyone's invited, it's they're celebrated and that's a very big difference. Yeah. It's, you see conferences offer discounts for women for tickets or minorities, but you don't necessarily see them put them running where their mouth is actually recruit the right women to be on stage. Right. Something you know a little bit about John >>Diversity brings better outcomes, better product perspectives. The product is better with all the perspectives involved. Percent, it might go a little slower, maybe a little debates, but it's all good. I mean, it's, to me, the better product comes when everyone's in. >>I hope you didn't just imply that women would make society. So >>I think John men, like slower means a slower, >>More diversity, more debate, >>The worst. Bringing the diversity into picture >>Wine. That's, that's how good groups, which is, which is >>Great. I mean, yeah, yeah, >>Yeah, yeah. I, I take that mulligan back and say, hey, you knows >>That's >>Just, it's gonna go so much faster and better and cheaper, but that not diversity. Absolutely. >>Yes. Well, you make better products faster because you have a variety >>Of perspectives. The bigger the group, there's more debate. More debate is key. But the key to success is aligning and committing. Absolutely. Once you have that, and that's what open sources has been about for. Oh God, yeah. Generations >>Has been a huge theme in the >>Show generations. All right, so, so, >>So you have to add another, like another important, so observation if you will, is that the security is, is paramount right. Requirement, especially for open source. There was a stat which was presented in the morning that 60% of the projects in under CNCF have more vulnerabilities today than they had last year. So that was, That's shocking actually. It's a big jump. It's a big jump. Like big jump means jump, jump means like it can be from from 40 to 60 or or 50 or 60. But still that percentage is high. What, what that means is that lot more people are contributing. It's very sort of di carmic or ironic that we say like, Oh this project has 10,000 contributors. Is that a good thing? Right. We do. Do we know the quality of that, where they're coming from? Are there any back doors being, you know, open there? How stringent is the process of rolling those things, which are being checked in, into production? You know, who is doing that? I've >>Wondered about that. Yeah. The quantity, quality, efficacy game. Yes. And what a balance that must be for someone like CNCF putting in the structure to try and >>That's >>Hard. Curate and regulate and, and you know, provide some bumpers on the bowling lane, so to speak, of, of all of these projects. Yeah. >>Yeah. We thought if anybody thought that the innovation coming from, or the number of services coming from AWS or Google Cloud or likes of them is overwhelming, look at open source, it's even more >>Overwhelming. What's your take on the supply chain discussion? More code more happening. What are you hearing there? >>The supply chain from the software? Yeah. >>Supply chain software, supply chain security pays. Are people talking about that? What are you >>Seeing? Yeah, actually people are talking about that. The creation, the curation, not creation. Curation of suppliers of software I think is best done in the cloud. Marketplaces Ive call biased or what, you know, but curation of open source is hard. It's hard to know which project to pick. It's hard to know which project will pan out. Many of the good projects don't see the day light of the day, but some decent ones like it becomes >>A marketing problem. Exactly. The more you have out there. Exactly. The more you gotta get above the noise. Exactly. And the noise echo that. And you got, you got GitHub stars, you got contributors, you have vanity metrics now coming in to this that are influencing what's real. But sometimes the best project could have smaller groups. >>Yeah, exactly. And another controversial thing a little bit I will say that is that there's a economics of the practitioner, right? I usually talk about that and economics of the, the enterprise, right? So practitioners in our world, in software world especially right in systems world, practitioners are changing jobs every two to three years. And number of developers doubles every three years. That's the stat I've seen from Uncle Bob. He's authority on that software side of things. Wow. So that means there's a lot more new entrance that means a lot of churn. So who is watching out for the enterprise enterprises economics, You know, like are we creating stable enterprises? How stable are our operations? On a side note to that, most of us see the software as like one band, which is not true. When we talk about all these roles and personas, somebody's writing software for, for core layer, which is the infrastructure part. Somebody's writing business applications, somebody's writing, you know, systems of bracket, some somebody's writing systems of differentiation. We talk about those things. We need to distinguish between those and have principle based technology consumption, which I usually write about in our Oh, >>So bottom line in Europe about it, in your opinion. Yeah. What's the top story here at coupon? >>Top story is >>Headline. Yeah, >>The, the headline. Okay. The open source cannot be ignored. That's a headline. >>And what should people be paying attention to if there's a trend coming out? See any kind of trends coming out or any kind of signal, What, what do you see that people should pay attention to here? The put top >>Two, three things. The signal is that, that if you are a big shop, like you'd need to assess your like capacity to absorb open source. You need to be certain size to absorb the open source. If you are below that threshold, I mean we can talk about that at some other time. Like what is that threshold? I will suggest you to go with the managed services from somebody, whoever is providing those managed services around open source. So manage es, right? So from, take it from aws, Google Cloud or Azure or IBM or anybody, right? So use open source as managed offering rather than doing it yourself. Because doing it yourself is a lot more heavy lifting. >>I I, >>There's so many thoughts coming, right? >>Mind it's, >>So I gotta ask you, what's your rapport? You have some swag, What's the swag look >>Like to you? I do. Just as serious of a report as you do on the to floor, but I do, so you know, I come from a marketing background and as I, I know that Lisa does as well. And one of the things that I think about that we touched on in this is, is you know, canceling the noise or standing out from the noise and, and on a show floor, that's actually a huge challenge for these startups, especially when you're up against a rancher or companies or a Cisco with a very large budget. And let's say you've only got a couple grand for an activation here. Like most of my clients, that's how I ended up in the CU County ecosystem, was here with the A client before. So there actually was a booth over there and I, they didn't quite catch me enough, but they had noise canceling headphones. >>So if you just wanted to take a minute on the show floor and just not hear anything, which I thought was a little bit clever, but gonna take you through some of my favorite swag from today and to all the vendors, you know, this is why you should really put some thought into your swag. You never know when you're gonna end up on the cube. So since most swag is injection molded plastic that's gonna end up in the landfill, I really appreciate that garden has given all of us a potable plant. And even the packaging is plantable, which is very exciting. So most sustainable swag goes to garden. Well done >>Rep replicated, I believe is their name. They do a really good job every year. They had some very funny pins that say a word that, I'm not gonna say live on television, but they have created, they brought two things for us, yet it's replicated little etch sketch for your inner child, which is very nice. And given that we are in Detroit, we are in Motor City, we are in the home of Ford. We had Ford on the show. I love that they have done the custom K eight s key chains in the blue oval logo. Like >>Fords right behind us by the way, and are on you >>Interviewed, we had 'em on earlier GitLab taking it one level more personal and actually giving out digital portraits today. Nice. Cool. Which is quite fun. Get lap house multiple booths here. They actually IPOed while they were on the show floor at CubeCon 2021, which is fun to see that whole gang again. And then last but not least, really embracing the ship wheel logo of a Kubernetes is the robusta accrue that is giving out bucket hats. And if you check out my Twitter at sabba Savvy, you can see me holding the ship wheel that they're letting everyone pose with. So we are all in on Kubernetes. That cove gone 2022, that's for sure. Yeah. >>And this is something, day one guys, we've got three. >>I wanna get one of those >>Hats. We we need to, we need a group photo >>By the end of Friday we will have a beverage and hats on to sign off. That's, that's my word. If I can convince John, >>Don, what's your takeaway? You guys did a great kind of kickoff about last week or so about what you were excited about, what your thoughts were going to be. We're only on day one, There's been thousands of people here, we've had great conversations with contributors, the community. What's your take on day one? What's your, what's your tagline? >>Well, Savannah and I had at we up, we, we were talking about what we might see and I think we, we were right. I think we had it right. There's gonna be a lot more people than there were last year. Okay, check. That's definitely true. We're in >>Person, which >>Is refreshing. I was very surprised about the mask mandate that kind of caught me up guard. I was major. Yeah. Cause I've been comfortable without the mask. I'm not a mask person, but I had to wear it and I was like, ah, mask. But I understand I support that. But whatever. It's >>Corporate travel policy. So you know, that's what it is. >>And then, you know, they, I thought that they did an okay job with the gates, but they wasn't slow like last time. But on the content side, definitely Kubernetes security, top line headline, Kubernetes at scale security, that's, that's to me the bumper sticker top things to pay attention to the supply chain and the role of docker and the web assembly was a surprise. You're starting to see containers ecosystem coming back to, I won't say tension growth in the functionality of containers cuz they have to solve the security problem in the container images. Okay, you got scanning technology so it's a little bit in the weeds, but there's a huge movement going on to fix that problem to scale it so it's not a problem area contain. And then Dr sent a great job with productivity interviews. Scott Johnston over a hundred million in revenue so far. That's my number. They have not publicly said that. That's what I'm reporting from sources extremely well financially. And they, and they love their business model. They make productivity for developers. That's a scoop. That's new >>Information. That's a nice scoop we just dropped there on the co casually. >>You're watching that. Pay attention to that. But that, that's proof. But guess what, Red Hat's got developers too. Yes. Other people have to, So developers gonna go where it's the best. Yeah. Developers are voting with their code, they're voting with their feet. You will see the winners with the developers and that's what we've talked about. >>Well and the companies are catering to the developers. Savannah and I had a great conversation with Ford. Yeah. You saw, you showed their fantastic swag was an E for Ev right behind us. They were talking about the, all the cultural changes that they've really focused on to cater towards the developers. The developers becoming the influencers as you say. But to see a company that is as, as historied as Ford Motor Company and what they're doing to attract and retain developer talent was impressive. And honestly that surprised me. Yeah. >>And their head of deb relations has been working for, for, for 29 years. Which I mean first of all, most companies on the show floor haven't been around for 29 years. Right. But what I love is when you put community first, you get employees to stick around. And I think community is one of the biggest themes here at Cuco. >>Great. My, my favorite story that surprised me and was cool was the Red Hat Lockheed Martin interview where they had edge deployments with micro edge, >>Micro shift, >>Micro >>Shift, new projects under, there's, there are three new projects under, >>Under that was so, so cool because it was an edge story in deployment for the military where lives are on the line, they actually had it working. That is a real world example of Kubernetes and tech orchestrating to deploy the industrial edge. And I think that's proof in my mind that Kubernetes and this ecosystem is gonna move faster through this next wave of growth. Because once things start clicking, you get hybrid on premise to super cloud and edge. That was, that was my favorite cause it was real. That was real >>Story that it can make is literally life and death on the battlefield. Yeah, that was amazing. With what they're doing and what >>They're talking check out the Lockheed Martin Red Hat edge story on Silicon Angle and then a press release all pillar. >>Yeah. Another actually it's impressive, which we knew this which is happening, but I didn't know that it was happening at this scale is the finops. The finops is, I saw your is a discipline which most companies are adopting bigger companies, which are spending like hundreds of millions dollars in cloud average. Si a team size of finops for finops is seven people. And average number of tools is I think 3.5 or around 3.7 or something like that. Average number of tools they use to control the cost. So finops is a very generic term for years. It's not financial operations, it's the financial operations for the cloud cost, you know, containing the cloud costs. So that's a finops that is a very emerging sort of discipline >>To keep an eye on. And well, not only is that important, I talked to, well one of the principles over there, it's growing and they have real big players in that foundation. Their, their events are highly attended. It's super important. It's just, it's the cost side of cloud. And, and of course, you know, everyone wants to know what's going on. No one wants to leave there. Their Amazon on Yeah, you wanna leave the lights on the cloud, as we always say, you never know what the bill's gonna look like. >>The cloud is gonna reach $3 billion in next few years. So we might as well control the cost there. Yeah, >>It was, it was funny to get the reaction I found, I don't know if I was, how I react, I dunno how I felt. But we, we did introduce Super Cloud to a couple of guests and a, there were a couple reactions, a couple drawn. There was a couple, right. There was a couple, couple reactions. And what I love about the super cloud is that some people are like, oh, cringing. And some people are like, yeah, go. So it's a, it's a solid debate. It is solid. I saw more in the segments that I did with you together. People leaning in. Yeah. Super fun. We had a couple sum up, we had a couple, we had a couple cringes, I'll say their names, but I'll go back and make sure I, >>I think people >>Get 'em later. I think people, >>I think people cringe on the, on the term not on the idea. Yeah. You know, so the whole idea is that we are building top of the cloud >>And then so I mean you're gonna like this, I did successfully introduce here on the cube, a new term called architectural list. He did? That's right. Okay. And I wanna thank Charles Fitzgerald for that cuz he called super cloud architectural list. And that's exactly the point of super cloud. If you have a great coding environment, you shouldn't have to do an architecture to do. You should code and let the architecture of the Super cloud make it happen. And of course Brian Gracely, who will be on tomorrow at his cloud cast said Super Cloud enables super services. Super Cloud enables what Super services, super service. The microservices underneath the covers have to be different. High performing, automated. So again, the debate and Susan, the goal is to keep it open. And that's our, that's our goal. But we had a lot of fun with that. It was fun to poke the bear a little bit. So >>What is interesting to see just how people respond to it too, with you throwing it out there so consistently, >>You wanna poke the bear, get a conversation going, you know, let let it go. We'll see, it's been positive so far. >>There, there I had a discussion outside somebody who is from Ford but not attending this conference and they have been there for a while. I, I just some moment hit like me, like I said, people, okay, technologists are horizontal, the codes are horizontal. They will go from four to GM to Chrysler to Bank of America to, you know, GE whatever, you know, like cross vertical within vertical different vendors. So, but the culture of a company is local, right? Right. Ford has been building cars for forever. They sort of democratize it. They commercialize it, right? But they have some intense culture. It's hard to change those cultures. And how do we bring in the new thinking? What is, what approach that should be? Is it a sandbox approach for like putting new sensors on the car? They have to compete with te likes our Tesla, right? Yeah. But they cannot, if they are afraid of deluding their existing market or they're afraid of failure there, right? So it's very >>Tricky. Great stuff. Sorry. Great to have you on as our cube analyst breaking down the stories. We'll document that, that we'll roll out a post on it. Lisa Savannah, let's wrap up the show for day one. We got day two and three. We'll start with you. What's your summary? Quick bumper sticker. What's today's show all about? >>I'm a community first gal and this entire experience is about community and it's really nice to see the community come together, celebrate that, share ideas, and to have our community together on stage. >>Yeah. To me, to me it was all real. It's happening. Kubernetes cloud native at scale, it's happening, it's real. And we see proof points and we're gonna have faster time to value. It's gonna accelerate faster from here. >>The proof points, the impact is real. And we saw that in some amazing stories. And this is just a one of the cubes >>Coverage. Ib final word on this segment was well >>Said Lisa. Yeah, I, I think I, I would repeat what I said. I got eight, nine years back at a rack space conference. Open source is amazing for one biggest reason. It gives the ability to the developing nations to be at somewhat at par where the dev develop nations and, and those people to lift up their masses through the automation. Cuz when automation happens, the corruption goes down and the economy blossoms. And I think it's great and, and we need to do more in it, but we have to be careful about the supply chains around the software so that, so our systems are secure and they are robust. Yeah, >>That's it. Okay. To me for SAR B and my two great co-host, Lisa Martin, Savannah Peterson. I'm John Furry. You're watching the Cube Day one in, in the Books. We'll see you tomorrow, day two Cuban Cloud Native live in Detroit. Thanks for watching.

>>And welcome to this cube conversation here in Palo Alto, California. I'm John furrier, host of the cube. We have a great guest coming in remotely from LA Christian Hernandez developer experienced lead at code fresh code fresh IO. Recently they were on our feature at a startup showcase series, season two episode one cloud data innovations, open source innovations, all good stuff, Christian. Thanks for coming on this cube conversation. >>Thank you. Thank you, John. Thank you for having me on, >>You know, I'm I was really impressed with code fresh. My met with the founders on here on the cube because GI ops AI, everything's something ops devs dev sec ops. You've got AI ops. You've got now GI ops, essentially operationalizing the software future is here and software's eating the world is, was written many years ago, but it's open source is now all. So all things software's open source and that's kind of a done deal. It's only getting better and better. Mainstream companies are contributing. You guys are on this wave of, of this open source tsunami and you got cloud scale. Automation's right there, machine learning, all this stuff is now the next gen of, of, of code, right? So you, your code fresh and your title is developer experience lead. What does that mean right now? What does it mean to be a developer experience lead? Like you make sure people having a good experience. Are you developing you figuring out the product? What does that mean? >>Yeah. That's and it's also part of the, the whole Debre explosion that's happening right now. I believe it's, you know, everyone's always asking, well, what, you know, what is developer advocate? What does that mean developer experience? What does that mean? So, so you, you kind of hit the nail on the head a little bit up there in, in the beginning, is that the, the experience of the developer when using a particular platform, right? Especially the code flash platform. That is my responsibility there at code fresh to enable, to enable end users, to enable partners, to enable, you know, anyone that wants to use the code fresh platform for their C I C D and get ops square flows. So that's, that's really my, my corner of the world is to make sure their experience is great. So that's, it's really what, what I'm here to do >>At food fresh. You know, one of the things I can say of my career, you've been kind of become a historian over time. When I was a developer back in the old days, it was simply you compiled stuff, you did QA on it. You packaged it out. You wanted out the door and you know, that was a workflow right now with the cloud. I was talking with your founders, you got new abstraction layers. Cloud has changed again again, open source. So newer things are coming, right? Like, like, like Kubernetes for instance is a great example that came out of the open source kind of the innovations. But that, and Hadoop, we were mentioning before he came on camera from a storage standpoint, kind of didn't make it because it was just too hard. Right. And it made the developer's job harder. And then it made the developer's requirements to be specialized. >>So you had kind of two problems. You had hard to use a lot of friction and then it required certain expertise when the developers just want to code. Right. So, so you have now the motion of, with GI ops, you guys are in the middle of kinda this idea of frictionless based software delivery with the cloud. So what's different now, can you talk about that specific point because no one wants to be, do hard work and have to redo things. Yeah. Shift left and all that good stuff. What's hard now, what do you guys solve? What's the, what's the friction that you're taking out what's to become frictionless. >>Yeah. Yeah. And you, you, you mentioned a very interesting point about how, you know, things that are coming out almost makes it seem harder nowadays to develop an application. You used to have it to where, you know, kind of a, sort of a waterfall sort of workflow where, you know, you develop your code, you know, you compile it. Right. You know, I guess back in the day, Java was king. I think Java still is, has a, is a large footprint out there where you would just compile it, deploy it. If it works, it works. Alright cool. And you have it and you kind of just move it along in its process. Whereas I think the, the whole idea of, I think Netflix came out with like the, the fail often fail fast release often, you know, the whole Atlassian C I C D thing, agile thing came into play. >>Where now it's, it's a little bit more complex to get your code out there delivered to get your code from one environment to the other environment, especially with the, the Avan of Kubernetes and cloud native architecture, where you can deploy and have this imutable infrastructure where you can just deploy and automate so quickly. So often that there needs to be some sort of new process now into place where to have a new process, like GI ops to where it'll, it it's frictionless, meaning that it's, it, it makes it that process a little easier makes that little, that comp that complex process of deploying onto like a cloud native architecture easier. So that way, as you said before, returning the developers to back to what they care about, mot, the most is just code. I just want to code. >>Yeah. You know, the other thing, cool thing, Christian, I wanna bring up and we'll get into some of the specifics around Argo specifically CD is that the community is responding as a kind of, it takes a village kind of mindset. People are getting into this just saying, Hey, if we can get our act together around some de facto workflows and de facto capabilities, everyone wins. It's a rising tide, floats all boats, kind of concept. CNCF certainly has been a big part of that. Even seen some of the big hyper scales getting behind it. But you guys are part of the founding members of the open get ups working group, Amazon Azure, GitHub, red hat Weaveworks and then a ton of contributors. Okay. So this is kind of cool. This means that there's like people behind this thing. Look, we gotta get here faster. What happened at co con this year? You guys had some news around Argo and you had some news around the hosted solution. Can you take a minute to explain two things, one the open community vibe, and then two, what you guys announced at Coon in Spain. >>Yeah. Yeah. So as far as open get ups, that was, you know, as you said before, code fresh was part of that, that founding committee. Right. Of, of group of people trying to figure out, define what get ups is. Right. We're trying to bring it beyond the, you know, the, the hype word, right beyond just like a marketing term to where we actually define what it actually is, because it is actually something that's out there that people are doing. Right. A lot of people, you know, remember that the, the Chick-fil-A story where it's like, they, they are completely doing, you know, this get ops thing, we're just now wanting, putting definition around it. So that was just amazing to see out at there in, in Cuban. And, but like you said, in QAN, we, you know, we're, we're, we're taking some of that, that acceleration that we see in the community to, and we, we announce our, our hosted get ops offering. >>Right. So hosted get ops is something that our customers have been asking for for a while. Many times when, you know, someone wants to use something like Argo CD, the, in, they install it on their cluster, they get up and running. And, but with, with all that comes like the feed and care of that platform, and, you know, not only just keeping the lights on, but also management security, you know, general maintenance, you know, all the things that, that come along with managing a system. And on top of that comes like the scale aspect of it. Right. And so with scale, so a lot of people go with like a hub and spoke others, go with like a fleet design in, in either case, right. There's, there's a challenge for the feet and care of it. Right. And so with code fresh coast of get ups, we take that management headache away. >>Right? So we, we take the, the, the management of, of Argo CD, the management of, of all of that, and kind of just offer Argo CD as a surface, right. Which offers, you know, allows users to, you know, let us take care of all the, of the get offs, runtime. And so they can concentrate on, you know, their application deployments. Right. And you also get things like Dora metrics, right. Integrated with the platform, you have the ability to integrate multiple CI providers, you know, like get hub actions or whatever, existing Jenkins pipelines. And really that, that code fresh platform becomes like your get ops platform becomes like, you know, your, your central view of the world of, of your, you know, get ups processes. >>Yeah. I mean, that whole single source of truth concept is really kind of needed. I gotta ask you though, with the popularity of the Argo CD on get ups internally, right. That's been clear, right. Kubernetes, the way that's going, it's accelerating fast. People want simple it's scaling, you got automation built in all that good stuff. What was the driver behind the hosted get up solution? Was it customer needs? Was it efficiency all the above? What was specifically and, and why would someone want to have the hosted versus say internal? >>Yeah. So it's, it was really driven by, you know, customer need been something that the customers have been asking for. And it's also been something that, you know, you, you, you have a process of developing an application to, you know, you know, a fleet of clusters in a traditional, you know, I keep saying traditional, get outs practice as if get outs are so old. And, you know, in, you know, when, when, when people first start out, they'll start, you know, installing Argo city on all these clusters and trying to manage that at scale it's, it's, it, it seemed like there was, you know, it it'd be nice if we can just like, be able to consume this as a service. So we don't have to like, worry about, you know, you know, best practices. We don't have to worry about security. We don't just, all of that is taken care of and managed by us at code fresh. So this is like something that, you know, has been asked for and, and something that, you know, we believe will accelerate, you know, developers into actually developing their, their applications. They don't have to worry about managing >>The platform. So just getting this right. Hosted, managed service by you guys on this one, >>Correct? Yes. >>Okay. Got it. All right. So let me, let me get in the Argo real quick, just to kind of just level set for the folks that are, are leaning into this and then kicking the tires. Where are we with Argo? What, why was it so popular? What did it do specifically? Did it just make it easier for developers to manage and monitor Kubernetes, keep 'em updated? What was the specific value behind Argo? Where, where, where did it come from and why is it so popular? >>Yeah, so Argo the Argo project, which is made up of, of a few tools, usually when people say Argo, they meet, they they're talking about Argo CD, but there's also Argo workflows, Argo events, Argo notifications. And, and like I said before, CD with that, and that is something that was developed internally at Intuit. Right? So for those of who don't know, Intuit is the company behind turbo tax. So for those, those of us in the us, we, we know, you know, we know that season all too well, the tax season. And so that was a tool that was developed internally. >>And by the way, Intuit we've done many years. They're very huge cloud adopters. They've been on that train from the day one. They've been, they've been driving a lot of cloud scale too. Sorry >>To interrupt. Yeah. And, and, and yeah, no, and, and, and also, you know, they, they were always open source first, right. So they've always had, you know, they developed something internally. They always had the, the intention of opensourcing it. And so it was really a tool that was born internally, and it was a tool that helped them, you know, get stuff done with Kubernetes. And that's kind of like the tagline they use for, for the Argo project is you need to get stuff done. They wanted their developers to focus less on deploying the application and more right. More than on writing the application itself. And so the, and so the Argo project is a suite of tools essentially that helps deploy onto Kubernetes, you know, using get ups as that, you know, that cornerstone in design, right in the design philosophy, it's so popular because of the ease of use and developer friendliness aspect of it. It's, it's, it's, it's meant to be simple right. In and simple in a, in a good sense of getting up and running, which attracted, you know, developers from, you know, all around the world. You know, other companies like red hat got into it as well. BlackRock also is, is a, is a big contributor, thousands of other independent contributors as well to the Argo project. >>Yeah. Christian, if you bring up a good point and I'm gonna go on a little tangent here, but I wanna get your reaction to something that Dave ante and I, and our cube team has been kind of riffing on lately. You mentioned, you know, Netflix earlier, you mentioned Intuit. There's a kind of a story that's been developing and, and with traction and momentum and trajectory over the past, say 10 years, the companies that went on the cloud, like Netflix into it, snowflake, snowflake, not so much now, but in terms of open source, they're all contributing lift. They're all contributing back to open source, but they're not cloud providers. Right. So you're seeing that kind of first generation, I's a massive contribution to open source. So open source been around for a while, remember the early days, and we'd all participate on projects, but now you have real companies building IP going open source first because they're on a hyperscale cloud, but they're not the cloud themselves. They took advantage of that. So there's kind of this cycle of flywheel of cloud to open source, not from the vendors themselves like Amazon, which services or Azure, but the people who rode their CapEx and built on that scale, feeding into the open source. And then coming back, this is kind of an interesting dynamic. What's your reaction to that? Do you see that? Yeah. Super cloud kind of vibe there. >>Yeah. Yeah. Well, and, and also it, it, I think it's, it's a, it's indicative that, you know, open source is not only, you know, a way to develop, you know, applications, a way to engineer, you know, your project, but also kind of like a strategic advantage in, in, in such a way. Right. You know, you, you see, you see companies like, like, like even like Microsoft has been going into, you know, open source, right. They they've been going to open source first. They made a, a huge pivot to, you know, using open source as, you know, like, like a, like a strategic direction for, for the company. And I think that goes back to, you know, a little bit for my roots, you know, I, I, I always, I always talk about, you know, I always talk about red hat, right. I always talk about, you know, I was, I was, I was in red hat previously and, you know, you know, red hat being, you know, the first billion dollar open source company. >>Right. I, we always joke is like, well, you know, internally, like we know you were a billion dollar company that sold free software. How, you know, how, how does that happen? But it's, it's, it's really, you know, built into the, built into being able to tap into those expert resources. Yeah. You know, people love using software. People love the software they love using, and they wanna improve it. Companies are now just getting out of their way. Yeah. You know, companies now, essentially, it's just like, let's just get out of the way. Let's let people work on, you know, what they wanna work on. They love the software. They wanna improve it. Let's let them, >>It's interesting. A lot of people love the clouds have all this power. If you think about what we are just riffing on and what you just said, the economics and the organic self-governing has always been the open source way where commercial value is enabled. If you play ball, right. Like, oh, red hat, for instance. And now you're seeing the community kind of be that arbiter of the cloud. So, Hey, if everyone can create value on say AWS or Azure, bring it to open source, everyone benefits across all clouds hope eventually. So the choice aspect comes in. So this community angle is huge. And I think it's changing a lot for the better. And I think this is where we're seeing a lot of that growth. And you guys have been the middle level with the Argo project and get ups specifically in that, in that sector. How have you seen that growth? What some dynamics have you seen power dynamics, organic? Is it governed well, whats some of the, the successes, what are some of the challenges? Can you share your thoughts on the community's growth around get ops and Argo project? >>Yeah, yeah. Yeah. So I've been, you know, part of some of these communities, right? Like the, the open, get, get ops community, the Argos community pretty much from the beginning and, and seeing it developed from an idea to, you know, having all these contributors, having, you know, the, the, the buzzword come out of it, you know, the get ups and it be that being the, you know, having it, you know, all over the, you know, social media, all over LinkedIn, all over all, all these, all these different channels, you know, I I've seen things like get ops con, right. So, you know, being part of the, get ops open, get ops community, you know, one of the things we did was we did get ops con it started as a meetup, you know, couple years ago. And now, you know, it was a, you know, we had an actual event at Cuan in Los Angeles. >>You know, we had like, you know, about 50 people there, but then, you know, Cuan in Valencia this past Cuan we had over 200 people, it was a second largest co-located events in, at Cuan. So that just, just seeing that community and, you know, from a personal standpoint, you know, be being part of that, that the, the community being the, the event chair, right. Yeah. Being, being one of the co-chairs was a, was a moment of pride for me being able to stand up there and just seeing a sea of people was like, wow, we just started with a handful of people at a meetup. And now, you know, we're actually having conferences and, and, and speaking of conference, like the Argo community as well, we put in, you know, we put on a virtual only event on Argo con last year. We're gonna do it in person today. You know, this year. >>Do you have a date on that? Do you have a date on that Argo con 22? >>Two? Yeah, yeah, yeah. Argo con September 19th, 2022. So, you know, mark your calendars, it it's, you know, it's a multi-day event, you know, it's, it's part of something else that I've seen in the community where, you know, first we're talk talking about these meetups. Now we're doing multi-day events. We're, you know, in talks of the open, get ups, you know, get ups can also make that a multi-day event. There's just so many talks in so many people that want to be involved in network that, you know, we're saying, well, we're gonna need more days because there's just so many people coming to these events, you know, in, in, you know, seeing these communities grow, not just from like the engineering standpoint, but also from the end user standpoint, but also from the people that are actually doing these things. And, you know, seeing some of these use cases, seeing some of the success, seeing some of the failures, right? Like people love listening to those talks about postmortems, I think are part of my favorite talks as well. So seeing that community grow is, is, you know, on a personal level, it's, it's a point >>It's like CSI for software developers. You want to curious about >>Exactly >>What happened. You know, you know, it's interesting, you mentioned about the, the multiple events at Coon. You know, the vibe that's going on is a very festival vibe, right? You have organic groups coming together. I remember when they had just started doing the day zero programs. Now you have like, almost like multiple stages of content at these events. It feels like, like a Coachella vibe or some sort of like festival vibe, like a lot of things going on and you, and if you pick your kind of area, but you can move around, I find that the kind of the format de Azure I think is going well these days. What do you think about that? >>Yeah, yeah. No, for sure. It's and, and, and I love that that analogy of Coachella, it does feel like, you know, it's, there's something for everyone and you can find what you like, and you'll find a little, you know, a little group, right. A little click of, of, of people that's probably the wrong term to use, but you know, you, you find, you know, you, you know, like-minded people and, you know, passionate about the same thing, right? Like the security guys, they, you know, you see them all clump together, right? Like you see like the, the developer C I CD get ops guys, we all kind of clump together and start talking, you know, about everything that we're doing. And it's, that's, that's, I think that's really something special that coupon, you know, some, you know, it's gotten so big that it's almost impossible to fit everything in a, in a week, because unless there's just so much to do. And there's so much that that interests, you know, someone, but it's >>A code, a code party is what we call it. It's a code party. Yeah. >>It's, it's a code party for sure. For >>Sure. Nerd nerd Fest on, on steroids. Hey, I gotta get, I wanna wrap this up and give you the final word, Christian. Thanks for coming on. Great insight, great conversation. There's a huge, you guys are in the middle of a hot area, obviously large scale data growth. Kubernetes is scaling beautifully and making it easier at managed services. What people want machine learning's kicking in and, and you get automation building in all favoring, the developer and C I CD pipeline and all that good stuff. People want to learn more. Can you take a minute to put the plug in for code fresh on the certification? How do I get involved? Where are you? Is there levels if I want to jump in and get trained and get fluent on code fresh, can you share commentary and, and, and what the status is? >>Yeah, yeah, for sure. So code fresh is offering a free certification, right? For get ups or Argo CD and get ops. The first of it's kind for Argo CD, first of it's kind for get ops is you can actually go get certified with Argo CD and get ops. You know, we there level one is out right now. You can go take that code, fresh.io/certification. It's out there, sign up, you know, you, you don't, you don't need to pay anything, right. It's, it's something it's a, of a free course. You could take level two is coming soon. Right? So level two is coming soon in the next few months, I believe I don't wanna quote a specific day, but soon because I, but soon I, it it's soon, soon as in, as in months. Right? So, you know, we're, we're counting that down where you can not only level one cert level certification, but a level, two more advanced certification for those who have been using Argo for a while, they can still, you know, take that and be, you know, be able to get, you know, another level of certification for that. So also, you know, Argo con will be there. We're, we're part of the programming committee for Argo con, right? This is a community driven event, but, you know, code fresh is a proud diamond sponsor. So we'll be there. >>Where's it located up to us except for eptember 19th multiday or one day >>It's a, it's a multi-day event. So Argo con from 19, 19 20 and 21 in a mountain view. So it'll be in mountain view in the bay area. So for those of you who are local, you can just drive in. Great. >>I'm write that down. I'll plug it. I'll put in the show notes. >>Awesome. Awesome. Yeah. And you will be there so you can talk to me, you can talk to anyone else at code, fresh talking about Argo CD, you know, find, find out more about hosted, get ups code, fresh.io. You know, you can find us in the Argo project, open, get ups community, you know, we're, we're, we're deep in the community for both Argo and get ups. So, you know, you can find us there as well. >>Well, let's do a follow up in when you're in town, so's only a couple months away and getting through the summer, it's already, I can't believe events are back. So it's really great to see face to face in the community. And there was responding. I mean, co con in October, I think that was kind of on the, that was a tough call and then get to see your own in Spain. I couldn't make it. Unfortunately, I had got COVID came down with it, but our team was there. Open sources, booming continues to go. The next level, new power dynamics are developing in a great way. Christian. Thanks for coming on, sharing your insights as the developer experience lead at code fresh. Thanks so much. >>Thank you, John. I appreciate it. >>Okay. This is a cube conversation. I'm John feer, host of the cube. Thanks for watching.