>>Keon Cloud Native Con kicks off in Detroit on October 24th, and we're pleased to have Stewart Miniman, who's the director of Market Insights, hi, at, for hybrid platforms at Red Hat back in the studio to help us understand the key trends to look for at the events. Do welcome back, like old, old, old >>Home. Thank you, David. It's great to, great to see you and always love doing these previews, even though Dave, come on. How many years have I told you Cloud native con, It's a hoodie crowd. They're gonna totally call you out for where in a tie and things like that. I, I know you want to be an ESPN sportscaster, but you know, I I, I, I still don't think even after, you know, this show's been around for so many years that there's gonna be too many ties into Troy. I >>Know I left the hoodie in my off, I'm sorry folks, but hey, we'll just have to go for it. Okay. Containers generally, and Kubernetes specifically continue to show very strong spending momentum in the ETR survey data. So let's bring up this slide that shows the ETR sectors, all the sectors in the tax taxonomy with net score or spending velocity in the vertical axis and pervasiveness on the horizontal axis. Now, that red dotted line that you see, that marks the elevated 40% mark, anything above that is considered highly elevated in terms of momentum. Now, for years, the big four areas of momentum that shine above all the rest have been cloud containers, rpa, and ML slash ai for the first time in 10 quarters, ML and AI and RPA have dropped below the 40% line, leaving only cloud and containers in rarefied air. Now, Stu, I'm sure this data doesn't surprise you, but what do you make of this? >>Yeah, well, well, Dave, I, I did an interview with at Deepak who owns all the container and open source activity at Amazon earlier this year, and his comment was, the default deployment mechanism in Amazon is containers. So when I look at your data and I see containers and cloud going in sync, yeah, that, that's, that's how we see things. We're helping lots of customers in their overall adoption. And this cloud native ecosystem is still, you know, we're still in that Cambridge explosion of new projects, new opportunities, AI's a great workload for these type type of technologies. So it's really becoming pervasive in the marketplace. >>And, and I feel like the cloud and containers go hand in hand, so it's not surprising to see those two above >>The 40%. You know, there, there's nothing to say that, Look, can I run my containers in my data center and not do the public cloud? Sure. But in the public cloud, the default is the container. And one of the hot discussions we've been having in this ecosystem for a number of years is edge computing. And of course, you know, I want something that that's small and lightweight and can do things really fast. A lot of times it's an AI workload out there, and containers is a great fit at the edge too. So wherever it goes, containers is a good fit, which has been keeping my group at Red Hat pretty busy. >>So let's talk about some of those high level stats that we put together and preview for the event. So it's really around the adoption of open source software and Kubernetes. Here's, you know, a few fun facts. So according to the state of enterprise open source report, which was published by Red Hat, although it was based on a blind survey, nobody knew that that Red Hat was, you know, initiating it. 80% of IT execs expect to increase their use of enterprise open source software. Now, the CNCF community has currently more than 120,000 developers. That's insane when you think about that developer resource. 73% of organizations in the most recent CNCF annual survey are using Kubernetes. Now, despite the momentum, according to that same Red Hat survey, adoption barriers remain for some organizations. Stu, I'd love you to talk about this specifically around skill sets, and then we've highlighted some of the other trends that we expect to see at the event around Stu. I'd love to, again, your, get your thoughts on the preview. You've done a number of these events, automation, security, governance, governance at scale, edge deployments, which you just mentioned among others. Now Kubernetes is eight years old, and I always hear people talking about there's something coming beyond Kubernetes, but it looks like we're just getting started. Yeah, >>Dave, It, it is still relatively early days. The CMC F survey, I think said, you know, 96% of companies when they, when CMC F surveyed them last year, were either deploying Kubernetes or had plans to deploy it. But when I talked to enterprises, nobody has said like, Hey, we've got every group on board and all of our applications are on. It is a multi-year journey for most companies and plenty of them. If you, you look at the general adoption of technology, we're still working through kind of that early majority. We, you know, passed the, the chasm a couple of years ago. But to a point, you and I we're talking about this ecosystem, there are plenty of people in this ecosystem that could care less about containers and Kubernetes. Lots of conversations at this show won't even talk about Kubernetes. You've got, you know, big security group that's in there. >>You've got, you know, certain workloads like we talked about, you know, AI and ml and that are in there. And automation absolutely is playing a, a good role in what's going on here. So in some ways, Kubernetes kind of takes a, a backseat because it is table stakes at this point. So lots of people involved in it, lots of activities still going on. I mean, we're still at a cadence of three times a year now. We slowed it down from four times a year as an industry, but there's, there's still lots of innovation happening, lots of adoption, and oh my gosh, Dave, I mean, there's just no shortage of new projects and new people getting involved. And what's phenomenal about it is there's, you know, end user practitioners that aren't just contributing. But many of the projects were spawned out of work by the likes of Intuit and Spotify and, and many others that created some of the projects that sit alongside or above the, the, you know, the container orchestration itself. >>So before we talked about some of that, it's, it's kind of interesting. It's like Kubernetes is the big dog, right? And it's, it's kind of maturing after, you know, eight years, but it's still important. I wanna share another data point that underscores the traction that containers generally are getting in Kubernetes specifically have, So this is data from the latest ETR survey and shows the spending breakdown for Kubernetes in the ETR data set for it's cut for respondents with 50 or more citations in, in by the IT practitioners that lime green is new adoptions, the forest green is spending 6% or more relative to last year. The gray is flat spending year on year, and those little pink bars, that's 6% or down spending, and the bright red is retirements. So they're leaving the platform. And the blue dots are net score, which is derived by subtracting the reds from the greens. And the yellow dots are pervasiveness in the survey relative to the sector. So the big takeaway here is that there is virtually no red, essentially zero churn across all sectors, large companies, public companies, private firms, telcos, finance, insurance, et cetera. So again, sometimes I hear this things beyond Kubernetes, you've mentioned several, but it feels like Kubernetes is still a driving force, but a lot of other projects around Kubernetes, which we're gonna hear about at the show. >>Yeah. So, so, so Dave, right? First of all, there was for a number of years, like, oh wait, you know, don't waste your time on, on containers because serverless is gonna rule the world. Well, serverless is now a little bit of a broader term. Can I do a serverless viewpoint for my developers that they don't need to think about the infrastructure but still have containers underneath it? Absolutely. So our friends at Amazon have a solution called Fargate, their proprietary offering to kind of hide that piece of it. And in the open source world, there's a project called Can Native, I think it's the second or third can Native Con's gonna happen at the cncf. And even if you use this, I can still call things over on Lambda and use some of those functions. So we know Dave, it is additive and nothing ever dominates the entire world and nothing ever dies. >>So we have, we have a long runway of activities still to go on in containers and Kubernetes. We're always looking for what that next thing is. And what's great about this ecosystem is most of it tends to be additive and plug into the pieces there, there's certain tools that, you know, span beyond what can happen in the container world and aren't limited to it. And there's others that are specific for it. And to talk about the industries, Dave, you know, I love, we we have, we have a community event that we run that's gonna happen at Cubans called OpenShift Commons. And when you look at like, who's speaking there? Oh, we've got, you know, for Lockheed Martin, University of Michigan and I g Bank all speaking there. So you look and it's like, okay, cool, I've got automotive, I've got, you know, public sector, I've got, you know, university education and I've got finance. So all of you know, there is not an industry that is not touched by this. And the general wave of software adoption is the reason why, you know, not just adoption, but the creation of new software is one of the differentiators for companies. And that is what, that's the reason why I do containers, isn't because it's some cool technology and Kubernetes is great to put on my resume, but that it can actually accelerate my developers and help me create technology that makes me respond to my business and my ultimate end users. Well, >>And you know, as you know, we've been talking about the Supercloud a lot and the Kubernetes is clearly enabler to, to Supercloud, but I wanted to go back, you and John Furrier have done so many of, you know, the, the cube cons, but but go back to Docker con before Kubernetes was even a thing. And so you sort of saw this, you know, grow. I think there's what, how many projects are in CNCF now? I mean, hundreds. Hundreds, okay. And so you're, Will we hear things in Detroit, things like, you know, new projects like, you know, Argo and capabilities around SI store and things like that? Well, you're gonna hear a lot about that. Or is it just too much to cover? >>So I, I mean the, the good news, Dave, is that the CNCF really is, is a good steward for this community and new things got in get in. So there's so much going on with the existing projects that some of the new ones sometimes have a little bit of a harder time making a little bit of buzz. One of the more interesting ones is a project that's been around for a while that I think back to the first couple of Cube Cuban that John and I did service Mesh and Istio, which was created by Google, but lived under basically a, I guess you would say a Google dominated governance for a number of years is now finally under the CNCF Foundation. So I talked to a number of companies over the years and definitely many of the contributors over the years that didn't love that it was a Google Run thing, and now it is finally part. >>So just like Kubernetes is, we have SEO and also can Native that I mentioned before also came outta Google and those are all in the cncf. So will there be new projects? Yes. The CNCF is sometimes they, they do matchmaking. So in some of the observability space, there were a couple of projects that they said, Hey, maybe you can go merge down the road. And they ended up doing that. So there's still you, you look at all these projects and if I was an end user saying, Oh my God, there is so much change and so many projects, you know, I can't spend the time in the effort to learn about all of these. And that's one of the challenges and something obviously at Red Hat, we spend a lot of time figuring out, you know, not to make winners, but which are the things that customers need, Where can we help make them run in production for our, our customers and, and help bring some stability and a little bit of security for the overall ecosystem. >>Well, speaking of security, security and, and skill sets, we've talked about those two things and they sort of go hand in hand when I go to security events. I mean, we're at reinforced last summer, we were just recently at the CrowdStrike event. A lot of the discussion is sort of best practice because it's so complicated. And, and, and will you, I presume you're gonna hear a lot of that here because security securing containers now, you know, the whole shift left thing and shield right is, is a complicated matter, especially when you saw with the earlier data from the Red Hat survey, the the gaps are around skill sets. People don't have the skill. So should we expect to hear a lot about that, A lot of sort of how to, how to take advantage of some of these new capabilities? >>Yeah, Dave, absolutely. So, you know, one of the conversations going on in the community right now is, you know, has DevOps maybe played out as we expect to see it? There's a newer term called platform engineering, and how much do I need to do there? Something that I, I know your, your team's written a lot about Dave, is how much do you need to know versus what can you shift to just a platform or a service that I can consume? I've talked a number of times with you since I've been at Red Hat about the cloud services that we offer. So you want to use our offering in the public cloud. Our first recommendation is, hey, we've got cloud services, how much Kubernetes do you really want to learn versus you want to do what you can build on top of it, modernize the pieces and have less running the plumbing and electric and more, you know, taking advantage of the, the technologies there. So that's a big thing we've seen, you know, we've got a big SRE team that can manage that for use so that you have to spend less time worrying about what really is un differentiated heavy lifting and spend more time on what's important to your business and your >>Customers. So, and that's, and that's through a managed service. >>Yeah, absolutely. >>That whole space is just taken off. All right, Stu I'll give you the final word. You know, what are you excited about for, for, for this upcoming event and Detroit? Interesting choice of venue? Yeah, >>Look, first of off, easy flight. I've, I've never been to Detroit, so I'm, I'm willing to give it a shot and hopefully, you know, that awesome airport. There's some, some, some good things there to learn. The show itself is really a choose your own adventure because there's so much going on. The main show of QAN and cloud Native Con is Wednesday through Friday, but a lot of a really interesting stuff happens on Monday and Tuesday. So we talked about things like OpenShift Commons in the security space. There's cloud Native Security Day, which is actually two days and a SIG store event. There, there's a get up show, there's, you know, k native day. There's so many things that if you want to go deep on a topic, you can go spend like a workshop in some of those you can get hands on to. And then at the show itself, there's so much, and again, you can learn from your peers. >>So it was good to see we had, during the pandemic, it tilted a little bit more vendor heavy because I think most practitioners were pretty busy focused on what they could work on and less, okay, hey, I'm gonna put together a presentation and maybe I'm restricted at going to a show. Yeah, not, we definitely saw that last year when I went to LA I was disappointed how few customer sessions there were. It, it's back when I go look through the schedule now there's way more end users sharing their stories and it, it's phenomenal to see that. And the hallway track, Dave, I didn't go to Valencia, but I hear it was really hopping felt way more like it was pre pandemic. And while there's a few people that probably won't come because Detroit, we think there's, what we've heard and what I've heard from the CNCF team is they are expecting a sizable group up there. I know a lot of the hotels right near the, where it's being held are all sold out. So it should be, should be a lot of fun. Good thing I'm speaking on an edge panel. First time I get to be a speaker at the show, Dave, it's kind of interesting to be a little bit of a different role at the show. >>So yeah, Detroit's super convenient, as I said. Awesome. Airports too. Good luck at the show. So it's a full week. The cube will be there for three days, Tuesday, Wednesday, Thursday. Thanks for coming. >>Wednesday, Thursday, Friday, sorry, >>Wednesday, Thursday, Friday is the cube, right? So thank you for that. >>And, and no ties from the host, >>No ties, only hoodies. All right Stu, thanks. Appreciate you coming in. Awesome. And thank you for watching this preview of CubeCon plus cloud Native Con with at Stu, which again starts the 24th of October, three days of broadcasting. Go to the cube.net and you can see all the action. We'll see you there.

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

