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