>>The cube presents, Coon and cloud native con Europe 22, brought to you by the cloud native computing foundation. >>Welcome to vincia Spain in Coon cloud native con Europe, 2022. I'm Keith towns alongside en Rico senior. Etti senior it analyst for giong welcome back to the show en >>Rico. Thank you again for having me here. >>First impressions of QAN. >>Well, great show. As, as I mentioned before, I think that we are really in this very positive mode of talking with each other and people wanting to see, you know, the projects, people that build the projects at it's amazing. I mean, a lot of interesting conversation in the show floor and in the various sessions, very positive move. >>So this is gonna be a fun one. We have some amazing builders on the show this week, and none other than William Morgan, CEO of buoyant. What's your role in the link D project? >>So I was one of the original creators of link D but at this point I'm just the, the beautiful face of the project. >>Speaking of beautiful face of the project, linker D just graduated from as a CNCF project. >>Yeah, that's right. So last year we, we became the first service mesh to graduate in the CNCF. Very proud of that. And that's thanks, you know, largely to the incredible community around Linky that is just excited about the project and, you know, wants to talk about it and wants to be involved. >>So let's talk about the significance of that link D not the only service mesh project out there. Talk to me about the level effort to get it to the point that it's graduated. That's you don't see too many projects graduating CNCF in general. So let's talk about kind of the work needed to get Nier D to this point. >>Yeah. So, you know, the, the, the bar is high and it's mostly a measure, not necessarily of like the, the project being technically good or bad or anything, but it's really a measure of maturity of the community around it. So is it being adopted by organizations that are really relying on it in a critical way? Is it, you know, being adopted across industries, you know, is it having kind of a significant impact on the cloud native community? And so for us, you know, there was the, the work involved in that was really not any different from the work involved in, in kind of maintaining ity and growing the community in the first place, which is you try and make it really useful. You try and make it really easy to get started with you, try and be supportive and to, you know, have a, a friendly and welcoming community. And if you do those things and, you know, you kind of naturally get yourself to the point where it's a, it's a really strong community full of people who are excited about it. >>So from the of view of, you know, users adopting the, this technology, so we are talking about everybody, or do you see really, you know, large organization, large Kubernetes yeah. Clusters infrastructure adopting it. >>Yeah. So that's the answer to that is changed a little bit over time. But at this point we see Linky adoption across industries, across verticals, and we see it from very small companies to very large ones. So, you know, one of the talks I'm really excited about at this conference is from the folks at Xbox cloud gaming, who talked about, who are gonna talk about how they deployed Linky across, you know, 22,000 pods around the world to serve, you know, basically on demand video games, never a use case I would ever have imagined for Linky. And at the previous Kuan, you know, virtually Kuan EU, we had a whole keynote about how Linky was used to combat COVID 19. So all sorts of uses. And it really doesn't, you know, whether, whether it's a small cluster or large cluster it's equally applicable. >>Wow. So as we talk about link D service match, we obviously are gonna talk about security application control, etcetera. But in this climate Software supply chain is critical, right. And as we think about open source software supply chain, talk to us about the recent security audit of link dealer. >>Yeah. So one of the things that we do as part of a CNCF project, and also as part of, I, I think our relationship with our community is we have regular security audits, you know, where we, we engage security professionals who are very thorough and, you know, dig into all the details. Of course the source code is all out there, you know, so anyone can read through the code, but they'll build threat model analyses and things like that. And then we take their, their report and we publish it. We say, Hey, look, here's, you know, here's the situation. So we have earlier reports online, and this newest one was done by a company called trail of bits. And they built a whole threat model and looked through all the different ways that Linky could go wrong. And they always find issues. Of course, you know, it's, it would be very scary, I think, to get a report that was like, no, we didn't find yeah. Earth clean, you know? Yeah. Everything's fine. You know, should be okay. I don't know. Right. But they, you know, they did not find anything critical. They found some issues that we rapidly addressed and then, you know, everything gets written up in the report and, and then we publish it, you know, as part of an open source artifact >>Are, you let's say, you know, do they give you and add something? So if something happens so that you can act on the code before, you know, somebody else discovers the >>Yeah, yeah. They'll give you a preview of what they found. And then often, you know, it's not like you're going before the judge and the judge makes a judgment and then like off the jail, right. It's, it's a dialogue because they don't necessarily understand the project. Well, they definitely don't understand it as well as you do. So you are helping them, you know, understand which parts and, and your, you know, are, are interesting to look at from the security perspective, which parts are not that interesting. They do their own investigation of course, but it's a dialogue the entire time. So you do have an opportunity to say, oh, you told me that was a, a, a minor issue. I actually think that's larger or, or vice versa. You know, you, you think that's a big problem. Actually, we thought about that, and it's not a big problem because of whatever. So it's a collaborative process. >>So link D been around, like, when I first learned about service me link D was the project that I learned about. Yeah. It's been there for a long time, but just mentioned 22,000 clusters. That's just mind boggling pod, 22,000 pods, the pods. Okay. >>Clusters would be >>Great. Yeah. Yeah. Clusters would be great too, but filled 22 thousands pods, big deployment. That's the big deployment of link D but all the way down to the small, smallest set of pods as well. What are some of the recent project updates from of the learnings you bought back from the community and updated the, the project as a result? >>Yeah. So a big one for us, you know, on the topic of security link, a big driver of link adoption is security and, and less on the supply chain side and more on the traffic, like live traffic security. So things like mutual TLS. So you can encrypt the communication between pods and make sure it's authenticated. One of the recent feature additions is authorization policy. So you can lock down connections between services and you can say service a is only allowed to talk to service B. And I wanna do that. Not based on network identity, you know, and not based on like IP addresses, cuz those are spoof. And you know, we've kind of like as an industry moved, moved, we've gotten a little more advanced from that, but actually based on the workload identity, you know, as captured by the mutual TLS certificate exchange. So we give you the ability now to, to, to restrict the types of communication that are allowed to happen on your cluster. >>So, okay. This is what happened. What about the future? Can you give us, you know, into suggestion of what is going to happen in the medium and long term? >>I think we're done, you know, we graduated, so we're just gonna >>Stop there's >>What else is there to do? There's no grad school, you know? No, no. So for us, there's a clear roadmap ahead, continuing down the, the security realm, for sure. We've given you kind of the very first building block, which at the service level, but coming up in, in the two point 12 release, we'll have route based policy as well, as you can say, this service is only allowed to call these three, you know, routes on this end point and we'll be working later to do things like mesh expansion so we can run the data plane outside of Kubernetes. You know, so the control plane will stay in in Kubernetes, but the data plane will, you'll be able to run that on VMs and, and, and things like that. And then of course in the, you know, we're also starting to look at things like I like to make a fun of WAM a lot, but we are actually starting to look at WAM in, in the ways that that might actually be useful for Linky users. >>So we talk a lot about the flexibility of a project, like link D you can do amazing things with it from a security perspective, but we're talking still to a DevOps type cloud of, of, of developers who are spread thin across their skillset. How do you help balance the need for the flexibility, which usually becomes more nerd knobs and servicing a crowd that wants even higher levels of abstraction and simplicity. >>Yeah. Yeah. That's a great question. And this is, this is what makes Linky so unique in the service mesh spaces. We have a laser focus on simplicity and especially on operational simplicity. So our audience, you know, we can make it easy to install Linky, but what we really care about is when you're running it and you're on call for it and it's sitting in this critical, vulnerable part of your infrastructure, do you feel confident in that? Do you feel like you understand it? Do you feel like you can observe it? Do you feel like you can predict what it's gonna do? And so every aspect of Linky is designed to be as operationally simple as possible. So when we deliver features, you know, that's always our, our primary consideration is, you know, we have to reject the urge. You know, we have an urge as, as engineers to like want to build everything, you know, it's an ultimate platform to solve all problems and we have to really be disciplined and say, we're not gonna do that. >>We're gonna look at solving the minimum possible problem with a minimum set of features because we need to keep things simple. And, and then we need to look at the human aspect to that. And I think that's been a part of, of Link's success. And then on the buoyant side, of course, you know, I don't just work on link day. I also work on, on buoyant, which helps organizations adopt Linky and, and increasingly large organizations that are not service mesh experts don't wanna be service mesh experts that, you know, they wanna spend their time and energy developing their business, right. And, and building the business logic that powers their company. So for them, we have actually re recently introduced, fully managed. Linky where we can take on, even though Linky has to run on your cluster, right? The, the, the, the sidecar proxies has to be alongside your application. We can actually take on the operational burden of, of upgrades and trust, anchor rotation, and installation. And you can effectively treat it as a utility, right. And, and, and have a, a hosted, like, experience, even though the, the actual bits, at least most of them, not all of them, most of 'em have to live on your cluster. >>I love the focus of most CNCF projects, you know, it's, it's peanut butter or jelly, not peanut butter. Yeah. Trying to be become jelly. Right. What's the, what's the, what's the peanut butter to link D's jelly. Like where does link D stop and some of the things that customers should really consider yeah. When looking at service mesh. >>Yeah. No, that's a great way of looking at it. And I, I actually think that that philosophy comes from Kubernetes. I think Kubernetes itself, one of the reasons it was so successful is because it had some clearly delineated, it said, this is what we're gonna do. Right. And this is what we're not gonna do. So we're gonna do layer three, four networking. Right. But we're gonna stop there. We're not gonna do anything with layer seven. And that allowed the service mesh. So I guess if I were to go down the, the bread, the bread of the sandwich has Kubernetes, and then Linky is the, is the peanut butter, I guess, and then the jelly, you know, so I think the jelly is every other aspect of, of building a platform. Right. So if you are the, the audience for Linky, most of the time, it's a platform owners, right. They're building a platform, an internal platform for their developers to write code. And so, as part of that, of course, you've got Kubernetes, you've got Linky, but you've also got a C I CD system. You've also got a, you know, a code repository, if it's GitLab or, or GitHub or wherever you've got, you know, other kind of tools that are enforcing various other constraints. All of that is the jelly, you know, in the, this is, analogy's getting complicated now. And like the, the platform sandwich that, you know, that you're serving. >>So talk to us about trans and service mesh from the, from the, as we think of the macro. >>Yeah. Yeah. So, you know, it's been an interesting space because we were talking a little bit about, you know, about this before the show, but the, there was so much buzz, you know, and then what we, what we saw was basically it took two years for that buzz to become actual adoption, you know, and now a lot of the buzz is off on other exciting things. And the people who remain in the Linky space are, are very focused on, oh, I actually have a, a real problem that I need to solve and I need to solve it now. So that's been great. So in terms of broader trends, you know, I think one thing we've seen for sure is the service mesh space is kind of notorious for complexity, you know, and a lot of what we've been doing on the Linky side has been trying to, to reverse that, that, that idea, you know, because it doesn't actually have to be complex. There's interesting stuff you can do, especially when you get into the way we handle the sidecar model. It's actually really, it's a wonderful model operationally. It's really, it feels weird at first. And then you're like, oh, actually this makes my operations a lot easier. So a lot of the trends that I see at least for Linky is doubling down on the sidecar model, trying to make side cards as small and as thin as possible and try and make them, you know, kind of transparent to the rest of the application. So >>Well, William Morgan, one of the coolest Twitter handles I've seen at WM on Twitter, that's actually a really cool Twitter handle. Thank you, CEO of buoyant. Thank you for joining the cube again. Cube alum from Valencia Spain. I'm Keith towns, along with en Rico, and you're watching the cube, the leader in high tech coverage.