>>Hello everyone Welcome to the cubes coverage of cubic on cloud native come here in person in L A 2021. I'm john ferrier, host of the Cuban Dave Nicholson host cloud host for the cube and of course former host of the cube steve minutemen. Now at red hat stew, we do our normal keynote reviews. We had to have you come back first while hazard and red hat >>john it's phenomenal. Great to see you nice to have Dave be on the program here too. It's been awesome. So yeah, a year and a day since I joined Red hat and uh, I do miss you guys always enjoyed doing the interviews in the cube. But you know, we're still in the community and still interacting lots, >>but we love you too. And Davis, your new replacement and covering the cloud angles. He's gonna bring little stew mo jokes of the interview but still, we've always done the wrap up has always been our favorite interviews to do an analysis of the keynote because let's face it, that's where all the action is. Of course we bring the commentary, but this year it's important because it's the first time we've had an event in two years too. So a lot of people, you know, aren't saying this on camera a lot, but they're kind of nervous. They're worried they're weirded out. We're back in person again. What do I feel? I haven't seen people, I've been working with people online. This is the top story. >>Yeah, john I thought they did a really good job in the keynote this morning. Normally, I mean this community in general is good with inclusion. Part of that inclusion is hey, what are you comfortable with if your remote? We still love you and it's okay. And if you're here in person, you might see there's wrist bands of green, yellow, red as in like, hey, you okay with a handshake. You want to do there or stay the f away from me because I'm not really that comfortable yet being here and it's whatever you're comfortable with. That's okay. >>I think the inclusion and the whole respect for the individual code of conduct, C N C. F and limits Foundation has been on the front end of all those trends. I love how they're taking it to a whole nother level. David, I want to get your take because now with multi cloud, we heard the same message over and over again that hey, open winds, okay. Open winds and still changing fast. What's your take? >>Open absolutely wins. It's uh, it's the present. It's the future. I know in some of the conversations we've had with folks looking back over the last seven years, a lot of things have changed. Um, whenever I think of open source anything, I go back to the foundations of Lennox and I remember a time when you had to reboot a Linux server to re scan a scuzzy bus to add a new storage device and we all sort of put our penguin hats on and kind of ignored that for a while. And uh, and, and as things are developed, we keep coming into these new situations. Multi cluster management was a big, big point of conversation in the keynote today. It's fascinating when you start thinking about something that was once sort of a back room science experiment. Absolutely. It's the center of the enterprise now from a software >>from an open tour standpoint security has been one of those front and center things. One of the day, zero events that got a lot of buzz coming at the beginning of the week was secure supply chain. So with the Solar Wind act going in there, you know, we remember cloud, wait, can I trust it with the security? Open source right now. Open source and security go together. Open source and the security in the cloud all go together. So you know that that wave of open source, obviously one of the things that brought me to red hat, I'd had a couple of decades, you know, working within the enterprise and open source and that that adoption curve which went through a few bumps in the road over time and it took time. But today, I mean open sources have given this show in this ecosystem are such proof >>points of a couple things. I noticed one, I want to do a shout out for the folks who put a nice tribute for dan Kaminsky who has passed away and we miss him. We saw on the Cube 2019, I believe he's on the Cube that year with Adam on big influence, but the inclusiveness do and the community is changing. I think security has changed a lot and I want to get your guys take on this. Security has forced a lot of things happen faster data, open data. Okay. And kubernetes to get hardened faster stew. I know your team's working on it. We know what Azure and amazon is working on it. What do you guys think about how security's been forcing the advances in kubernetes and making that stable? >>Yeah. So john security, you know, is job one, it is everyone's responsibility. We talk about it from a container and kubernetes standpoint. We think we have a relatively good handle on what's happening in the kubernetes space red hat, we made an acquisition earlier this year of stack rocks, which was one of the leading kubernetes native security pieces. But you know, john we know security isn't just a moat anymore in a wall that you put up every single piece. You need to think about it. Um, I've got a person from the stack rocks acquisition actually on my team now and have told him like hey, you need to cross train all of us. We need to understand this more from a marketing standpoint, we need to talk about it from a developer standpoint. We need to have consideration of it. It's no longer, hey, it works okay on my machine. Come on, It needs to go to production. We all know this shift left is something we've been talking about for many years. So yes, security, security, security, we cannot overemphasize how important is um, you know, when it comes to cooper, I think, you know, were relatively mature, we're crossing the chasm, the adoption numbers are there, so it's not an impediment anymore. >>It's totally next level. I don't agree with this too. David, get your thoughts on this whole adoption um, roadmap that put it together, one of the working groups that we interviewed has got that kind of navigate, kinda like trailheads for salesforce, but that speaks to the adoption by mainstream enterprises, not the hard core, >>you know, >>us devops guys, but like it goes into mainstream main main street enterprise had I. T. Department and security groups there, like we got a program faster. How do you see the cloud guys in this ecosystem competing and making that go faster. >>So it's been interesting over the last decade or more often, technology has been ahead of people's comfort level with that technology for obvious reasons, it's not just something went wrong, it's something went wrong. I lost my job. Really, really bad things happened. So we tend to be conservative. Rightfully so in the sometimes there are these seminal moments where a shift happens go back sort of analogous go back to a time when people's main concern with VM ware was how can I get support from Microsoft and all of a sudden it went from that within weeks to how can I deploy this in my enterprise very, very quickly. And I'm fascinated by this concept of locking down the supply chain of code, uh sort of analogous to https, secure, http. It's the idea of making sure that these blocks of code are validated and secure as they get implemented. You mentioned, you mentioned things like cluster and pad's security and infrastructure security. >>Well, David, you brought up a really good point. So get off is the instance creation of that. How can I have my infrastructure as code? How can I make sure that I don't have drift? It's because I could just, it'll live and get hub and therefore it's version controlled. If I try to do something, it will validate that it's there and keep me on version because we know john we talked about it for years on the cube, we've gone beyond human scale if I don't build automation into it, if I don't have the guard rails in place because humans will mess things up so we need to make sure that we have the processes and the automation in place and kubernetes was built for that automation at its core, putting in, we've seen get up the Argosy, D was only went graduated, you know, the one dato was supported as coupon europe. Earlier this year, we already had a number of our customers deploying it using it. Talking publicly >>about it too. I want to get the kid apps angle and that's a good call out there and, and mainly because when we were on the cute, when you work, you post with with us, we were always cheerleading for Cuban. It we love because we've been here every single coupon. We were one saying this is gonna be big trust us and it is, it happens to so, but now we've been kind of, we don't have to sell it anymore. We don't, I mean not that we're selling it, but like we don't have to be a proponent of something we knew was going to happen, it happened. You're now work for a vendor red hat you talk to customers. What is that next level conversation look like now that they know it's real, they have to do it. How is the tops and then modern applications development, changing. What are your observations? Can you share with us from a redhead perspective as someone who's talking to customers, you know, what does real look like? >>Yeah. So get off is a great example of that. So, you know, certain of our government agencies that we work with, you know, obviously very secured about, you know, we want zero trust who do we put in charge of things. So if they can have, you know that that source of truth and know that that is maintained and lockdown and not await some admin is gonna mess something up on us either maliciously or oops, by accident or anything in between. That's why they were pushing that adoption of that kind of technology. So absolutely they, for the most part john they don't want to have to think about the infrastructure piece anymore. What if developers want the old past days was I want to be able to, you know, write once deploy anywhere, live anywhere, containers helps that a little bit. We even have in the container space. Now you can, you can use a service deployment model with Okay. Natives, the big open source project that, you know, VM ware ourselves are working on google's involved in it. So, you know, having us be able to focus on the business and not, you know, running the plumbing anymore. >>That's exactly, that's exactly, that's what we're so psyched for. Okay guys, let's wrap this up and and review the keynote day will start with you. What do you think of the keynote? What were the highlights? What do you take away from the taste keynote? >>So you touched on a couple of things, uh inclusion from all sorts of different angles. Really impressive. This sort of easing back into the world of being face to face. I think they're doing a fantastic job at that. The thing that struck me was something I mentioned earlier. Um moving into multi cluster management in a way that really speaks to enterprise deployments and the complexity of enterprise deployments moving forward? It's not just, it's not just, I'm a developer, I'm using resources in the cloud. I'm doing things this way, the rest of the enterprises doing it a legacy way. It's really an acknowledgement that these things are coming together increasingly. That's what really struck me >>to do. What's your takeaway from the end? >>So there's been a discussion in the industry, you know, what do the next million cloud customers look like we've crossed the chasm on kubernetes. One of the things they announced the keynote is they have a new associate level certification because I tell you before the keynote, I stopped by the breakfast area, saturday table, talk to a couple people. One guy was like, hey, I'm been on amazon for a bunch of years, but I'm a kubernetes newbie, I'm here to learn about that. It's not the same person that five years ago was like, I'm gonna grab all these projects and pull them down from getting, build my stack and you know, have a platform team to manage it from a red hat standpoint, we're delivering our biggest growth areas in cloud services where hey, I've got an SRE team, they can manage all that because can you do it? Sure you got people maybe you'll hire him, but wouldn't you rather have them work on, you know, that security initiative or that new application or some of these pieces, you know, what can you shift to your vendor? What can you offload from your team because we know the only constant is that things are gonna there's gonna be gonna be new pieces and I don't want to have to look at, oh there's another 20 new projects and how does that fit? Can I have a partner or consultant in sc that can help me integrate that into my environment when it makes sense for me because otherwise, oh my God, cloud, So much innovation. How do I grasp what I want? >>Great stuff guys, I would just say my summary is that okay? I'm excited this community has broken through the pandemic and survived and thrived people were working together during the pandemic. It's like a V. I. P. Event here. So that my keynote epiphany was this is like the who's who some big players are here. I saw Bill Vaz from amazon on the on the ground floor on monday night, He's number two at a W. S. I saw some top Vcs here. Microsoft IBM red hat the whole way tracks back. Whole track is back and it's a hybrid event. So I think we're here for the long haul with hybrid events where you can see a lot more in person, V. I. P. Like vibe people are doing deals. It feels alive too and it's all open. So it's all cool. And again, the team at C. N. C. F. They do an exceptional job of inclusion and making people feel safe and cool. So, great job. Thanks for coming on. I appreciate it. Good stuff. Okay. The keynote review from the cube Stupid Man shot for Dave Nicholson. Thanks for watching >>mm mm mm.

>>Hello and welcome back to the cubes coverage of dr khan 2021. I'm john for your host of the cube. Great guests here cube alumni Stephen Chin, vice president of developer relations for jay frog Stephen, great to see you again this remote this time this last time was in person. Our last physical event. We had you in the queue but great to see you. Thanks for coming in remotely. >>No, no, I'm very glad to be here. And also it was, it was awesome to be in person at our s a conference when we last talked and the last year has been super exciting with a whole bunch of crazy things like the I. P. O. And doing virtual events. So we've, we're transitioning to the new normal. We're looking forward to things getting to be hybrid. >>Great success with jay frog. We've been documenting the history of this company, very developer focused the successful I. P. O. And just the continuation that you guys have transitioned beautifully to virtual because you know, developer company, it runs virtual, but also you guys have been all about simplicity for developers and and we've been talking for many, many years with you guys on this. This is the theme that dr khan again, this is a developer conference, not so much an operator conference, but more of a deva deV developer focused. You guys have been there from the beginning, um nationally reported on it. But talk about jay Frog and the Doctor partnership and why is this event so important for you? >>Yeah. So I think um like like you said, jay Frog has and always is a developer focused company. So we we build tools and things which which focus on developer use cases, how you get your code to production and streamlining the entire devoPS pipeline. And one of the things which which we believe very strongly in and I think we're very aligned with with doctor on this is having secure clean upstream dependencies for your Docker images for other package and language dependencies and um you know, with the announcement of dr khan and dr Hubbs model changing, we wanted to make sure that we have the best integration with doctor and also the best support for our customers on with Docker hub. So one of the things we did strategically is um, we um combined our platforms so um you can get the best in class developer tools for managing images from Docker. Um everyone uses their um desktop tools for for building and managing your containers and then you can push them right to the best container registry for managing Docker Images, which is the jay frog platform. And just like Docker has free tools available for developers to use. We have a free tier which integrates nicely what their offerings and one of the things which we collaborate with them on is for anybody using our free tier in the cloud. Um there's there's no limits on the Docker images. You can pull no rate limiting, no throttling. So it just makes a clean seamless developer experience to to manage your cloud native projects and applications. >>What's the role of the container registry in cloud NATO? You brought that up? But can you just expand on that point? >>Yeah. So I think when you when you're doing deployments to production, you want to make sure both that you have the best security so that you're making sure that you're scanning and checking for vulnerabilities in your application and also that you have a complete um traceability. Basically you need a database in a log of everything you're pushing out to production. So what container registries allow you to do is um they keep all of the um releases all of the Docker images which are pushing out. You can go back and roll back to a previous version. You can see exactly what's included in those Docker images. And we jay frog, we have a product called X ray which does deep scanning of container images. So it'll go into the Docker Image, it'll go into any packages installed, it'll go into application libraries and it does kind of this onion peel apart of your entire document image to figure out exactly what you're using. Are there any vulnerabilities? And the funny thing about about Docker Images is um because of the number of libraries and packages and installed things which you haven't given Docker Image. If you just take your released Docker Image and let it sit on the shelf for a month, you have thousands of vulnerabilities, just just buy it um, by accruing from different reported zero day vulnerabilities over time. So it's extremely important that you, you know what those are, you can evaluate the risk to your organization and then mitigated as quickly as possible. If there is anything which could impact your customers, >>you bring up a great point right there and that is ultimately a developer thing that's been, that's generational, you know what generation you come from and that's always the problem getting the patches in the old days, getting a new code updated now when you have cloud native, that's more important than ever. And I also want to get your thoughts on this because you guys have been early on shift left two years ago, shift left was not it was not a new thing for you guys ever. So you got shift left building security at the point of coding, but you're bringing up a whole another thing which is okay automation. How do you make it? So the developments nothing stop what they're doing and then get back and say, okay, what's out there and my containers. So so how do you simplify that role? Because that's where the partnership, I think really people are looking to you guys and Dakar on is how do you make my life easier? Bottom line, what's it, what's it, what's it about? >>Yeah. So I I think when you when you're looking at trying to manage um large applications which are deployed to big kubernetes clusters and and how you have kind of this, this um all this infrastructure behind it. One of the one of the challenges is how do you know what you have that in production? Um So what, how do you know exactly what's released and what dependencies are out there and how easily can you trace those back? Um And one of the things which we're gonna be talking about at um swamp up next week is managing the overall devops lifecycle from code all the way through to production. Um And we we have a great platform for doing package management for doing vulnerability scanning, for doing um ci cd but you you need a bunch of other tools too. So you need um integrations like docker so you can get trusted packages into your system. You need integrations with observe ability tools like data, dog, elastic and you need it some tools for doing incident management like Patriot duty. And what we've, what we've built out um is we built out an ecosystem of partner integrations which with the J frog platform at the center lets you manage your entire and and life cycle of um devops infrastructure. And this this addresses security. It addresses the need to do quick patches and fixes and production and it kind of stitches together all the tools which all of the successful companies are using to manage their fast moving continuous release cycle, um and puts all that information together with seamless integration with even developer tools which um which folks are using on a day to day basis, like slack jeer A and M. S. Teams. >>So the bottom line then for the developer is you take the best of breed stuff and put it, make it all work together easily. That right? >>Yeah. I mean it's like it's seamless from you. You've got an incidents, you click a button, it sticks Ajira ticket in for you to resolve. Um you can tie that with the code, commits what you're doing and then directly to the security vulnerability which is reported by X ray. So it stitches all these different tools and technologies together for a for a seamless developer experience. And I think the great relationship we have with Docker um offers developers again, this this best in class container management um and trusted images combined with the world's best container registry. >>Awesome. Well let's get into that container issue products. I think that's the fascinating and super important thing that you guys solve a big problem for. So I gotta ask you, what are the security risks of using unverified and outdated Docker containers? Could you share your thoughts on what people should pay attention to because if they got unverified and outdated Docker containers, you mentioned vulnerabilities. What are those specific risks to them? >>Yeah, so I there's there's a lot of um different instances where you can see in the news or even some of the new government mandates coming out that um if you're not taking the right measures to secure your production applications and to patch critical vulnerabilities and libraries you're using, um you end up with um supply chain vulnerability risks like what happened to solar winds and what's been fueling the recent government mandates. So I think there's a there's a whole class of of different vulnerabilities which um bad actors can exploit. It can actually go quite deep with um folks um exploiting application software. Neither your your company or in other people's systems with with the move to cloud native, we also have heavily interconnected systems with a lot of different attack points from the container to the application level to the operating system level. So there's multiple different attack vectors for people to get into your software. And the best defense is an organization against security. Vulnerabilities is to know about them quickly and to mitigate them and fix them in production as quickly as possible. And this requires having a fast continuous deployment strategy for how you can update your code quickly, very quick identification of vulnerabilities with tools like X ray and other security scanning tools, um and just just good um integration with tools developers are using because at the end of the day it's the developers who both are picking the libraries and dependencies which are gonna be pushed into production and also they're the ones who have to react and and fix it when there's a uh production incident, >>you know, machine learning and automation. And it's always, I love that tech because it's always kind of cool because it's it's devops in action, but you know, it's it's not like a silver bullet, your machine, your machine learning is only as good as your your data and the code is written on staying with automation. You're not automating the right things or or wrong things. It's all it's all subjective based on what you're doing and you know Beauty's in the eye of the beholder when you do things like that. So I wanna hear your thoughts on on automation because that's really been a big part of the story here, both on simplicity and making the load lighter for developers. So when you have to go out and look at modifying code updates and looking at say um unverified containers or one that gets a little bit of a hair on it with with with more updates that are needed as we say, what do you what's the role of automation? How do you guys view that and how do you talk to the developers out there when posturing for a strategy on and a playbook for automation? >>Yeah, I think you're you're touching on one of the most critical parts of of any good devops um platform is from end to end. Everything should be automated with the right quality gates inserted at different points so that if there's a um test failure, if you have a build failure, if you have a security vulnerability, the the automatic um points in there will be triggered so that your release process will be stopped um that you have automated rollbacks in production um so that you can make sure that their issues which affect your customers, you can quickly roll back and once you get into production um having the right tools for observe ability so that you can actually sift through what is a essentially a big data problem. So with large systems you get so much data coming back from your application, from the production systems, from all these different sources that even an easy way to sift through and identify what are the messages coming back telling you that there's a problem that there's a real issue that you need to address versus what's just background noise about different different processes or different application alerts, which really don't affect the security of the functionality of your applications. So I think this this end to end automation gives you the visibility and the single pane of glass to to know how to manage and diagnose your devops infrastructure. >>You know, steve you bring up a great point. I love this conversation because it always highlights to me why I love uh Coop Con and Cloud Native con part of the C N C F and dr khan, because to me it's like a microcosm of two worlds that are living together. Right? You got I think Coop khan has proven its more operated but not like operator operator, developer operators. And you got dr khan almost pure software development, but now becoming operators. So you've got that almost those two worlds are fusing together where they are running together. You have operating concerns like well the Parachute open, will it work? And how do I roll back these roll back? These are like operating questions that now developers got to think about. So I think we're seeing this kind of confluence of true devops next level where you can't you can be just a developer and have a little bit of opposite you and not be a problem. Right? Or or get down under the under the hood and be an operator whenever you want. So they're seeing a flex. What's your thoughts on this is just more about my observation kind of real time here? >>Yeah, so um I think it's an interesting, obviously observation on the industry and I think you know, I've been doing DEVOPS for for a long time now and um I started as a developer who needed to push to production, needed to have the ability to to manage releases and packages and be able to automate everything. Um and this naturally leads you on a path of doing more operations, being able to manage your production, being able to have fewer incidents and issues. Um I think DEVOPS has evolved to become a very complicated um set of tools and problems which it solves and even kubernetes as an example. Um It's not easy to set up like setting up a kubernetes cluster and managing, it is a full time job now that said, I think what you're seeing now is more and more companies are shifting back to developers as a focus because teams and developers are the kingmakers ends with the rise of cloud computing, you don't need a full operations team, you don't need a huge infrastructure stack, you can you can easily get set up in the cloud on on amazon google or as your and start deploying today to production from from a small team straight from code to production. And I think as we evolve and as we get better tools, simpler ways of managing your deployments of managing your packages, this makes it possible for um development teams to do that entire site lifecycle from code through to production with good quality checks with um good security and also with the ability to manage simple production incidents all by themselves. So I think that's that's coming where devoPS is shifting back to development teams. >>It's great to have your leadership and your experience. All right there. That's a great call out, great observation, nice gym there. I think that's right on. I think to get your thoughts if you don't mind going next level because you're, you're nailing what I see is the successful companies having these teams that could be and and workflows and have a mix of a team. I was talking about Dana Lawson who was the VP of engineering get up and she and I were riffing on this idea that you don't have to have a monolithic team because you've got you no longer have a monolithic environment. So you have this microservices and now you can have these, I'm gonna call micro teams, but you're starting to see an SRE on the team, that's the developer. Right? So this idea of having an SRE department maybe for big companies, that could be cool if you're hyper scalar, but these development teams are having certain formations. What's your observation to your customer base in terms of how your customers are organizing? Because I think you nailed the success form of how teams are executing because it's so much more agile, you get the reliability, you need to have security baked in, you want end to end visibility because you got services starting and stopping. How are teams? How are you seeing developers? What's the state of the art in your mind for formation? >>Yeah, so I think um we we work with a lot of the biggest companies who were really at the bleeding edge of innovation and devoPS and continuous delivery. And when you look at those teams, they have, they have very, very small teams, um supporting thousands of developers teams um building and deploying applications. So um when you think of of SRE and deVOPS focus there is actually a very small number of those folks who typically support humongous organizations and I think what we're hearing from them is their increasingly getting requirements from the teams who want to be self service, right? They want to be able to take their applications, have simple platforms to deploy it themselves to manage things. Um They don't they don't want to go through heavy way processes, they wanted to be automated and lightweight and I think this is this is putting pressure on deVOPS teams to to evolve and to adopt more platforms and services which allow developers to to do things themselves. And I think over time um this doesn't this doesn't get rid of the need for for devops and for SRE roles and organizations but it it changes because now they become the enablers of success and good development teams. It's it's kind of like um like how I. T. Organizations they support you with automated rollouts with all these tools rather than in person as much as they can do with automation. Um That helps the entire organization. I think devops is becoming the same thing where they're now simplifying and automating how developers can be self service and organizations. >>And I think it's a great evolution to because that makes total sense because it is kind of like what the I. T. Used to do in the old days but its the scale is different, the services are different, the deVOPS tools are different and so they really are enabling not just the cost center there really driving value. Um and this brings up the whole next threat. I'd love to get your thoughts because you guys are, have been doing this for developers for a while. Tools versus platform because you know, this whole platform where we're a platform were control plane, there's still a need for tooling for developers. How do we thread the needle between? What's, what's good for a tool? What's good for a platform? >>Yeah, So I I think that um, you know, there's always a lot of focus and it's, it's easier if you can take an end to end platform, which solves a bunch of different use cases together. But um, I I think a lot of folks, um, when you're looking at what you need and how you want to apply, um, devops practices to your organization, you ideally you want to be able to use best in breed tools to be able to solve exactly what your use cases. And this is one of the reasons why as a company with jay frog, we we try to be as open as possible to integrations with the entire vendor ecosystem. So um, it doesn't matter what ci cd tool you're using, you could be using Jenkins circle, ci spinnaker checked on, it doesn't matter what observe ability platform you're using in production, it doesn't matter what um tools you're using for collaboration. We, we support that whole ecosystem and we make it possible for you to select the the best of breed tools and technologies that you need to be successful as an organization. And I think the risk is if, if you, if you kind of accept vendor lock in on a single platform or or a single cloud platform even um then you're, you're not getting the best in breed tools and technologies which you need to stay ahead of the curve and devops is a very, very fast moving um, um, discipline along with all the cloud native technologies which you use for application development and for production. So if you're, if you're not staying at the bleeding edge and kind of pushing things forward, then you're then you're behind and if you're behind, you're not be able to keep up with the releases, the deployments, you need to be secure. So I think what you see is the leading organizations are pushing the envelope on on security, on deployment and they're they're using the best tools in the industry to make that happen. >>Stephen great to have you on the cube. I want to just get your thoughts on jay frog and the doctor partnership to wrap this up. Could you take them in to explain what's the most important thing that developers should pay attention to when it comes to security for Docker images? >>Yeah. So I think when you're when you're developer and you're looking at your your security strategy, um you want tools that help you that come to you and that help you. So you want things which are going to give you alerts in your I. D. With things which are going to trigger your in your Ci cd and your build process. And we should make it easy for you to identify mitigate and release um things which will help you do that. So we we provide a lot of those tools with jay frog and our doctor partnership. And I think if you if you look at our push towards helping developers to become more productive, build better applications and more secure applications, this is something the entire industry needs for us to address. What's increasingly a risk to software development, which is a higher profile vulnerabilities, which are affecting the entire industry. >>Great stuff. Big fan of jay frog watching you guys be so successful, you know, making things easy for developers is uh, and simpler and reducing the steps it takes to do things as a, I say, is the classic magic formula for any company, Make it easier, reduce the steps it takes to do something and make it simple. Um, good success formula. Great stuff. Great to have you on um for a minute or two, take a minute to plug what's going on in jay frog and share what's the latest increase with the company, what you guys are doing? Obviously public company. Great place to work, getting awards for that. Give the update on jay frog, put a plug in. >>Yeah. And also dr Frog, I've been having a lot of fun working at J frog, it's very, very fast growing. We have a lot of awesome announcements at swamp up. Um like the partnerships were doing um secure release bundles for deployments and just just a range of advances. I think the number of new features and innovation we put into the product in the past six months since I. P. O. Is astounding. So we're really trying to push the edge on devops um and we're also gonna be announcing and talking about stuff that dr khan as well and continue to invest in the cloud native and the devops ecosystem with our support of the continuous delivery foundation and the C. N C F, which I'm also heavily involved in. So it's it's exciting time to be in the devoPS industry and I think you can see that we're really helping software developers to improve their art to become better, better at release. Again, managing production applications >>and the ecosystem is just flourishing. It's only the beginning and again Making bring the craft back in Agile, which is a super big theme this year. Stephen. Great, great to see you. Thanks for dropping those gems and insights here on the Cube here at Dr. 2021 virtual. Thanks for coming on. >>Yeah. Thank you john. >>Okay. Dr. 2020 coverage virtual. I'm John for your host of the Cube. Thanks for watching. Mhm. Mhm. Yeah.

>>from around the >>globe, it's the >>cube with coverage of Kublai >>khan and cloud Native con, europe 2021 virtual brought to you by red hat. The cloud >>native computing >>foundation and ecosystem partners. Welcome back to the cubes coverage of Yukon 21 cloud native con part of the C n C f s event. This is the cubes continuing coverage. You got a great guest cube alumni entrepreneurs to borrow founder and ceo of up bound. Great to see you remotely too bad. We're not in person. But soon the pandemic Is right around the corner will be post pandemic with searing events are coming back. Great to see you. Thanks for coming on for coop con 21 >>Good, good to be back on the cube, john >>great to see you. You know, I've always loved your career, what you've been doing with that many conversations on the Cuban. Also in person, you're the creative rook and cross plane um, C N C F projects there. Um great venture, really part of this cloud native revolution that's happening, you were early on and the history of your career, but now you're seeing it go mainstream. Let's get into that on this session, because I really want to dig into this across cloud and now get ops is hugely popular. This is kind of what you call day to operate your ongoing, this is the future. This is a new environment. Before we get going, talk about the update on your in what's new with cross plane. >>Uh, So cross plane is growing as you know, it's a multi cloud control plane that essentially lets you uh you can connect it up to all the different infrastructure vendors and lets you manage infrastructure in a consistent way consistent with what, you know, what we do with the tops and and on the kubernetes ap I um and so the community has been growing tremendously. We've just applied for it together, the incubation status at the CNC F and really happy with all the progress around it. It's, it's such an amazing journey we've been on with cross plane, >>you know, it's funny you watch all the, the evolution of the cloud in the early days, it was, what is cloud, the big debate, people define what cloud is that? It was Oh yeah, clouds great. You can, you know, start up cloud developers, Greenfield, then it became enterprise cloud around 2015. Now, you know, today the cloud is not so much, you know, moving to the cloud as it was in 2015, it's like scaling and cloud, that is true enterprise grade. Um real serious operational security impacts multiple resources and this is where cross cloud comes in or, or, you know, I see hybrid clouds operating model, everyone has agreed on that. That's the architecture, but that also brings in assumes multiple clouds, right? This is where the new kind of control plane or you guys called cross cloud management kicks in. This is an enterprise priority. From what I can see. Do you agree with that? Can you share your commentary on how much our enterprises of prioritizing cross cloud management? Because that seems to be the Hot one. What's your take on us? >>Yeah, the way, the way we see it is that and we see this with customers and we see those folks in the community. Almost every enterprise we talked to is modernizing their I. T. You know, that, as you said, they're not going to cloud, they're already in cloud, but they're doing so many more things to kind of accelerate the pace of innovation and reduce the time for them to ship applications, which is now a fundamental part or fundamental measure uh of their success. Right. And so what we're seeing is that they're organizing into platform teams internally, and these teams are the ones that own the cloud accounts, they're the ones that are responsible for deploying infrastructure cross, whether it's cross cloud or hybrid cloud. Um and these teams are essentially organizing to build what looks like an internal platform and a key ingredient of this. Internal platform is a control plane and this is what enables getups. You see kubernetes as a control plane, that's in there, um it's it's the piece that's allowing them to actually connect to different clouds. It's the piece that's allowing them to manage their infrastructure, whether it's on premise or in cloud, it's the thing that's allowing them to do day to operations, all of that's happening in an interesting way. It's, it's happening within the enterprise. It is their own platform and it layers on top of the back and infrastructure that they're using, whether it's cloud providers or hybrid, you know, infrastructure, it's happening in a way that's enterprise from the enterprise and going out to the vendors, which is a little different model than we've seen in the past. And that's where multi cloud tends to come in and multi vendor or heterogeneity in general. Uh we see that very, very commonly in in the enterprise, >>you know, I think you're exactly right. That's classic market evolution in computer industry, you know, multi multi vendors, ultimately when things start to settle in on the massive growth. Hybrid cloud, however, is really kind of where the action is today. And you can see people struggling and innovating around the area of continuous operations and as you can use development develops concept. But the problem is that as they realize, well stuffs in production, it's in the public cloud, its on premises, you know, this, the operational piece starts to rear its head and we gotta fix that. And then they connect the dots a saying, if multi cloud is coming, which people generally agree upon, then they go, if we don't clean this up, we're gonna be screwed. That's generally the consensus that I can that I hear from people so explain, explain with the rise of multi cloud what cross plane is, I mean, what is cross playing about? Give us an overview around this. >>So, I mean there's a lot of ways to describe this, but we see it as like the rise of platform engineering, there's a lot happening around people building their own platforms that layer on top of cloud, which happens to also be multi vendor and multi cloud. So when you're building a platform in an enterprise that can talk to amazon that can talk to Microsoft Azure that can talk to your on premise infrastructure, whether it's VM ware or open shift, you need a, you need a layer that is able to orchestrate and deploy and manage and deal with day to operations, Right. That that is an important piece. It's the piece that is, you know, the way you can enforce your policies, you can set out your controls, whether your compliance, do your compliance and governance and essentially sell sell served uh this to your developers so that they can actually get productive and deploy applications on on this platform. And we see cross plane and what what Kubernetes has started with a control plane as a critical approach in this, in this new platform. In fact, the approach that's kind of pioneered by kubernetes with the kubernetes Api and control plane is now becoming the dominant way of managing infrastructure and deploying applications on it. This is you hear this in different ways, like this is why get off has become popular. Get Office is a really great thing. It's a way to essentially let you manage infrastructure through, you know, configuration that's stored in GIT repositories. But the thing that it connects to is a control plane that's going to make it happen, right? And we see that with kubernetes uh predominantly with kubernetes. Right. And so what cross plane does is lets you extend the getups approach and the management approach that's pioneered by the kubernetes community to the entire surface area of cloud. So not only can you deploy your containers using get apps, you can actually manage through the tops VMS server lists, databases and cloud Hybrid environments. Multi cloud environments. You know, even, you know, your load balances that are on premise could be managed through tops anything that speaks in a p I could be managed to get off if you go through a project like cross plane. Now, that part is that part is where we're seeing the most success right now. We're seeing a lot of people that are adopting these approaches to managing infrastructure while they're building their platforms and they're pulling in cross plains, we're seeing massive end user adoption of cross plane right >>now. I want to get into this. I want to get this impact of the control playing but before we get there I want a real quick while I got you an expert. I know this coupon. You don't need to explain what get upset. Everyone knows what that is. But for the folks that aren't aren't aren't in the community, I want to grab the sound bite if you don't mind. Could you define what is getups? >>Uh huh. So so get up is somewhat of a marketing term. Uh but the way I interpreted is essentially storing your configuration in a git repository. Are you using, you know, uh versioning techniques that are pioneered to manage code, right? Whether using Pr flows, storing things and get doing the collaboration of what changes happen in get and then having that be essentially mirrored to uh control plane that is able to implement the declarative configuration that you've specified. So a good example of this is if you wanted to deploy, say, you know, start up a cluster of kubernetes cluster in the cloud vendor and then run applications on it and then configure it to connect to databases. You can describe your intent and store it and get collaborate with your team members on it, make sure it's all correct. And then through getups pipeline, you're able to take those, you know, essentially, configuration and then apply it via control plane onto your vendor of choice. Right? That's that's the style. It's great because, you know, get is a great place to store configuration. It's a great place to collaborate. There are amazing tools around pr flows, pull request flows. They're amazing tools for audit ability and versioning and you get to leverage all of those when you are deploying infrastructure that runs your entire >>enterprise. Yeah. And I would also add to that. I I explain it simply for people that aren't in the weeds on the tech is think of it like a QA for srs it's like you need to manage the infrastructure because we're talking about devops infrastructure as code, we're programming infrastructure. So you've got to have some sort of process. And I think this brings up my next point about this control plane, because you mentioned um Cross plans has these nice has this nice uh program to it. Most people write their own code, they'll like they'll they'll like do homegrown work to create in their platform, mainly because there's gaps in there. Can you comment on how you guys are different than someone saying? I'm just gonna write my own code and do my own thing, my own platform team. I don't need cosplaying what I need you for. I'm gonna do it myself. >>So what we see predominantly is folks that are doing get ops or infrastructure as code and setting up pipelines for their compute workloads and specifically for containers. Right. And then, like you said, they're actually writing homegrown scripts or doing Tara forum or doing other things that are on the side to deploy. The other parts, uh including, you know, state full workloads or things that are running across a I M L on premise, hybrid, all of that stuff is done organically on the side of this beautiful path. Forget ops right. What we're doing with cross plane is essentially letting you bring all of the things that you're managing organically into the same pipelines with get offs. So you're able to actually normalize on a single approach for management for orchestration of infrastructure and applications. So you're you're able to, you know, get rid of your custom scripts and use a P I. S to define what your developers should do. You're able to, you know, use the mechanisms that are in the tools that are available to you forget ups and for the in the company's ecosystem to manage the entire surface area of, you know, infrastructure that you're managing within the enterprise in a consistent way. Right? That's where cross money comes in cross plane enables you to extend the control plane of kubernetes to manage everything that's offered by amazon and Microsoft and google and VM ware and open shift and red hat, Everything else can become falls into the same orchestrator, the same control plane that's managing it all and you can access it and give it to your developers in a safe way using, you know, get ups like approaches. >>You know, I've heard horror stories where people pushed new codes, trivial stuff and then all of a sudden breaks because um, code or script was written for a different purpose, but the impact was created into a small little dependency, but it's essentially the human error aspect of software. It's like, well we didn't really kind of see that coming, but at that point that script worked. Now this new thing, something trivial and easy breaks because and then it crashes. This is the kind of day to operations >>that very amounting >>about. Is that right? >>That's that's very much that's very much the case. And we see a lot of people kind of normalizing on templates and scripts, you know, where it's like, okay, you want to deploy database, here's a we'll open a ticket. Uh, and then some human runs, uh, you know, a template, a Terror form template, etcetera, that deploys a script and then shuttle credentials back to the developers over email or over slack and then they plug them into their manifest to deploy on through getups, pipelines. That there's a lot of interesting things that are happening and what we we want to do is to prevent the human error. To put the guard rails in place is essentially arrive at a consistent approach for all of it. Your legacy workloads, your multi cloud workloads, your hybrid workloads, your the little system that's sitting on the side. You can, you can do, you can essentially normalize on using a single approach to manage all of it. One that is safe, that you can give to developers directly there. It has all the guardrails in place, has policy and controls factored in and is exposed through an api that's the part that I think is uh, you know, leads to the largest, most scalable platforms in the world. >>You know, I think that's just natural evolution to us as your customers and enterprises get visibility on the operational standards like, Okay, let's lock that input. The guard rails down. Makes a lot of sense. I gotta ask you on the enterprise adoption pieces, something that we've been covering on silicon angle on the cube this year is looking at the mainstream adoption of kubernetes and whatnot and the rest of the cloud native. It's certainly with Covid, it's accelerated everything. How is the enterprise adoption of cross plane changing? Uh is a game that kind of momentum you expected when you started the project a few years ago? >>Um We're very pleasantly surprised by the adoption, especially in the last six months since we declared cross plane one point. Oh, it has reached a maturity level now that it's actually in Fortune 100 massive production deployments in Fortune 100 companies. Um This is why we're actually, you know, taking to the next level of C N C F, we're also proud of the ecosystem convergence on it, so we're seeing the cloud providers, working with all of them on ensuring that Crossman can address their infrastructure and we're seeing main, the community rally around us. Uh We think the ecosystem part is super interesting for cross money, as you can imagine having an orchestrator control plane that's able to, you know, address the entire surface area of infrastructure offered by all these different vendors requires the vendors to be involved. Right? Uh and so both, uh, it's a two sided network. Both the ecosystem, you know, adoption and the end user adoption are important for cross plane and we're seeing like massive traction on both right >>now. That's awesome. Traditionally, the the adoption arises that users want more things actually enterprise. They they want everything every nook and cranny, they want every feature, they want every integration. I mean they prioritize but, but as you get more, it's not just like a consumer product, although it is cloud native and you've got that, but there's, there's certain things that are table stakes and then there's innovation, but they really want the well known integrations, um, and support and so forth. How is cross playing in the community responding to the challenges as you guys get more popular and as the standards become clear around multi cloud? >>Yeah, I mean, this is the beauty of open source. I mean, we're seeing a lot of different folks contributing to open source. The majority of contributors right now to cross plane are outside of a pound. The company that started cross plane and essentially donated C N C. F. We're seeing folks that are coming in and adding the resources that they are needing, um, or adding features, really significant features to the code base and improving, which is, you know, again, it's the network effect around open source and it's just unbelievable to see and, and I'm able to see it happen and happen so quickly around the project. >>That's awesome. Well something great to have you on, your always great to talk to your super smart, we've had many great conversations in person on camera on the cube. Now, remote CNC F is again um doing such a great job with the um, the open source and now with Coop Con and cloud, Native Con, the open hybrid cloud and now cross cloud, multi cloud, whatever you wanna call it, it's happening. So I gotta ask you with respect to kubernetes because you know, we were all having beers and open stack that time we write, cooper is going to be hot, I think how many years ago that was, um I think you are kind of hanging around with me and robert and others. Um, Kubernetes was just an idea it was developing. Now it's obviously mainstream. The question that I get a lot now is how do I manage and deploy kubernetes in an open hybrid cloud to take advantage of the current state of the art, Open software and commercial opportunities and be positioned to take advantage of multi cloud. In other words, they want the future of multi cloud, but they've got to address the open hybrid cloud. So how do I do that? What's your what's your advice? >>You know, honestly, uh reflecting on the success of kubernetes, I I have a you know, maybe a controversial answer to your question. >>I think >>Kubernetes will be remembered for its control plane and its ability to manage infrastructure and applications in a general way, and not for the fact that it's a container orchestrator In 10 years, we'll probably look at kubernetes and say it's true superpower is the fact that it revolutionized how we manage infrastructure and applications using this declarative approach, using this control plane approach uh to management. And the fact that it's managing the fact that it started out with just containers is well, we'll probably be a historical thing. Uh so so so in some ways, you know, to kind of to kind of go back to your question, I'd say yes. I think kubernetes is reached mainstream in the in the container space, but we now have two uncontained, arise it and use it for management, managing infrastructure everywhere in a multi cloud and a you know, in a hybrid environment as well. >>Well, I mean that's a great point. First, I don't think that's radical. I'm on the record years ago saying that I saw it as the TCP I P moment for cloud where you have interoperability and what you're getting and I think that's so interesting right now and I think everyone is kind of, it's the hidden secrets kind of like the land grab, everyone's trying to go for us. Customers just want a provision and manage cloud infrastructure and program it with applications. I mean just think about that general basic concept. Right? I want to provision, I don't want to have to have meetings, no waterfall know that. I want to be agile. Yeah, I want operation, I want security, I want all that big 10. That's kind of where the puck is going >>very much. Self, self service is a really critical part and the part that um is part of the kubernetes uh kind of design is you developers just want a database or they wanna cash to run their application alongside their application. They don't really need to understand all the security details and networking and be pcs and everything else. And so if you give them an A. P. I just like kubernetes does that tells them. Okay, look, if you want a pot or if you want a database or if you want to cash, here's the A. P. I use, use whatever framework you want, use any language you want. And then we've got all the guardrails built in behind the A. P. I line, just, you know, through getups or not deploy this thing, provision it and then the control plane takes care of the rest. That's the, that's the path we're on as an industry, >>whatever you wanna call it, getups, cross cloud, it's unlimited cloud resource at scale. That's what customers want to do. The markets evolving superfast tons of opportunity for entrepreneurs, tons of evidence for enterprises who are themselves innovating. Again, another big theme here. I'll give you the final word around this user generated open source paradigm, what they've always been involvement now, more than ever, you start to see that, I don't know, maybe second generation, maybe third generation end user inside companies contributing to projects and driving this. This is an interesting dynamic. No one's really reporting this, your thoughts on this end user driven projects. >>We're seeing, we're seeing a lot of end users get involved in projects like cross plane. I mean, it's amazing. It's like companies that are, you know, directionally, they're all, you know, when they're modernizing, they're all heading down about that's open source or even towards cloud native projects. Right. And so it's what we see is they typically get involved initially by just asking questions and, you know, reporting issues and asking for features. And then within within a few months you see actual like meaningful contributions come in two projects. Right. And so I mean there's nothing speaks uh, nothing, nothing says their work. You know, they're committed more than just submitting a pull request where they've spent hours weeks making changes to a project. Right. And and that's happening across the entire, you know, ecosystem around cloud Native. It's, it's what makes it so powerful, >>awesome. But some great to have this conversation. Great insights. Thanks for sharing the update on cross plane and your vision around this, you know, provisioning new infrastructure, having this control, universal control plan. I think this is where everyone is talking about having that value and the scale sets up automation. You know, it just brings everything to the next, next gen, next level of capability. So I appreciate taking the time. Thanks for coming in. >>Thanks john Yeah, good. Good to be back on the, on the cube. >>Great to see you. Okay. This is the Cube coverage of coop con 21 virtual cloud native Khanum jaan for your host with the cube. Thanks for watching. Mhm.

>>from around the globe. >>It's the cube with coverage of Kublai khan and cloud Native >>Con, Europe 2021 Virtual >>brought to you by >>red hat, cloud >>Native Computing foundation >>and ecosystem partners. >>Welcome back to the cubes coverage of coupon 21 cloud native con 21 part of the C N C s annual event this year. It's Virtual. Again, I'm john Kerry host of the cube and we have two great guests from the C N C. F. Cheryl Hung VP of ecosystems and Katie Manji who's the ecosystem advocate for C N C F. Thanks for coming on. Great to see you. I wish we were in person soon, maybe in the fall. Cheryl Katie, thanks for coming on. >>Um, definitely hoping to be back in person again soon, but john great to see you and great to be back on the >>cube. You know, I have to say one of the things that really surprised me is the resilience of the community around what's been happening with the virtual in the covid. Actually, a lot of people have been, um, you know, disrupted by this, but you know, the consensus is that developers have used to been working remotely and virtually in a home and so not too much disruption, but a hell of a lot of productivity. You're seeing a lot more cloud native, um, projects, you're seeing a lot more mainstreaming and the enterprise, you're starting to see cloud growth, just a really kind of nice growth. And we've been saying for years, rising tide floats, all boats, Cheryl, but this year you're starting to see real mainstream adoption with cloud native and this has really been part of the work of the community you guys have done. So what's your take on this? Because we're going to be coming out of this Covid pretty soon. There's a post covid light at the end of the tunnel. What's your view? >>Yeah, definitely, fingers crossed on that. I mean, I would love Katie to give her view on this. In fact, because she came from Conde Nast and American Express, both huge companies that were adopting have adopted cloud Native successfully. And then in the middle of the pandemic, in the middle of Covid, she joined CN CF. So Katie really has a view from the trenches and Katie would love to hear your thoughts. >>Yeah, absolutely. Uh, definitely cloud native adoption when it comes to the tooling has been more permanent in the enterprises. And that has been confirmed of my role at American Express. That is the role I moved from towards C N C F. But the more surprising thing is that we see big companies, we see banks and financial organization that are looking to adopt open source. But more importantly, they're looking for ways to either contribute or actually to direct it more into these areas. So from that perspective, I've been pretty much at the nucleus of enterprise of the adoption of cloud Native is definitely moving, it's slow paced, but it's definitely forward moving as well. Um and now I think while I'm in the role with C N C F as an ecosystem advocate and leading the end user community, there has been definitely uh the community is growing um always intrigued to find out more about the cloud Native usage is one of the things that I find quite intriguing is the fact that not one cloud native usage, like usage of covering just one platform, which is going to be called, the face is going to be the same. So it's always intriguing to find new use cases, find those extremist cases as well, that it really pushes the community forward. >>I want to do is unpack. The end user aspect of this has been a hallmark of the CNC F for years, always been a staple of the organization. But this year, more than ever it's been, seems to be prominent as people are integrating in what about the growth? I mean from last year this year and the use and user ecosystem, how have you guys seen the growth? Is there any highlights because have any stats and or observations around how the ecosystem is growing around the end user piece? >>Sure, absolutely. I mean, I can talk directly about C N C F and the C N C F. End user community, much like everything else, you know, covid kind of slowed things down, so we're kind of not entirely surprised by that, But we're still going over 2020 and in fact just in the last few months have brought in some really, really big names like Peloton, Airbnb, Citibank, um, just some incredible organizations who are, who have really adopted card native, who have seen the success and the benefits of it. And now we're looking to give back to the community, as Katie said, get involved with open source and be more than just a passive consumer of the technologies, but actually become leaders in their own right, >>Katie talk about the dynamic of developers that end user organizations. I mean, you have been there, you're now you've been on both sides of the table if you will not to the sides of the table, it's more like a round table if you will, but community driven. But traditional, uh, end user organizations, not the early adopters, not the hyper scale is, but the ones now are really embedding hybrid, um, are changing how I t to how modern applications being built. That's a big theme in these mainstream organizations. What's the dynamic going on? What's your view? >>I think for any organization, the kind of the core, what moves the organization towards cloud Native is um pretty much being ahead of your competitors. And now we have this mass of different organization of the cloud native and that's why we see more kind of ice towards this area. So um definitely in this perspective when it comes to the technology aspect, companies are looking to deploy complex application in an easier manner, especially when it comes to pushing them to production system securely faster. Um and continuously as well. They're looking to have this competitive edge when it comes to how can they quickly respond to customer feedback? And as well they're looking for this um hybrid element that has been, has been talked about. Again, we're talking about enterprise is not just about public cloud, it's about how can we run the application security and getting both an element of data centers or private cloud as well. And now we see a lot of projects which are balancing around that age but more importantly there is adoption and where there's adoption, there is a feedback loop and that's how which represents the organic growth. >>That's awesome. Cheryl like you to define what you mean when you say end user driven open source, what does that mean? >>Mm This is a really interesting dynamic that I've seen over the last couple of years. So what we see is that more and more of the open source project, our end users who who are solving their own problems and creating their own projects and donating these back to the community. An early example of this was Envoy and lift and Yeager from Uber but Spotify also recently donated backstage, which is a developer portal which has really taken off. We've also got examples from Intuit Donating Argo. Um I'm sure there are some others that I've just forgotten. But the really interesting thing I see about this is that class classically right. Maybe a few years ago, if you were an end user organization, you get involved through a vendor, you'd go to a red hat or something and say, hey, you fix this on my behalf because you know that's what I'm paying you to do. Whereas what I see now is and user saying we want to keep this expertise in house and we want to be owners of our own kind of direction and our own fate when it comes to these open source projects. And that's been a big driver for this trend of open source and user driven, open source. >>It's really the open model is just such a great thing. And I think one of the interesting thing is that fits in with a lot of people who want to work from mission driven companies, but here there's actually a business benefit as you pointed out as in terms of the dynamic of bringing stuff to the community. This is interesting. I'm sure that the ability to do more collaboration, um, either hiring or contributing kind of increases when you have this end user dynamic because that's a pretty big decision to donate and bring something into the open source. What's the playbook though? If I'm sitting in an end user organization like american express Katie or a big company, say, hey, you know, we really developed this really killer use cases niche to us, but we want to bring it to the community. What do they do? Is there like a, like a manager? Do they knock on someone's door? Zara repo is, I mean, how does someone, I mean, how does an end user get this done? >>Mm. Um, I think one of the best resources out there is called the to do group, which is a organization underneath the Linux foundation. So it's kind of a sister group to C N C F, which is about open source program offices. And how do you formalize such an open source program? Because it's pretty easy to say, oh well just put something on get hub. But that's not the end of the story, right? Um, if you want to actually build a community, if you want other people to contribute, then you do actually have to do more than just drop it and get up and walk away. So I would say that if you are an end user company and you have created something which scratches your own itch and you think other people could benefit from it then definitely come. And like you could email me, you could email Chris and chick who is the ceo of C N C F and just get in touch and sort of ask around about what are the things that you could do in terms of what you have to think about the licensing, How do you develop a community governance program, um, trademark issues, all of these things. >>It's interesting how open source is growing so much now, chris has got so much action going on. New verticals are opening up, you know, so, so much action Cheryl you had posted on the internet predictions for cloud native, which I found interesting because there's so much action going on, you have to break things out into pillars, tech devops and ecosystem, each one kind of with a slew event of key trends. So take us through the mindset, why break it out like that? You got tech devops and ecosystem tradition that was all kind of bundled in one. Why? Why the pillars? And is it because there's so much action, what's, what's the basis behind the prediction? >>Um so originally this was just a giant list of things I had seen from talking to people and reading around and seeing what people are talking about on social media. Um And when, once I invested at these 10, I thought about what, what does this actually mean for the people who are going to look at this list and what should they care about? So I see tech trends as things related to tools, frameworks. Um, perhaps architects I see develops as people who are more as a combination of process, things that a combination of process and people and culture best practices and then ecosystem was kind of anything else broader than that. Things that happened across organizations. So you can definitely go to my twitter, you can go to at boy Chevelle, O I C H E R Y L and take a look at this and This is my list of 10. I would love to hear from you whether you agree with it, whether you think there are other things that I've missed or what would your >>table. I love. I love the top. Well, first of all I think this is very relevant. The one that I would ask you on is more rust and cloud native. That's the number one item. Um, I think cross cloud is definitely totally happening, I think people are really starting to think about that and so I'd love to get your comments on that. But I think the thing that jumped out at me was the devops piece because this is a trend that I've been seeing a lot more certainly even in academic institutions, for folks in school, right? Um going to college for computer science and engineering. This idea of, sorry, large scale, cloud is not so much an IT practice, it's much more of a cloud native mindset. So I think this idea of of ops so much more about scale. I use SRE only because I can't think of a better word around it and certainly the edge pieces with kubernetes, I think this is the, I think the biggest story to me that's where all the action seems to be when I talk to people around what they're working on in terms of training new people on boarding and what not Katie, you're shaking your head, you're like Yeah, what's your thoughts? Yeah, >>I have definitely been uh through all of these stages from having a team where the develops, I think it's more of a culture of like a pattern to adopt within an organization more than anything. So I've been pre develops within develops and actually during the evolution of it where we actually added an s every team as well. Um I think having these cultural changes with an organization, they are necessary, especially they want to iterate iterate quicker and actually deliver value to the customers with minimal agency because what it actually does there is the collaboration between teams which were initially segregated. And that's why I think there is a paradigm nowadays which is called deficit ops, which actually moves security more to its left. This has been very popular, especially in the, in the latest a couple of months. Lots of talks around it and even there is like a security co located event of Yukon just going to focus on that mainly. Um, but as well within the Devil's area, um, one of the models that has been quite permanent has been get ups as well, which pretty much uses the power of gIT repositories to describe the state of the applications, how it actually should be within the production system and within the cloud native ecosystem. There are two main tools that pretty much leave this area and there's going to be Argo City which has been donated by, into it, which is our end user And we have flux as well, which has been donated by we've works and both of these projects currently are within the incubation stage, which pretty much by default um showcases there is a lot of adoption from the organizations um more than 100 of for for some of them. So there is a wider adoption um, and everything I would like to mention is the get ups working group which has emerged I think between que con europe and north America last year and that again is more to define a manifest of how exactly get expert and should be adopted within organizations. So there is a lot of, I would say initiatives and this is further out they confirmed with the tooling that we have within the ecosystem. >>That's really awesome insight. I want to just, if you don't mind follow up on that, why is getups so important right now, Is it because the emphasis of security is that the emphasis of more scale, Is it just because it's pretty much kid was okay just because storing it over there, Is it because there's so much more inspections are going on around it? I mean code reviews have been going on for a long time. What's what's the big deal? Why is it so hot right now? In your opinion? >>I think there is definitely a couple of aspects that are quite important. You mentioned security, that's definitely one of them with the get ups battery. And there is a pool model rather than a push model. So you have the actual tool, for example, our great city of flux watching for repository and if any changes are identified is going to pull those changes automatically. So the first thing that we actually can see from this model is that we always will have a delta between what's within our depositors and the production system. Usually if you have a pool model, you can pull it uh can push the changes towards death staging environment but not always the production because you have the change window sometimes with the get ups model, you'll always be aware of what's the Dell. Can you have quite a nice way to visualize that especially for your city, which has the UI as well as well with the get ups pattern, there is less necessity to share the credentials with the actual pipeline tool. All of because Argo flux there are natively build around communities, all the secrets are going to be residing within the cluster. There is no need to share any extra credentials or an extra permissions with external tools as well. There are scale, there is again with kids who have historical data points which allows us to easily revert um to stable points of the applications in the past. So multiple, multiple benefits I would say, but definitely secured. I think it's one of the main one and it has been talked about quite a lot as well. >>A lot of these end user stories revolve around these dynamics and the ones you guys are promoting and from your members as well as in the community at large is I hate to use the word day two operations, but that really is the issue like okay, we're up and running. I want more automation. This is again tops kind of vibe here where it's like okay we gotta go troubleshoot all this, but it should be working as more stuff comes in. This becomes more and more the dynamic is that is that because of just more edges, more things, more devices, what's what's the what's the push behind all these stories around this automation and day to operation things? What do you guys think? >>I think, I think the expectations are getting higher and higher to be honest, a few years ago it was enough to use containers and start using the barest minimum, you know, to orchestrate those containers. But now what we see is that, you know, it's easy to choose the technology, it's easy to install it and even configure it. But as you said, john those data operations are really, really hard. For example, one of the ones that we've seen up and coming and we care about from CNCF is kubernetes on the edge. And we see this as enabling telco use cases and 5G and IOT and really, really broad, difficult use cases that just a few years ago would have been nice on impossible, Katie, your zone, Katie Katie, you also talk about edge. Right? >>Absolutely. I think I I really like to watch some of the talks that keep going, especially given by the big organizations that have to manage thousands or tens of thousands, hundreds of thousands of customers. And they have to deliver a cluster to these to these teams. Now, from their point of view, they pretty much have to manage clusters at scale. There is definitely the edge out there and they really kind of pushing the technology towards how can we get closer to the physical devices within the customers? Kind of uh, let's say bubble or area in surface. So age has been definitely something which has been moving a lot when it comes to the cloud native ecosystem. We've had a lot of projects moving to towards the incubation stage, carefree as has been there, um, for for a while and again, has a lot of adoption is known for its stability. But another thing that I would like to mention is that now currently we have a lot of projects that are age focus but within some box, so there is again, a lot of potential if there's gonna be a higher demand for this, I would expect this tools move from sandbox to incubation and even graduation. So that's definitely something which, uh, it's moving and there is dynamism around it. >>Well, Cheryl kid, you guys are awesome, love the work you're doing. I gotta ask the final question since you brought it up about the expectations. Cheryl, if you guys could both end the segment with the comment around expectations as the industry and companies and developers and participants continue to grow. What, what's changed with C N C F koo Kahne cloud, native khan as the expectation has been growing and the stakes are higher too, frankly, I mean you've got security, you mentioned these things edge get up, so you start to see the maturation of this ecosystem, what's new and what's expected of you guys, What do you see and how are you guys organizing? >>I think we can definitely say the ecosystem has matured a lot compared to a few years ago. Same with CNTF, same with Cuba con, I think the very first cubic on I went to was Berlin, which was about 1800 people. Um, the kind of mind boggling to see how much, how much it's grown since then. I mean one of the things that we try and do is to expand the number of people who can reach the community. So for example, we launched kubernetes community days and we launched, that means community organized events in africa, for example, for people who couldn't come to large events in north America or europe, um we also launching things to help students. I actually love talking to students because quite often now you talk to them and they say, oh, I've never run software in anything other than a container. You're like, yeah, well this was a new thing, this is brand new a few years ago and now you can be 18 and have never tried anything else. So it's pretty amazing. But yeah, there's definitely, there's always space to go to the community. >>Yeah, once you go cloud native, it's like, you know, like you've never load Lennox on them server before. I mean, what, what's going on? Get your thoughts as expectations go higher And certainly there's more in migration, not only for young folks because they're jumping into this was that engineering meets computer science is now cross discipline. You're seeing scale, you mentioned scaling up those are huge factors, you've got younger, you got cross training, you got cybersecurity and you've got Fin tech ops that's chris is working on so much is happening. What, what, what you guys keep up with your, how you gonna raise the ball? >>Absolutely. I think there's definitely technology moving forward, but I think nowadays there is a more need for actual end user stories while at the beginning of cube cons there is a lot of focus on the technical aspects. How can you fix this particular problem of deploying between two clusters are deploying at scale. There is like a lot of technical aspects nowadays they're looking for the stories because as I mentioned before, not one platform is gonna be the same when it comes to cloud native and I think there's still, the community is still trying to look for some patterns or some standards and we actually can see like especially when it comes to the open standards, we can see this moving within um the observe abilities like that application delivery will have for example cross plane and Que Bella we have open metrics and open tracing as well, which focuses on observe ability and all of the interfaces that we had around um, Cuban directory service men and so forth. All of these pretty much try to bring a benchmark, making it easier to integrate these special use cases um when it comes to actual extreme technology kind of solutions that you need to provide and um, I was mentioning the end user stories that are there more in demand nowadays mainly because these are very, very necessary from the community like for example the six or the project maintainers, they require feedback to actually move forward. And as part of that, I would like to mention that we've recently soft launched the injuries lounge, which really focuses on this particular aspect of end user stories. We try to pretty much question our end users and really understand what really moved them to adopt, coordinative, what keeps them on this path and what like future challenges they would like to um to tackle or are they facing the moment I would like to solve in the future. So we're trying to create the speed back home between the inducers and the projects out there. So I think this is something which needs to be a bit more closely together these two spheres, which currently are segregated, but we're trying to just solve that. >>Also you guys do great work, great job. Cheryl wrap us up real, take a minute to put a plug in for the C. N. C. F. In the ecosystem. What's the fashion this year? What's hot? What's the trend? What are you guys doing? Share some quick update on what's going on the ecosystem from your perspective? >>Yeah, I mean the ecosystem, even though I just said that we're maturing, you know, the growth has not stopped now, what we're seeing is these as Casey was saying, you know, more specific use cases, even bigger, even more demanding environments, even more kind of crazy use cases. I mean I love the story from the U. S. Department of Defense about putting kubernetes on their fighter jets and putting ston fighter jets, you know, it's just absurd to think about it, but I would say definitely come and be part of the community, share your stories, share what you know, help other people um if you are end user of these technologies then go to see NCF dot io slash and user and just come and be part of our community, you know, meet your peers and hear what everybody else is doing >>well. Having kubernetes and stu on jets, that's the Air Force, I would call that technical edge Katie to you know, bring, bring back the edge carol kitty, thank you so much for sharing the inside ecosystem is robust. Rising tide is floating all the boats as we always say here in the cube, it's been great to watch and continue to watch the rise. I think it's just the beginning, we're starting to see post pandemic visibility cloud native, more standards, more visibility into the economics and value and great to see the ecosystem rising up with the end users as well. So congratulations and thanks for coming up. >>Thank you so much, john it's a pleasure, appreciate >>it. Thank you for having us, john >>Great to have you on. I'm john for with the cube here for Coop Con Cloud, Native Con 21 virtual soon we'll be back in real life. Thanks for watching. Mhm.

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America. 2020. Virtual Brought to You by Red Hat, The Cloud, Native Computing Foundation and Ecosystem Partners Welcome back to the Cube. Virtual coverage of KUB Con Cloud native 2020. It's virtual this year. We're not face to face. Were normally in person where we have great interviews. Everyone's kind of jamming in the hallways, having a good time talking tech, identifying the new projects and knew where So we're not. There were remote. I'm John for your host. We've got two great gas, both Cuba alumni's Chris. And is it chief technology officer of the C and C F Chris, Welcome back. Great to see you. Thanks for coming on. Appreciate it. >>Awesome. Glad to be here. >>And, of course, another Cube alumni who is in studio. But we haven't had him at a Show Jr store meant executive director of the Fin Ops Foundation. And that's the purpose of this session. A interesting data point we're going to dig into how cloud has been enabling Mawr communities, more networks of practitioners who are still working together, and it's also a success point Chris on the C N C F vision, which has been playing out beautifully. So we're looking forward to digging. Jr. Thanks for coming on. Great to see you. >>Yeah, great to be here. Thanks, John. >>So, first of all, I want to get the facts out there. I think this is really important story that people should pay attention to the Finn Ops Foundation. That J. R. That you're running is really an interesting success point because it's it's not the c n c f. Okay. It's a practitioner that builds on cloud. Your experience in community you had is doing specific things that they're I won't say narrow but specific toe a certain fintech things. But it's really about the success of Cloud. Can you explain and and layout for take a minute to explain What is the fin Ops foundation and has it relate to see NCF? >>Yeah, definitely. So you know, if you think about this, the shift that we've had to companies deploying primarily in cloud, whether it be containers a ciencia focuses on or traditional infrastructure. The thing that typically people focus on right is the technology and innovation and speed to market in all those areas. But invariably companies hit this. We'd like to call the spend panic moment where they realize they're They're initially spending much more than they expected. But more importantly, they don't really have the processes in place or the people or the tools to do things like fully, you know, understand where their costs are going to look at how to optimize those to operate that in their organizations. And so the foundation pinups foundation eyes really focused on, uh, the people in practitioners who are in organizations doing cloud financial management, which is, you know, being those who drive this accountability of this variable spin model that's existed. So we were partnering very closely with, uh, see NCF. And we're now actually part of the Linux Foundation as of a few months ago, Uh, and you know, just to kind of put into context how that you kind of Iraq together, whereas, you know, CNC s very focused on open source coordinative projects, you know, For example, Spotify just launched their backstage cloud called Management Tool into CFCF Spotify folks, in our end, are working on the best practices around the cloud financial management that standards to go along with that. So we're there to help, you know, define this sort of cultural transformation, which is a shift to now. Engineers happen to think about costs as they never did before. On finance, people happen to partner with technology teams at the speed of cloud, and, you know executives happen to make trade off decisions and really change the way that they operate the business. With this variable page ago, engineers have all the access to spend the money in Cloud Model. >>Hey, blank check for engineers who doesn't like that rain that in its like shift left for security. And now you've got to deal with the financial Finn ops. It's really important. It's super point, Chris. In all seriousness. Putting kidding aside, this is exactly the kind of thing you see with open sores. You're seeing things like shift left, where you wanna have security baked in. You know what Jr is done in a fabulous job with his community now part of Linux Foundation scaling up, there's important things to nail down that is specific to that domain that are related to cloud. What's your thoughts on this? Because you're seeing it play out. >>Yeah, no, I mean, you know, I talked to a lot of our end user members and companies that have been adopting Cloud Native and I have lots of friends that run, you know, cloud infrastructure at companies. And Justus Jr said, You know, eventually there's been a lot of success and cognitive and want to start using a lot of things. Your bills are a little bit more higher than you expect. You actually have trouble figuring out, you know, kind of who's using what because, you know, let's be honest. A lot of the clouds have built amazing services. But let's say the financial management and cost management accounting tools charge back is not really built in well. And so I kind of noticed this this issue where it's like, great everyone's using all these services. Everything is great, But costs are a little bit confusing, hard to manage and, you know, you know, scientifically, you know, I ran into, you know, Jr and his community out there because my community was having a need of like, you know, there's just not good tools, standards, no practices out there. And, you know, the Finau Foundation was working on these kind of great things. So we started definitely found a way to kind of work together and be under the same umbrella foundation, you know, under the under Linux Foundation. In my personal opinion, I see more and more standards and tools to be created in this space. You know, there's, you know, very few specifications or standards and trying to get cost, you know, data out of different clouds and tools out there, I predict, Ah, lot more work is going to be done. Um, in this space, whether it's done and defendants foundation itself, CNC f, I think will probably be, uh, collaboration amongst communities. Can I truly figure this out? So, uh, engineers have any easier understanding of, you know, if I spent up the service or experiment? How much is this actually going to potentially impact the cost of things and and for a while, You know, uh, engineers just don't think about this. When I was at Twitter, we spot up services all time without really care about cost on, and that's happening a lot of small companies now, which don't necessarily have as a big bucket. So I'm excited about the space. I think you're gonna see a huge amount of focus on cloud financial management drops in the near future. >>Chris, thanks for that great insight. I think you've got a great perspective. You know, in some cases, it's a fast and loose environment. Like Twitter. You mentioned you've got kind of a blank check and the rocket ships going. But, Jr, this brings up to kind of points. This kind of like the whole code side of it. The software piece where people are building code, but also this the human error. I mean, we were playing with clubs, so we have a big media cloud and Amazon and we left there. One of the buckets open on the switches and elemental. We're getting charged. Massive amounts for us cash were like, Wait a minute, not even using this thing. We used it once, and it left it open. It was like the water was flowing through the pipes and charging us. So you know, this human error is throwing the wrong switch. I mean, it was simply one configuration error, in some cases, just more about planning and thinking about prototypes. >>Yeah. I mean, so take what your experience there. Waas and multiply by 1000 development teams in a big organization who all have access to cloud. And then, you know, it's it's and this isn't really about a set of new technologies. It's about a new set of processes and a cultural change, as Chris mentioned, you know, engineers now thinking about cost and this being a whole new efficiency metric for them to manage, right? You know, finance teams now see this world where it's like tomorrow. The cost could go three x the next day they could go down. You've got, you know, things spending up by the second. So there's a whole set of cross functional, and that's the majority of the work that are members do is really around. How do we get these cross functional teams working together? How do we get you know, each team up leveled on what they need, understand with cloud? Because not only is it, you know, highly variable, but it's highly decentralized now, and we're seeing, you know, cloud hit. These sort of material spend levels where you know, the big, big cloud spenders out there spending, you know, high nine figures in some cases you know, in cloud and it's this material for their for their businesses. >>And let's just let's be honest. Here is like Clouds, for the most part, don't really have a huge incentive in offering limits and so on. It's just, you know, like, hey, the more usage that the better And hopefully getting a group of practitioners in real figures. Well, holy put pressure to build better tools and services in this area. I think actually it is happening. I think Jared could correct me if wrong. I think AWS recently announced a feature where I think it's finally like quotas, you know, enabled, you know, you have introducing quotas now for and building limits at some level, which, you know, I think it's 2020 Thank you know, >>just to push back a little bit in support of our friends, you ask Google this company, you know, for a long time doing this work, we were worried that the cloud would be like, What are you doing? Are you trying to get our trying to minimize commitments and you know the dirty secret of this type of work? And I were just talking a bunch of practitioners today is that cloud spend never really goes down. When you do this work, you actually end up spending more because you know you're more comfortable with the efficiency that you're getting, and your CEO is like, let's move more workloads over. But let's accelerate. Let's let's do Maurin Cloud goes out more data centers. And so the cloud providers air actually largely incentivized to say, Yeah, we want people to be officially don't understand this And so it's been a great collaboration with those companies. As you said, you know, aws, Google, that you're certainly really focused in this area and ship more features and more data for you. It's >>really about getting smart. I mean, you know, they no, >>you could >>do it. I mean, remember the old browser days you could switch the default search engine through 10 menus. You could certainly find the way if you really wanted to dig in and make policy a simple abstraction layer feature, which is really a no brainer thing. So I think getting smarter is the right message. I want to get into the synergy Chris, between this this trend, because I think this points to, um kind of what actually happened here if you look at it at least from my perspective and correct me if I'm wrong. But you had jr had a community of practitioners who was sharing information. Sounds like open source. They're talking and sharing, you know? Hey, don't throw that switch. Do This is the best practice. Um, that's what open communities do. But now you're getting into software. You have to embed cost management into everything, just like security I mentioned earlier. So this trend, I think if you kind of connect the dots is gonna happen in other areas on this is really the synergy. Um, I getting that right with CNC >>f eso The way I see it is, and I dream of a future where developers, as they develop software, will be able to have some insight almost immediately off how much potential, you know, cost or impact. They'll have, you know, on maybe a new service or spinning up or potentially earlier in the development cycle saying, Hey, maybe you're not doing this in a way that is efficient. Maybe you something else. Just having that feedback loop. Ah lot. You know, closer to Deb time than you know a couple weeks out. Something crazy happens all of a sudden you notice, You know, based on you know, your phase or financial folks reaching out to you saying, Hey, what's going on here? This is a little bit insane. So I think what we'll see is, as you know, practitioners and you know, Jr spinoffs, foundation community, you know, get together share practices. A lot of them, you know, just as we saw on sense. Yeah, kind of build their own tools, models, abstractions. And, you know, they're starting to share these things. And once you start sharing these things, you end up with a you know, a dozen tools. Eventually, you know, sharing, you know, knowledge sharing, code sharing, you know, specifications. Sharing happens Eventually, things kind of, you know, become de facto tools and standards. And I think we'll see that, you know, transition in the thin ops community over the next 12 to 4 months. You know, very soon in my thing. I think that's kind of where I see things going, >>Jr. This really kind of also puts a riel, you know, spotlight and illustrates the whole developer. First cliche. I mean, it's really not a cliche. It's It's happening. Developers first, when you start getting into the calculations of our oi, which is the number one C level question is Hey, what's the are aware of this problem Project or I won't say cover your ass. But I mean, if someone kind of does a project that it breaks the bank or causes a, you know, financial problem, you know, someone gets pulled out to the back would shed. So, you know, here you're you're balancing both ends of the spectrum, you know, risk management on one side, and you've got return on investment on the other. Is that coming out from the conversation where you guys just in the early stages, I could almost imagine that this is a beautiful tailwind for you? These thes trends, >>Yeah. I mean, if you think about the work that we're doing in our practice you're doing, it's not about saving money. It's about making money because you actually want empower those engineers to be the innovation engines in the organization to deliver faster to ship faster. At the same time, they now can have, you know, tangible financial roo impacts on the business. So it's a new up leveling skill for them. But then it's also, I think, to Christmas point of, you know, people seeing this stuff more quickly. You know what the model looks like when it's really great is that engineers get near real time visibility into the impact of their change is on the business, and they can start to have conversations with the business or with their finance partners about Okay, you know, if you want me to move fast, I could move fast, But it's gonna cost this if you want me to optimize the cost. I could do that or I can optimize performance. And there's actually, you know, deeper are like conversation the candidate up. >>Now I know a lot of people who watch the Cube always share with me privately and Chris, you got great vision on this. We talked many times about it. We're learning a lot, and the developers are on the front lines and, you know, a lot of them don't have MBAs and, you know they're not in the business, but they can learn quick. If you can code, you can learn business. So, you know, I want you to take a minute Jr and share some, um, educational knowledge to developers were out there who have to sit in these meetings and have to say, Hey, I got to justify this project. Buy versus build. I need to learn all that in business school when I had to see s degree and got my MBA, so I kind of blended it together. But could you share what the community is doing and saying, How does that engineer sit in the meeting and defend or justify, or you some of the best practices what's coming out of the foundation? >>Yeah, I mean, and we're looking at first what a core principles that the whole organization used to line around. And then for each persona, like engineers, what they need to know. So I mean, first and foremost, it's It's about collaboration, you know, with their partners andan starting to get to that world where you're thinking about your use of cloud from a business value driver, right? Like, what is the impact of this? The critical part of that? Those early decentralization where you know, now you've got everybody basically taking ownership for their cloud usage. So for engineers, it's yes, we get that information in front of us quickly. But now we have a new efficiency metric. And engineers don't like inefficiency, right? They want to write fishing code. They wanna have efficient outcomes. Um, at the same time, those engineers need to now, you know, have ah, we call it, call it a common lexicon. Or for Hitchhiker's Guide to the Galaxy, folks. Ah, Babel fish that needs to be developed between these teams. So a lot of the conversations with engineers right now is in the foundation is okay. What What financial terms do I need to understand? To have meaningful conversations about Op X and Capex? And what I'm going to make a commitment to a cloud provider like a committed use discount, Google or reserved instance or savings Planet AWS. You know, Is it okay for me to make that? What? How does that impact our, you know, cost of capital. And then and then once I make that, how do I ensure that I could work with those teams to get that allocated and accounted? The right area is not just for charge back purposes, but also so that my teams can see my portion of the estate, right? And they were having the flip side of that conversation with all the finance folks of like, You need to understand how the variable cloud, you know, model works. And you need to understand what these things mean and how they impact the business. And then all that's coming together. And to the point of like, how we're working with C and C f you know, into best practices White papers, you know, training Siri's etcetera, sets of KP eyes and capabilities. Onda. All these problems have been around for years, and I wouldn't say they're solved. But the knowledge is out there were pulling it together. The new level that we're trying to talk with the NCF is okay. In the old world of Cloud, you had 1 to 1 use of a resource. You're running a thing on an instance in the new world, you're running in containers and that, you know, cluster may have lots of pods and name spaces, things inside of it that may be doing lots of different workloads, and you can no longer allocate. I've got this easy to instance and this storage to this thing it's now split up and very ephemeral. And it is a whole new layer of virtualization on top of virtual ization that we didn't have to deal with before. >>And you've got multiple cloud. I'll throw that in there, just make another dimension on it. Chris, tie this together cause this is nice energy to scale up what he's built with the community now, part of the Linux Foundation. This fits nicely into your vision, you know, perfectly. >>Yeah, no, 100% like, you know, so little foundation. You know, as you're well, well aware, is just a federation of open source foundations of groups working together to share knowledge. So it definitely fits in kind of the little foundation mission of, you know, building the largest share technology investment for, you know, humankind. So definitely good there with my kind of C and C f c T o hat, you know, on is, you know, I want to make sure that you know, you know my community and and, you know, the community of cloud native has access and, you know, knowledge about modern. You know, cloud financial management practices out there. If you look at some of the new and upcoming projects in ciencia things like, you know, you know, backstage, which came out of Spotify. They're starting to add functionality that, you know, you know, originally backstage kind of started out as this, you know, everyone builds their own service catalog to go catalog, and you know who owns what and, you know and all that goodness and developers used it. And eventually what happened is they started to add cost, you know, metrics to each of these services and so on. So it surfaces things a little bit closer, you know, a depth time. So my whole goal is to, you know, take some of these great, you know, practices and potential tools that were being built by this wonderful spinoffs community and trying to bring it into the project. You know, front inside of CNC F. So having more projects either exposed, you know, useful. You know, Finn, ops related metrics or, you know, be able to, you know, uh, you know, tool themselves to quickly be able to get useful metrics that could be used by thin ox practitioners out there. That's my kind of goal. And, you know, I just love seeing two communities, uh, come together to improve, improve the state of the world. >>It's just a great vision, and it's needed so and again. It's not about saving money. Certainly does that if you play it right, but it's about growth and people. You need better instrumentation. You need better data. You've got cloud scale. Why not do something there, right? >>Absolutely. It's just maturity after the day because, you know, a lot of engineers, you know, they just love this whole like, you know, rental model just uses many Resource is they want, you know, without even thinking about just basic, you know, metrics in terms of, you know, how many idle instances do I have out there and so, like, people just don't think about that. They think about getting the work done, getting the job done. And if they anything we do to kind of make them think a little bit earlier about costs and impact efficiency, charge back, you know, I think the better the world isn't Honestly, you know, I do see this to me. It's It's almost like, you know, with my hippie hat on. It's like Stephen Green or for the more efficient we are. You know, the better the world off cloud is coming. Can you grow? But we need to be more efficient and careful about the resource is that we use in sentencing >>and certainly with the pandemic, people are virtually you wanted mental health, too. I mean, if people gonna be pulling their hair out, worrying about dollars and cents at scale, I mean, people are gonna be freaking out and you're in meetings justifying why you did things. I mean, that's a time waster, right? I mean, you know, talking about wasting time. >>I have a lot of friends who, you know, run infrastructure at companies. And there's a lot of you know, some companies have been, you know, blessed during this, you know, crazy time with usage. But there is a kind of laser focused on understanding costs and so on and you not be. Do not believe how difficult it is sometimes even just to get, you know, reporting out of these systems, especially if you're using, you know, multiple clouds and multiple services across them. It's not. It's non trivial. And, you know, Jared could speak to this, But, you know, a lot of this world runs in like terrible spreadsheets, right and in versus kind of, you know, nice automated tools with potential, a p I. So there's a lot of this stuff. It's just done sadly in spreadsheets. >>Yeah, salute the flag toe. One standard to rally around us. We see this all the time Jr and emerging inflection points. No de facto kind of things develop. Kubernetes took that track. That was great. What's your take on what he just said? I mean, this is a critical path item for people from all around. >>Yeah, and it's It's really like becoming this bigger and bigger data problem is well, because if you look at the way the clouds are building, they're building per seconds and and down to the very fine grain detail, you know, or functions and and service. And that's amazing for being able to have accountability. But also you get people with at the end of the month of 300 gigabyte billing files, with hundreds of millions of rows and columns attached. So, you know, that's where we do see you companies come together. So yeah, it is a spreadsheet problem, but you can now no longer open your bill in a spreadsheet because it's too big. Eso you know, there's the native tools are doing a lot of work, you know, as you mentioned, you know, AWS and Azure Google shipping a lot. There's there's great, you know, management platforms out there. They're doing work in this area, you know, there's there's people trying to build their own open source the things like Chris was talking about as well. But really, at the end of the day like this, this is This is not a technology. Changes is sort of a cultural shift internally, and it's It's a lot like the like, you know, move from data center to cloud or like waterfall to Dev ops. It's It's a shift in how we're managing, you know, the finances of the money in the business and bringing these groups together. So it it takes time and it takes involvement. I'm also amazed I look like the job titles of the people who are plugged into the Phenoms Foundation and they range from like principal engineers to tech procurement. Thio you know, product leaders to C. T. O. S. And these people are now coming together in the classic to get a seat at the table right toe, Have these conversations and talk about not How do we reduce, you know, cost in the old eighties world. But how do we work together to be more quickly to innovate, to take advantage of these cognitive technologies so that we could be more competitive? Especially now >>it's automation. I mean, all these things are at play. It's about software. I mean, software defined operations is clearly the trend we've been covering. You guys been riding the wave cloud Native actually is so important in all these modern APS, and it applies to almost every aspect of stacks, so makes total sense. Great vision. Um, Chris props to you for that, Jr. Congratulations on a great community, Jerry. I'll give you the final word. Put a plug in for the folks watching on the fin ops Foundation where you're at. What are you looking to do? You adding people, What's your objectives? Take a minute to give the plug? >>Yeah, definitely. We were in open source community, which means we thrive on people contributing inputs. You know, we've got now almost 3000 practitioner members, which is up from 1500 just this this summer on You know, we're looking for those who have either an interesting need to plug into are checked advisory council to help define standards as part of this event, The cognitive gone we're launching Ah, white paper on kubernetes. Uh, and how to do confidential management for it, which was a collaborative effort of a few dozen of our practitioners, as well as our vendor members from VM Ware and Google and APP Thio and a bunch of others who have come together to basically defined how to do this. Well, and, you know, we're looking for folks to plug into that, you know, because at the end of the day, this is about everybody sort of up leveling their skills and knowledge and, you know, the knowledge is out there, nobody's head, and we're focused on how toe drive. Ah, you know, a central collection of that be the central community for it. You enable the people doing this work to get better their jobs and, you know, contribute more of their companies. So I invite you to join us. You know, if your practitioner ITT's Frito, get in there and plug into all the bits and there's great slack interaction channels where people are talking about kubernetes or pinups kubernetes or I need to be asked Google or where we want to go. So I hope you consider joining in the community and join the conversation. >>Thanks for doing that, Chris. Good vision. Thanks for being part of the segment. And, as always, C N C F. This is an enablement model. You throw out the soil, but the 1000 flowers bloom. You don't know what's going to come out of it. You know, new standards, new communities, new vendors, new companies, some entrepreneur Mike jump in this thing and say, Hey, I'm gonna build a better tool. >>Love it. >>You never know. Right? So thanks so much for you guys for coming in. Thanks for the insight. Appreciate. >>Thanks so much, John. >>Thank you for having us. >>Okay. I'm John Furry, the host of the Cube covering Coop Con Cloud, Native Con 2020 with virtual This year, we wish we could be there face to face, but it's cute. Virtual. Thanks for watching

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America 2020 Virtual brought to you by Red Hat The Cloud Native Computing Foundation and Ecosystem >>Partners Everyone welcome back to the cubes. Coverage of Coop con Cloud, native con North America 2020. Normally the Cuba's in person. But like the EU event, this is gonna be a remote virtual event. This is the Cube virtual. We are the Cube Virtual. This is a keynote and show review with our analysts and hosts Lisa Martin, GOP Scar and myself. Guys, welcome to the program. Lisa, Great to see you. You great to see you remotely. Thanks for coming on. >>Always great to be part of the Cuban acute virtual keeping us connected. >>So Coop Con Cloud Native cons November and I remember in 2016 the first Coop Con. That's when Hillary Clinton got defeated by Trump. And now this year the election's passed this time and, uh, Biden the winner. So, you know, election more good vibes this year in the community because everyone was kind of sad last time. So if you remember the first Cube con, it was in Seattle during that time, so that was important to kinda reminisce on. That other thing I want to bring up to you guys is the somber news of the passing of Dan Con who was the executive director of C N C F. He passed a few weeks ago on his home. It was illness and great legend. So we're gonna call that out, and there are thoughts and prayers. Go with the families. Condolences to his wife and kids. So what? I'm say, Dan. Godspeed. Funny dance story, Lisa. Yo, piece that I always always pronounce his name wrong on the queue was like, John, it's con, not Cohen. Okay. All right, Dan, Good to see you. Sorry, but a great guy friend to everyone And super great human being. So rest in peace. Okay. Que con, I >>think the big thing. >>This you wanna get your thoughts, you have to start with you, C and C F. What are they up to? Obviously remote. It's been a terrible year with the pandemic and all the disruptions on DCI change your thoughts on where they are now, this year. >>So you know, it's funny, even though it's remote. Even though reaching people, it's become harder. Uh, you know, we all have to deal with this from our you know, our living room, our office at home. But still, the C in C F is doing what it's been doing for a little while now. So instead of focusing on the technology part of RT world, there are focusing on you know, the community side of it. So they're fighting for inclusivity. They're fighting for diversity, for resilience in terms off their community. And they are really working on making the open source community more accessible, both for end user companies. A swell as offer developers thio enter the space, have their contribution and, you know, make sure that everyone can reap the full benefits off these open source products. >>You know, we talked to Priyanka Sharma and Stephen Augustus, and this was a big theme. There's there's been there's been a lot of engagement online, obviously, even though they have a remote platform, some people are thrilled with it. Some aren't. No one's ever happy these days. It's on the Web. It's always difficult, but the community been activated and a lot more diversity. I covered the big story around. You know, Master slave. The terminology now is gonna go main, you know, terminology and how that's gonna be safer. Also for diversity stem women in tech, This >>has been >>a big theme. I'd love to get your thoughts on that, because I think that's been a very positive thing. Uh, Lisa, you and I have been talking about this for years on the Cube around this diversity peace. What's your thoughts as well, like to get both your reactions on where this directions going. >>Yeah. You know, I think there's a number of things that have been catalyzed this year by the challenges that we've been through and the diversity pushed into the spotlight again. The spotlight is different, and it's really causing change for good. I think it's opening people's minds and perspective, as is, I think, this entire time, you know, it's for events like Yukon and all the other events that were normally getting a lot of airline miles for John and you were not getting. We're sitting at home with our in home studios, but at the same time, the engagement is increasing in every event, I imagine that the great Q. Khan and cognitive community that Dan Cohen has built is on Lee getting bigger and stronger, even though folks are physically separated. That's been just been my observation and something I felt from everything show I've covered every interview I've done that diversity is being raised now to a visibility level that we haven't seen in terms of a catalyzing action. >>You your reaction, Thio. >>No, I completely agree. And I want to add to that where you know, just like Lisa said. You know, we used to fly to these events. We were privileged and lucky to to be there to have the opportunity. But because everything is now digital and virtual, it opens the community up to so many other people who, for whatever reason, weren't able to join in person but are able to join virtually indigenously. So I think you know, even though there's a lot of downsides Thio to this pandemic, this is one of the, you know, the small nuggets of off seeing the sea NCF community opening up to a broader audience. >>Yeah, and that's a great point. You know, we aren't getting the airline miles we're getting Certainly the zoom and the cube mileage remote Lisa, because what's interesting you're saying is is that you know, we're getting more action with him coming in, doing some or hosting yourself, um, Eliana Gesu as well, Others. But we can get people more because remember, the people aren't we're not trying, but so aren't other people that were coming the big names, but also the fresh voices, the new names, names? We don't know yet. I think that's what we're seeing with the remote interviews is that it's one click away from being on the Cube now. So cute. Virtual is 24 73 65 we're gonna continue to do that. I think this is gonna change the makeup of the engagement in the conversation because you're gonna have mawr participation that's going to be highly accelerated. But also, these new voices are gonna bring a positive change. It might upset the hierarchy a little bit in the working groups at the top you, But you know they're open. I mean, I talked with Stephen Augustus. He's totally cool with this Chris, and I check is the same way he's like, Hey, bring on more people. This is the >>This is >>the vibe of the of the Lennox foundations always been. >>It's always been that way. And, you know, going back Teoh to the early open source events in Europe that I went to you. I started doing that as a teenager 15 years ago, and the vibe, you know, hasn't necessarily changed. The makeup of the audience certainly has changed right from it, being dominated by white males. It's totally opened up. And, you know, if we see that happening with the C N C F now as well, I think that's for you know, for the better. I think, um, our community, the i t community in the open source community need that resilience. Need all of those different perspectives from all of you know, different kinds of people from different walks of life with different histories. And I think that only makes the community stronger and more viable in the long run. I >>agree it's that >>open source needs. >>Sorry, it's not thought diversity that I think we're seeing even more now again. Just my perspective is just that the light that this challenging time is shining on, exposing things that are really opportunities and it's I think it's imperative to look at it in that way. But that thought diversity just opens up so many more opportunities that folks that are maybe a little bit more tunnel visioned aren't thinking of. But for businesses, thio and people Thio thrive and move forward and learn from this we need to be able Thio, take into consideration other concepts, other perspectives as we learn and grow. >>Yeah, that's a good point. You know, It was giving a a shout out to Dan Conn. And when I heard the news, I put a clip. One of my favorite clips over the interviews was really me kind of congratulating him on the success of C and C. I think it was, like two years ago or maybe last year. I forget, Um, but I >>was a >>critic of it ever initially, and I was publicly on the record on the Cube. Lisa, you remember, uh, with Stew, who's now having a great new career? Red hat Still and I were arguing, and I was saying, Stew, I think this is gonna fail, because if c. N. C F doesn't balance the end user peace with the logos that we're coming because remember, you about four years ago. It was like a NASCAR logo. Farmers like you know, it's like, you know, everything was like sponsored by Google this and then Amazon came in. You look at the sponsor list. It was like It's the who's who and cloud and now cloud native. It was the industry the entire industry was like, stacked up against reinvent. This is before Amazon made their move. I mean, uh, as your maid, they're moving for Google. Cloud kind of got their footing. So is essentially coop con against a W s. And I said, That's gonna fail, and I had to eat my words, and I did. It was rightfully so, But the balance, the balance between end user projects and vendor was very successful. And that's still plays out today. Lisa. This is important now because you said pandemic de ecosystem still needs to thrive, but there's no face to face anymore. >>What's the >>challenge? What's the opportunity there? I wanna put you on the spot. >>Sure. No, I think I think it's both challenging and opportunistic. I tend to look at it more from an opportunistic view. I think that it forced a lot of us, Even people like myself who worked from home a lot before, when I wasn't traveling for my marketing company or the Cube. You can really have very personal interactions. The people on Zoom and I found that it's connecting people in a deeper way than you even would get in the office. That's something that I actually really appreciate, how it has been an opportunity to really kind of expand relationships or toe open new doors that wouldn't be there if we were able to be studying together physically in person. And it's obviously changing. You know, all the vendors that we work with. It's very different to engage an audience when you are on Lee on camera, and it's something that, as we know, is we work with folks who haven't done it before. That's one of the things that I think a lot of the C suite I talked to Mrs is that opportunity Thio. You know, be on a stage and and be able to show your body language and your energy with your customers and your partners and your employees. But I actually do think that there is what we're doing through Zoom and and all these virtual platforms like the Cube virtual is well, we're opening up doors for a more intimate way that I think the conversations are more authentic. You know, people are have, like, three year old Discover occurs and they're running in the room when they're screaming behind that. That's how things are today. We're learning toe work with that, but we're also seeing people in a more human >>way. Containers Mitch, mainstream and shifting, left the role of security this year. What's your >>take? So I mean, if we're talking about security and nothing else, I think we're at a point where you know, the C N C. F has become mainstream. Its most popular products have become mainstream. Um, because if we're talking about security, there's, you know, not a lot left. And I say that with, you know, a little bit of sarcasm. I don't mean to offend anyone, but if I did, uh, I do apologize, but, you know, security. Even though it is super important again, it means that we have, you know, moved on from talking about kubernetes and and container Management, or we've moved on from storage. Um, it means that the technology part of the C N. C. F. Like the hard work has been done for 80%. We're now into the 20% where we're kind of, you know, dotting the I's and and making sure that we cover all of the bases. And so one of the news sandbox sandbox projects that has been accepted, I think, today even eyes certain Manager Thio to manage certificates Uh, you know, at scale, um, in an automated fashion. And I think that's, you know, 11 prime example of how security is becoming the theme and kind of the conversation at Yukon this year where, you know, we're again seeing that maturity come into play with even with sandbox projects now being able to help customers help end users with, you know, certificates which is, you know, in in the the macro picture a very specific, a very niche thing to be able to solve with open source software. But for every company, this is one of those vital, you know, kind of boilerplate security measures so that the, um the customer and all of their infrastructure remains safe. >>I think you what You're kind of really articulate, and there is the evolution of CNC off much to John Surprises. You said you thought in the very beginning that this wasn't gonna take off. It has. Clearly, Dan Cohen's left a great legacy there. But we're seeing the evolution of that. I do know John. Wanna ask because you did a lot of the interviews here. We've been talking for, what, nine months now on the Cube Virtual about the acceleration of transformation, of every business to go from that. Okay, how do we do this work in this in this weird environment? Keep the lights on. How do we actually be successful and actually become a thriving business? As things go forward, what are some of the things that you heard from the guests regarding? Kobe has an accelerator. >>Well, I think I think a couple of things. Good. Good question. I think it ranges. Right. So the new They had some news that they're trying to announce. Obviously, new survey certifications, K a security certification, new new tech radar support, diversity stats. You know, the normal stuff they do in the event, they gotta get the word out. So that was one thing I heard, but on the overall macro trend. You know, we saw the covert impact, and no >>one's >>afraid of it there. I mean, I think, you know, part of the legacy of these tech communities is they've been online. They're they're used to being online. So it's not a new thing. So I don't think that the work environment has been that much of a disruption to the people in the in the core community. Linux Foundation, for instance, had a great shot with Chris and a sticker on this. He's the CTO. He's been the CEO, brought a senior roles. Um, in fact, they're they're creating a template around C N C f. And then they're announced The Finn Finn Ops Foundation. Uh, Jr store meant, um, is an executive director. That's part of the new foundation. It's a practitioner community. So I think, um, teasing out the conversation is you're gonna see a template model of the C N. C f. Where you're going to see how groups work together. I think what cove? It has definitely shown in some of the things that you guys were saying around how people are gonna be more engaged, more diversity, more access. I >>think you're >>gonna start to see new social constructs emerge around distinct user groups. And I think this Finn ops Foundation is a tell sign around how groups of people going to start together, whether they're cube host coming together on Cube fans and cube alumni. I mean, let me think about the alumni that have been on the Cube. Lisa, you know Tim Hopkins, Sarah Novotny. Chelsie Hightower. Um, Dan Burns, Craig MK Lucky. I mean, we've had everybody on that's now Captain of the industry. So, um, way had capital one we've had, uh, you know, lift on. I mean, it's becoming a really tight knit. Everyone knows each other, and I think now they realize that they have a lot of, uh, power to infect change. And so when you're trying to affect change, um, that's a good thing, and people are pumped about. So I think the big focus was, um, CNC have a successful again. It's there's there's a somber note around Dan cons passing, but I think he had already moved on to a new position. So he was already passed the baton to management, But he did leave a mark, but I think there's Priyanka Sharma. She's doing a great job. People are upbeat and I think the theme is kubernetes. It happened. It's went next level, then it's going next level again and I think that's kind of what people really aren't saying is kind of the public secret, which is okay, this thing's going mainstream. Now you're gonna start to see it in, in, In commercial deployments. You're gonna start to see it scale into organizations. And that's not the cool kids or the Emerging Dev ops crowd. That's I t. So you know you know it's gonna happen is like, Hey, you know, I'm a nice guy, our developer. What is this? It has toe work. Well, that's the big I think I think people weren't talking about That's the most important story. >>I think another element to that John is the cultural shift. You know, we were talking when we talk about Dev ops who was think about speed and I talked to some folks who said, You know, it's it has to be the I T. Cultures on the business cultures coming together in a meaningful way to collaborate in a very new way. Thankfully, we have the technology to enable us to collaborate. But I think that's been another underlying thing that I've heard a lot through recent times. Is that that facilitator of of cultural change, which is always hard to dio? And there's a bit of a catalyst here for organizations to not just keep the lights on. But to be successful, going forward and and and find new ways of delighting their customers, >>we'll get the final word. I just want to say my big take away to the show is and we'll go down the line. I'll start Lisa in Europe, you could go is the usage of cloud and multi cloud is here. Everyone sees that. I think there's a financial aspect going on with security. You're gonna be tied in. I think you see new sets of services coming built on the foundation of the C N C F. But cloud and multi cloud is here. Multi cloud meeting edges. Well, that is definitely on everyone's radar. That was a big theme throughout the interview, so we'll see more of that. Lisa, your takeaways. >>Yeah, I would agree with that. And I think one of the biggest things that I hear consistently is the opportunities that have been uncovered, the the collaboration becoming tighter and folks having the opportunity to engage more with events like Coop Con and C and C F. Because of this virtual shift, I think there's only ah lot of positive things that we're going to stay to come. >>Yep. Yeah, my point of view is I mean, open source is validated completely right? It's a viable model to build around software. On the one hand, on the other hand, the C and C s role in making that open source community broadly accessible and inclusive is, I think, the biggest win Thio look back at at the last year. >>Well, I'm super excited for moving on to the next event. It's been great pleasure. Lisa. You you guys are great co host Virtual Cube. Thanks for participating. And we'll see you next time. Thank you. Okay, that's the cubes. Coverage of Coop con 2020 cloud Native con Virtual This the cube Virtual. We are the cube. Virtual. Thanks for watching

>>live from San Diego, California It's the Q covering Koopa and Cloud Native Cot brought to you by Red Cloud. Native Computing Pounding and its ecosystem >>Welcome back. This is the cubes. Fourth year of coverage at Q. Khan Cloud, Native Con. We're here in San Diego. It's 2019. I'm stewed. Minutemen, my host for this afternoon is Justin Warren and happy to welcome to guests from the newly minted platinum member of the CNC F Net Up. Sitting to my right is that Baldwin, who is the director of Cloud Native and Communities Engineering and sitting to his right is Rob Bhaskar, who's the product product strategy for Kubernetes. And it's also a board member on the CME CF, thank you both for joining us. Thank you. All right, s O, you know, maybe start with you. You know, uh, you know, companies that No, I've got plenty of history with net up there. What I've been hearing from that up last few years is you know, the Corvette has always been software, and it is a multi cloud world. I've been hearing this message before. Kind of the cloud native Trinity's piece was going, Of course, there's been some acquisitions and met up continuing to go through its transformations if you will s o help us understand kind of net ops positioning in this ecosystem >>in communities. Yes. Okay, so what we're doing is we're building a product that large manage cloud native workloads on top of community. So we've solved the infrastructure problem. And that's kind of the old problem. We're bored to death. Talking about that problem, but we try to do is try to provide a single painting class to manage on premise. Workloads and off permits were close. So that's what we're trying to do. We're trying to say it's now more about the AP taxonomy in communities. And then what type of tooling do you build to manage that that application and communities and says what we're building right now? That's where we're headed with hybrid. >>There's a piece of it, though, that does draw from the historical strength of map, Of course. So we're building way have, essentially already in marketing capability that allows you to deploy communities an agnostic way, using pure, open unmodified kubernetes on all of the major public clouds, but also on trump. But over time and some of this is already evident. You'll see it married to the storage and data management capabilities that we draw from the historical NetApp and that we're starting to deploy into those public clouds >>with the idea that you should be able to take a project. So project being the name space, new space, having a certain application in it. So you have multiple deployments. I should be able to protect that name space or that project. I feel to move that and the data goes with it. So they were very data where that's what we're trying to do with our. Our software is, you know, make it very data. Where have that aligned with APS inside of communities, >>So maybe step back for a second. What? One of the one of things we've heard a few times at this show before and was talking about the keynote this morning is it is project over company when it comes to the C N C F Project Project over company. So it's about the ecosystem. The C in C F tries not to be opinionated, so it's okay for multiple projects to fitness face not moving up to a platinum a sponsor level. You know, participant here, Ned. It's got lots of history's in participating and driving standards, helping move where the industry's going. Where doesn't it up? See its position in, you know, the participating in the foundation and participating in this ecosystem? >>Yeah, So great question, actually. Love it. It's for my favorite topic. So I think the way we look at it is oftentimes, project to the extent they become ubiquitous, define a standard a de facto standard, so not necessarily ratified by some standards body. And so we're very interested in making sure that in a scenario where you would employ the standard from a technology integration perspective, our capabilities can can operate as an implementation behind the standard. So you get the distinguishing qualities of our capabilities. Our products in our service is Visa VI or in the context of the standard. We're not trying to take you down a walled garden path in a proprietary, uh, journey, if you will weigh, would rather actually compel you to work with us on the basis of the value, not necessarily operating off a proprietary set of interface. Kubernetes broadly perceive it as a defacto standard at this point, there's still some work to be done on running out the edges a lot of underway this week. It's definitely the case that there's a new appeal to making this more off herbal by pardon the expression mere mortals way. Think we can offer Cem, Cem, Cem help in that respect as well? >>Yeah, for us, its usability, right? I mean, that's the reason I started stacking. Cloud was that there was usability problem with kubernetes. I had a usability problem. That's what we're trying. That's how I'm looking at the landscape. And I look at kind of all the projects inside the C N c f. And I look at my role is our role is to How do we tie these together? How do we make these? So they're very, very usable to the users. How were engaging with the community is to try to like a line like this, basically pure upstream projects, and create a usability layer on top of that. But we're not gonna we don't want ever say we're gonna fork into these projects what we're gonna contribute back into these. >>That's one concern that I have heard from. Customers were speaking with some of them yesterday. One of the concerns I had was that when you add that manageability onto the base kubernetes layer, that often very spenders become rather opinionated about which way we think this is a good way to do that. And when you're trying to maintain that compatibility across the ecosystem. So some customers saying, Well, I actually don't want to have to be too closely welded to anyone. Vendor was part of the benefit of Kubernetes. I can move my workloads around. So how do you navigate What? What is the right level of opinion? Tohave and which part should actually just be part of a common sense >>should be along the lines of best practices is how we do it. So like, Let's take a number policy, for example, like applying a sane default network policy to every name space defying a saying default pod security policy. You know, building a cluster in the best practices fashion with security turned on hardening done where you would have done this already as a user. So we're not looking you in any way there, so that's we're not trying. I'm not trying to carry any type of opinion in the product we're trying to do is urbanize your experience across all of this ecosystem so that you don't ever have to think about time now building a cluster on top of Amazon. So I gotta worry about how do I manage this on Amazon? I don't want you to think about those providers anymore, right? And then on top of those on top of that infrastructure, I wanna have a way that you're thinking about managing the applications on those environments in the exact same way. So I'm scaling protecting an application on premise in the identical way I'm doing it in the cloud. >>So if it's the same everywhere, what's the value that you're providing? That means that I should choose your option than something else. >>So wait, do have This is where we have controllers and live inside of the clusters that manage this stuff for the user's so you could rebuild what we're doing, But you would have to roll it all by hands, but you could, you know, we don't stand in the way of your operations either. So, like if we go down, you don't go down that idea, but we do have controllers we have. We're using charities. And so, like our management technology, our controllers are just watching for workload to come into the environment. And then we show that in the interface. But you could just walk away as well if you wanted to. >>There's also a constellation of other service is that we're building around this experience, you know, they do draw again from some of the storage and management capabilities. So staple sets your traditional workloads that want to interact with or transact data against a block or a shared file system. We're providing capabilities for sophisticated qualities of persistence that can be can exist in all of those same public clouds. But moreover, over time, we're gonna be in on premises. Well, we're gonna be able to actually move migrate, place, cash her policy. Your put your persistent data with your workload as you move migrate scale burst would repatriate whatever the model is as you move across in between clouds. >>Okay, How how far down that pathway do you think we are? Because 11 criticism of proven it is is that a lot of the tooling that were used to from more traditional ways of operating this kind of infrastructure isn't really there yet. Hence into the question about we actually need to make this easy to use. How far down that pathway away? >>Why would argue that tooling that I've built has already solved some of those problems. So I think we're pretty far down. The people ride down the path. Now what we haven't done is open sourced. You know all my tools, right? To make it easier on everybody else. >>Get up, Scott. Strong partnerships across the cloud platforms. I had a chance to interview George at the Google Cloud event. New partner of the year. I believe some of the stuff help us understand how you know something about the team building. Interact with the public cloud. You look at anthems and azure Arkin. Of course, Amazon has many different ways. You can do your container and management piece there, you know, to talk a little bit of that relationship and how both with those partners and then across those partners, you know, work. >>Yeah, it's a wow. So how much time we have? So so there's certainly a lot of facets to to that, But drawing from the Google experience. We just announced the general availability of cloud volumes on top. So the ability to stand up and manage your own on top instance and Google's cloud. Likewise, we've announced the general availability of the cloud volume service, which gives you manage put fun as a service experience of shared file system on demand. Google, I believe, is either today or yesterday in London. I guess maybe I'll blame that on the time zone covers, not knowing what what day it was. But the point is that's now generally available. Some of those capabilities are going to be able to be connected to our ability from an ks to deploy, uh on demand kubernetes cluster and deploy applications from a market marketplace experience in a common way, not just with Google, but has your with Amazon. And so, you know, frankly, the story doesn't differ a little bit from one cloud to the next, but the the Endeavour is to provide common capabilities across all of them. It's also the case that we do have people that are very opinionated about I want to live only in the Google or that Microsoft of the Amazon, because we're trying to deliver a rich experience for those folks as well, even if you don't value the agnostic multi cloud expert. >>Yeah and Matt, You know, I'm sure you have a viewpoint on this, but you know, it's that skill set that that's really challenging. And I was at the Microsoft show and you've got people you know. It's not just about dot net, there's all that. They're they're embracing and opened all of these environment. But people tend to have the environment that you used to and for multi cloud to be a reality, it needs to be a little bit easier for me to go between them, but it's still we're still we're making progress. But there's work to do. Yeah, s so I just, you know, you know, I know you're building tools and everything, but what what more do we didn't need to do? What were some of the areas that you know you're hopeful for about a >>year before I need to go for the supreme? It's down. It's coming down to the data side like I need to be able to say that on when I turn on data service is inside of kubernetes. I need be able to have that work would go anywhere, right? And because it is a developer. So I have I'm running a production. I'm running an Amazon. But maybe I'm doing test locally on my bare metal environments. Right? I need I want to be able to maybe sink down some of my data. I'm working with a production down to my test environment. That stuff's missing. There's no one doing that right now, and that's where we're headed. That's the path that's where we're headed. >>Yeah. I'm glad you brought that up, actually, because one of the things that I feel like I heard a little bit last year, but it is violated more this year is we're talking a little bit more to the application to the application developer because, you know, communities is a piece of the infrastructure, But it's about the Colonel. Yeah, yeah, yeah. It's the colonel there. So, you know, how do we make sure you know, we're standing between what the APP developer needs and still making sure that, you know, infrastructure is taken care of because storage and networking they're still hard. >>It is. Yeah. Yeah. I mean, I'm I'm approaching. I'm thinking more along the lines of I'm trying to work about app developers personally than infrastructure This point on for me, you know, like so I have I give you a cluster in three minutes, right? So I don't really have to worry about that problem, you know, way also put Theo on top of the clusters. So it's like we're trying to create this whole narrative that you can manage that environment on day one day, two versions. But and that's for like, an I T manager, right? And society instead of our product. How I'm addressing this is you have personas and so you have this concept. You have an I T manager. They do these things that could set limits for the developer who's building the applications or the service's and pushing those up into the environment. They need to have a sense of freedom, right? And said on that side of the house, you know, I'm trying not to break them out of their tooling. So, like wait part of our product ties in to get s o. We have CD, you know? So you just get push, get commit to a branch and weaken target multiple clusters, Right? But no point to the developer, actually, drafty animal or anything. We make way basically create the container for you. Read the deployment, bring it online. And I feel like there's these lines and that I t guys need to be able to say I need to create the guard rails for the Debs. I don't want to make it seem like I'm creating guardrails for the deaths caused the deaths. Don't like that. That's how I'm balancing it. >>Okay, Because that has always been the tension and that there's a lot of talk about Dev ops, but you don't talkto application developers, and they don't wanna have anything to do with infrastructure. They just want a program to an A p I and get things done. They would like this infrastructure to be seamless. Yeah, >>and what we did, like also what I'm giving them is like service dashboards. Because as a developer, you know, because now you're in charge of your cue, eh? You're writing your tests you're pushing. If your c I is going to ct you on your service in production, right? And so we're delivering dashboards as well for service Is that the developers are running, so they dig in and say, Oh, here's an issue or here's where the issue is probably gonna be at I'm gonna go fix this. Yeah, and we're trying to create that type of like scenario for developer and for an I T manager, >>slightly different angle on it, by understanding that question correctly is part of the complexity of infrastructure is something we're also turned Friday deterministic sort of easy button capability, for perhaps you're familiar with them. That's nice. And a C I product, which we we kind of expand that as hybrid cloud infrastructure. If the intention is to make it a simple private cloud capability and indeed are not, a community service operates directly off of it. It's a big part of actually how we deliver Cloud Service is from it. The point is, is that if you're that application developer, if you want the effective and CASS on prom thing, Endeavor with are not a PhD. I product is to give you that sort of easy button extremes because you didn't really want to be a storage admin network at you didn't want to get into the be mired in the details of infra. So So you know, that's obviously work in progress. But we think we're definitely headed down the right direction >>for him. >>Yeah, it just seemed that a lot of enterprises wanna have the cloud like experience, but they want to be able to bring it home that we're seeing a lot more. Yeah. >>So this is like, this turn cheon from this turnkey cloud on premise and played with think has weaken like the same auto scaling. So take so take the dynamic nature of opportunities. Right. So I have a base cluster size of four worker notes, right? But my work, let's gonna maybe maybe need to have more notes. So my out of scale is gonna increase the size my cluster and decrease the size right Pretty much everybody only do that in the public cloud. I could do that in public and on premise now and so that's That's what we're trying to deliver. And that's nickel stuff. I think >>that there's a lot of advantages thio enterprises operating in that way because I have I people that here I can I can go and buy them, hire them and say way, need you to operate this gear and you, you've already done elsewhere. You can do it in cloud. You can do it on side. I could know run my operations the same across no matter where my applications leave, Which saves me a lot of money on training costs on development costs on generally makes for a much more smooth and seamless experience. So, Rob, if you could just love >>your takeaway on, you know, kind of net up participation here at the event and what you want people to take away off from the show this year. >>So it's certainly the case that we're doing a lot of great work. We, like people toe become aware of it. Not up, of course, is not. I think we talked about this and perhaps other context, not strictly a storage and data management company. Only way do draw from the strength of that as we're providing full stack capabilities in a way that are interconnected with public cloud things like are not a Cuban. Any service is really the foundational glue in many ways how we deliver the application run time, but over time will build a consolation of data centric capabilities around that as well. >>I would just love to get your viewpoint Is someone that you know built a company in this ecosystem. There's so many start ups here. Give us kind of that founder viewpoint of being in. They're so sort of ecosystem of the >>ecosystem. So this is how I came into the ecosystem at the beginning. I would have to say that it does feel different. Att This point, I'm gonna speak as Matt, not as now. And so my my thinking has always been It feels a lot like kind of your really your big fan of that rock bands, right? And you go to a local club way all get to know each other at that local club. There's, like maybe 500 of us or 1000 of us. And then that band gets signed a Warner Brothers and goes to the top it. Now there's 20,000 people or 12,000 people. That's how it feels to me right now, I think. But what I like about it is that just shows the power of the community is now at a point where is drawing in like cities now, not just a small collection of a tribe of people, right? And I think that's a very powerful thing with this community. And like all the where they called the kubernetes summits that they're doing way, didn't have any of those back when we first got going. I mean, it was tough to fill the room, you know, Now, now we can fill the room and it's amazing. And what I like seeing is is people moving past the problem with kubernetes itself and moving into, like, what other problems can I solve on top of kubernetes, you know? So you're starting to see that all these really exciting startups doing really need things, you know, and I really likes it like this vendor hall I really like, you know, because you get to see all the new guys. But there's a lot of stuff going on, and I'm excited to see where the community goes in the next five years. But it's we've gone from 0 to 60 insanely because you guys were at the original coupon. I think, Well, >>it's our fourth year doing the Cube at this show, but absolutely we've watched the early days, You know, I'm not supposed to mention open stack of this show, but we remember talking T o J j. And some of the early people there and wait interviewed Chris McCloskey back into Google days, right? So, yeah, we've been fortunate to be on here, really? Day zero here and definitely great energy. So much. Congrats. So much on the progress. Really appreciate the updates, Everything going. As you said, right, we've reached a certain estate and just adding more value on top of this whole >>environment. We're now like we're in, like, Junior high now. Right on were in grade school for a few years. >>All right, Matt. Rob, Thank you so much for the update. Hopefully not an awkward dance tonight for the junior people. For Justin Warren. I'm stupid and back with more coverage here from Q Khan Cloud native 2019. Diego, Thank you for watching Cute

>>Live from San Diego, California It's the Q Covering Koopa and Cloud Native Cot Brought to you by Red Cloud. Native Computing Pounding and its ecosystem >>Welcome back, toe Gorgeous. SAN Diego, California This is Q Khan Cloud Native Khan. 29 years. I'm still minimum. My co host is John Troyer, and this is the end of three days water wall coverage over 12,000 and 10 d Having a welcome to the program. Cassie, Who's the executive director at the national headquarters for v. American Red Cross. Matt. Thank you, American Red Cross. And thank you so much for joining us. >>Yeah. Thanks for having me. Uh, it's been a great conference so far. Uh, you know, we're here to share our story where as an end user on our journey with Cloud native with kubernetes Andi how that helps Red Cross do what we do, which is help people in need a cz best we can every day. >>Eso no matter what industry I talked to, everybody's dealing with change. There's always more things happening. American Red Cross. I mean, you know, it feels like I hear American Red Cross mentioned Maur a cz Time goes on because you know everything from, you know, things related to climate through, you know, global events and the like. So maybe before we get into some of the tech, just give us, you know, you know your role there and how kind of the changing world impact your organization. >>Sure. So my role is to support a few different business units. One is biomedical marketing. We try to recruit blood donors, too. Give blood at Red Cross Blood Dot or GE and other channels. That's obviously a significant part of what we d'oh were major player in the blood supply market in the US we provide service is to the armed forces, you know, in that regard as well. So that's part of it. Part of it is I work with humanitarian service is group as well to recruit financial donors on recruit volunteers. That's primarily through Red Cross. That or GE a T least as faras my group goes on, then corporate brand marketing and chapter related marketing and communications. So all that happens through Red Cross that Oregon Red Cross blood dot organ some related platforms on those our flagship brand products. >>Okay, And what led to the American Red Cross being part of this cloud. Native computing, Yeah, system. >>Our journey is a lot like, you know, a lot of other folks. We had a very, you know, monolithic type of architecture. We had all of these different business units with the different priorities, different timelines, different needs wrapped up into one big monster of a platform that, you know, kind of bundled up risk for everybody in this one platform. And, uh, you know, we'd always have collisions of priorities, mostly not to mention the resource issues of who's gonna work, you know, on what? At what time. And so a few years ago, we started talking about breaking that down. And, um, we've been lucky to have some technical leaders that are very aware of and welcoming to new cloud native technologies. We decided at that time to pursue, you know, a cloud native architecture. And what we have today in a few years later, is two years worth of being in production with a platform that runs on Amazon. We take advantage of a lot of the native orchestration tools there for running our clusters. And we've been able to service, you know, those different needs in a much more nimble way. We can release something for a Red Cross blood dot or without risking much on the financial donation side or on the volunteer recruitment side. And likewise, you know, for those other groups, we can kind of separate out the risks for each of those groups. And that's that's been a great, great benefit. >>You've been on the the vendor side. The for profit side is I t very different at the non profit. If you're looking, people are looking down, you get >>higher. Yeah, You know, I have been doing it a long time, a lot of different perspectives. But I think you know what I tried to do. And I would. I think I've seen work best is when I t is not the ticket taker, you know, integrated with the business. I'm very fortunate to have some business partners at Red Cross that collaborate. You know, every day we're having conversations every day. We have some people on our team that feel as though they're accountable for business outcomes, not just, you know, doing cool technology things, you know, For example, you know, multiyear evolution of process related to being more agile. We've got so much more integration and communication with business teams have gone from, you know, something like one release every five months now due to a weak, you know, and I think we could do more. It's just we don't have the need to do more. Um, and that's a huge, huge, big lift. You know, there's a lot of conversations that need to happen. Should make that work. >>Yeah, it's all a journey, right? We're all we're all improved. Continuous improvement, but so follow up there. So as a 90 leader for a very large organization, you know, they're one of the things people are saying this year. Wow. The conference is big. So many new technologies. So many new company somebody open source projects. You know, you're in the middle of this journey. You can't screw it up, right? That would be disastrous. So how do you How do you How did you and your organization look at new technologies and pick out which do technologies to try and incorporate them into your stack and your portfolio? >>Right. So we wanted to be a cloud native. We wanted a do, um, you know, focus on projects that where we knew there were skills in the marketplace, uh, that we could acquire at our price point. You know, we try to be good stewards of donor dollars at the end of the day, you know, all the money we have comes from folks like you and you guys who support Red Cross, you know, and thank you very much for all that generous support. And so we try to spend that money, uh, you know, very carefully. Way have some people who are, uh, you know, employees on our team made about 25 or so. But one of the great things we've been able to do with some of these technologies now is we have a program called Code for Good. It's a volunteer work force where we're here recruiting volunteers with the skill set that you know, they have a day job, but they have an interest in supporting Red Cross. Uh, maybe not financially. Maybe not with their blood, but they can give us some time on their skills, and we run it like an open source project. We set out a road map of features for six months or so. We have planning sessions, we say. Listen, you know if you can sign up for a feature that because you have two hours this week to work. Great. You have six hours. Great. You just had a baby, and you're not available for three months. Fine. You know, we we wanna have a, you know, a bench of people that can self select based on their time commitment, what to work on. And somehow it's been been working Great. You know, we started this in June. We have about 30 volunteers now on. We've already delivered an app for slack. That is kind of a workplace app where you can, you know, if your organization works with us, you can donate right from slack. You can give a schedule of blood donation, appointment, do things like that. >>I love that model. It's something that, you know we've looked at years ago. That kind of micro participation, if you will. You know, You think it's like, you know, Wikipedia wouldn't have been built if it wasn't for everybody. Just spending a little bit of time on it. Uh, I'm curious. Does something like participating with you know, this ecosystem I have generalized tools that people know and can plug in with, as opposed to, you know, having to know your direct stack Is that helpful To kind of be able to recruit people into that environment? What? What are the kind of most needed skills on dhe usages that you're recruiting? >>It is. You are learning. Curve at this point is much smaller than it was on our previous platform Because of the fact that we're using technologies people are familiar with, um, you know, things like Docker we use a lot. We just started evaluating Prometheus, another C N C F project for monitoring some non proud systems. Hopefully that'll graduate into production systems. So from a technology standpoint, yes, yes, we find that, you know, the people we talked with can walk in and be productive sooner. You know, there's still the Red Cross specific things they need to know about how we do business. But, um, you know, at least at this point, is that and not some proprietary system that they also have to learn >>any learnings that you've had participating in the c m. D. F. With the rollout of the technologies that you share with your peers, >>you know, I love the sea. NCF is very maintainer driven, You know, uh, and and user driven. I heard today at one of the analyst panels. I did. I think maybe 30% of people here are end users. >>That's a pretty >>large number. Um, you know, the fact that we can come here and learn about technologies meet people, meat vendors meet some of the people contributing code. Um, it's a lot different than you know, maybe some some summit sponsored by a for profit vendor that wants to, uh, you know, generate leads and sell you things. It feels much more community driven here and open to lots of different perspectives. >>So now what you looking forward to in the next few years? Both in terms of your stack and maybe coming back >>to Cuba? Yeah, way. It's funny. We've started to see other parts of Red Cross come to us toe, learn about kubernetes because the vendors they work with are mentioning these things. And and we have been early adopters, as far as you know, where across goes our group. Um and I think it's great if we can expand usage of, um, cloud native technologies to other parts of the organization on really get some economies of scale. So that's part of what we're trying to do is kind of internal, uh, consulting knowledge sharing collaboration on then, as far as what we're doing on our team way. Just really want to focus on. We're on a stable point in the platform, and then we want to do some things around monitoring and alerting that. Reduce those incident outages, too. Nothing. Hopefully, um, and work on that. >>You're working on a few projects that are that are being worked on here for That >>s So you have this Prometheus project. Like I said, we're piloting that, uh, you know, I would say in four or five months time, we'll know if that's going to be something we can, you know, put some more investment into >>All right, that want to give you the final word. Red cross dot org's code for good. I believe. The web. >>Yes, yes. >>What else? >>Your code for the number four. Good on. You know, if you're interested in volunteering, we need technical skills. We need team leadership skills, product owner skills, eh? So it's not just about you know, developing features and ops engineers as well. So thanks for your time. I want to say hi to my daughter, Peyton. It's late on the East Coast, so go to bed now, but thanks, folks. >>All right. What? Well, Matt, and actually, that is the final word for our day one of coverage for John Troyer. I'm stupid. And be sure to join us tomorrow. We've got two more days water wall coverage here. Lots of great speakers. Really appreciate. We've got the end users on. And, Matt, thank you so much. And, you know, great mission. The code for good. We definitely hope that the community here, you know, reaches out in connection Participates s Oh, that's it for today. Fixes all for watching.

>>live from Atlanta, Georgia. It's the Q covering answerable best 2019. Brought to you by Red hat. >>Welcome back, everyone to the Cube. Live coverage in Atlanta, Georgia for answerable fest. This is Red Hats Event where all the practices come together. The community to talk about automation anywhere. John Kerry with my coast to Minutemen, our next two guests arrive. And Bergeron, principal community architect for answerable now Red Hat and Greg Dankers Berg, senior director, Community Ansel's. Well, thanks for coming on. Appreciate it. >>Thank you. >>Okay, So we were talking before camera that you guys had. This is a two day event. We're covering the Cube. You guys have an awful fast, but you got your community day yesterday. The day before the people came in early. The core community heard great things about it. Love to get an update. Could you share just what happened yesterday? And then we'll get in some of the community. Sure. >>We s o uh, for all of our answer professed for a while now we've started them with ah, community contributor conference. And the goal of that conference is to get together. Ah, lot of the people we work with online right people we see is IRC nicks or get hub handles rights to get them together in the same room. Ah, have them interact with, uh, with core members of our team. Uh, and that's where we really do, uh, make a lot of decisions about how we're gonna be going forward, get really direct feedback from some of our key contributors about the decisions were making The things were thinking about, uh, with the goal of, you know, involving our community deeply in a lot of decisions we make, that's >>a working session, meets social, get together. That's >>right, Several working sessions and then, you know, drinks afterward for those who want the drinks and just hang out time that >>way. Drinks and their last night was really good. I got the end of it. I missed the session, but >>they have the peaches, peaches, it on the >>table. That was good. But this is the dynamic community. This is one things we notice here. Not a seat open in the house on the keynote Skinny Ramon Lee, active participant base from this organic as well Be now going mainstream. How >>you >>guys handling it, how you guys ride in this way? Because certainly you certainly do. The communities which is great for feedback get from the community. But as you have the commercial eyes open sores and answerable, it's a tough task. >>Well, I'd like to think part of it is, I guess maybe it's not our first rodeo. Is that what we'd say? I mean, yeah, uh, for Ansel. I worked at ELASTICSEARCH, uh, doing community stuff. Before that, I worked at Red Hat. It was a fedora. Project leader, number five. And you were Fedora project Leader. What number was that? Number one depends >>on how you count, but >>you're the You're the one that got us to be able to call it having a federal project leader. So I sort of was number one. So we've been dealing with this stuff for a really long time. It's different in Anselm that, you know, unlike a lot of, you know, holds old school things like fedora. You know, a lot of this stuff is newer and part of the reason it's really important for us to get You know, some of these folks here to talk to us in person is that you know especially. And you saw my keynote this morning where they talked about we talked about modularity. Lot of these folks are really just focused on. They're one little bit and they don't always have is much time. People are working in lots of open source projects now, right, and it's hard to pay deep attention to every single little thing all the time. So this gives them a day of in case you missed it. Here's the deep, dark dive into everything that you know we're planning or thinking about, and they really are. You know, people who are managing those smaller parts all around answerable, really are some of our best feedback loops, right? Because they're people who probably wrote that model because they're using it every single day and their hard core Ansel users. But they also understand how to participate in community so we can get those people actually talking with the rest of us who a lot of us used to be so sad. Men's. I used to be a sis admin, lots of us. You know. A lot of our employees actually just got into wanting to work on Ansel because they loved using it so much of their jobs. And when you're not, actually, since admitting every day, you you lose a little bit of >>the front lines with the truth of what's around. Truth is right there >>and putting all these people together in room make sure that they all also, you know, when you have to look at someone in the eye and tell them news that they might not like you have a different level of empathy and you approach it a little bit differently than you may on the Internet. So, >>Robin So I lived in your keynote this morning. You talked about answerable. First commit was only back in 2012. So that simplicity of that modularity and the learnings from where open source had been in the past Yes, they're a little bit, you know, what could answerable do, being a relatively young project that it might not have been able to dio if it had a couple of decades of history? >>Maybe Greg should tell the story about the funk project >>way. There was a There was a project, a tread hat that we started in 2007 in a coffee shop in Chapel Hill, North Carolina is Ah, myself and Michael the Han and Seth the doll on entry likens Who still works with this with us? A danceable Ah, and we we put together Ah, an idea with all the same underpinnings, right? Ah, highly modular automation tool We debated at the time whether it should be based on SSL or SS H for funk. We chose SSL Ah, and you know, after watching that grow to a certain point and then stagnates and it being inside of red Hat where, you know, there were a lot of other business pressures, things like that. We learned a lot from that experience and we were able to take that experience. And then in 2012 there there's the open source community was a little different. Open source was more acceptable. Get Hubbell was becoming a common plat platform for open source project hosting. And so a lot of things came together in a short pier Time All that experience, although, >>and also market conditions, agenda market conditions in 2007 Cloud was sort of a weird thing that not really everyone was doing 2012 rolls around. Everyone has these cloud images and they need to figure out how to get something in it. Um, and it turns out that Hansel's a really great way to actually do that. And, you know, even if we had picked SS H back in the beginning, I don't know, you know, not have had time projects grow to a certain point. And I could point a lots of projects that were just It's a shame they were so ahead of their time. And because of that, you know, >>timing is everything with the key. I think now what I've always admired about the simplicity is automation requires that the abstract, the way, the complexities and so I think you bring a cloud that brings up more complexity, more use cases for some of the underlying paintings of the plumbing. And this is always gonna This is a moving train that's never going to stop. What was the feedback from the community this year around? As you guys get into some of these analytical capabilities, so the new features have a platform flair to it. It's a platform you guys announced answerable automation platform that implies that enables some value. >>You know, I >>think in >>a way. We've always been a platform, right, because platform is a set of small rules and then modules that attached to it. It's about how that grows, right? And, uh, traditionally, we've had a batteries included model where every module and plug in was built to go into answerable Boy, that got really big bright and >>we like to hear it. I don't even know how many I keep say, I'll >>say 2000. Then it'll be 3000 say 3000 >>something else, a lot of content. And it's, you know, in the beginning, it was I can't imagine this ever being more than 202 150 batteries included, and at some point, you know, it's like, Whoa, yeah, taking care of this and making sure it all works together all the time gets >>You guys have done a great You guys have done a great job with community, and one of the things that you met with Cloud is as more use cases come, scale becomes a big question, and there's real business benefits now, so open source has become part of the business. People talk about business, models will open source. You guys know that you've been part of that 28 years of history with Lennox. But now you're seeing Dev Ops, which is you'll go back to 78 2009 10 time frame The only the purest we're talking Dev ops. At that time, Infrastructures Co was being kicked around. We certainly been covering the cubes is 2010 on that? But now, in mainstream enterprise, it seems like the commercialization and operational izing of Dev ops is here. You guys have a proof point in your own community. People talk about culture, about relationships. We have one guest on time, but they're now friends with the other guy group dowels. So you stay. The collaboration is now becoming a big part of it because of the playbook because of the of these these instances. So talk about that dynamic of operational izing the Dev Ops movement for Enterprise. >>All right, so I remember Ah, an example at one of the first answer professed I ever went thio There were there were a few before I came on board. Ah, but it was I >>think it was >>the 1st 1 I came to when I was about to make the jump from my previous company, and I was just There is a visitor and a friend of the team, and there was an adman who talked to me and said, For the first time, I have this thing, this playbook, that I can write and that I can hand to my manager and say this is what we're going to D'oh! Right? And so there was this artifact that allowed for a bridging between different parts of the organization. That was the simplicity of that playbook that was human readable, that he could show to his boss or to someone else in the organ that they could agree on. And suddenly there was this sort of a document that was a mechanism for collaboration that everyone could understand buy into that hadn't really existed before. Answerable existed after me. That was one of the many, you know, flip of the light moments where I was like, Oh, wow, maybe we have something >>really big. There were plenty of other infrastructures, code things that you could hand to someone. But, you know, for a lot of people, it's like I don't speak that language right? That's why we like to say like Ansel sort of this universal automation language, right? Like everybody can read it. You don't have to be a rocket scientist. Uh, it's, you know, great for your exact example, right? I'm showing this to my manager and saying This is the order of operations and you don't have to be a genius to read it because it's really, really readable >>connecting system which connects people >>right. It's fascinating to May is there was this whole wave of enterprise collaboration tools that the enterprise would try to push down and force people to collaborate. But here is a technology tool that from the ground up, is getting people to do that collaboration. And they want to do it. And it's helping bury some >>of those walls. And it's interesting you mention that I'm sure that something like slack is a thing that falls into that category. And they've built around making sure that the 20 billion people inside a company all sign up until somebody in the I T departments like, What do you mean? These random people are just everyone's using it. No one saving it isn't secure, and they all freak out, and, um, well, I mean, this is sort of, you know, everybody tells her friend about Ansel and they go, Oh, right, Tool. That's gonna save the world Number 22 0 wait, actually, yeah. No, this is This actually is pretty cool. Yeah, yeah, yeah, I get started. >>Well, you know, sometimes the better mouse trap will always drive people to that solution. You guys have proven that organic. What's interesting to me is not only does it keep win on capabilities, it actually grew organically. And this connective tissue between different groups, >>right? Got it >>breaks down that hole silo mentality. And that's really where I tease been stuck? Yes. And as software becomes more prominent and data becomes more prominent, it's gonna just shift more power in the hands of developer and to the, uh, just add mons who are now being redeployed into being systems, architects or whatever they are. This transitional human rolls with automation, >>transformation architect >>Oh my God, that's a real title. I don't >>have it, but >>double my pay. I'll take it. >>So collections is one of the key things talked about when we talk about the Antelope Automation platform. Been hearing a lot discussion about how the partner ecosystems really stepping up even more than before. You know, 4600 plus contributors out there in community, But the partners stepping up Where do you see this going? Where? Well, collections really catalyze the next growth for your >>It's got to be the future for us that, you know, there there were a >>few >>key problems that we recognize that the collections was ultimately the the dissolution that we chose. Uh, you know, one key problem is that with the batteries included model that put a lot of pressure on vendors to conform to whatever our processes were, they had to get their batteries in tow. Are thing to be a part of the ecosystem. And there was a huge demand to be a part of our ecosystem. The partners would just sort of, you know, swallow hard and do what they needed to d'oh. But it really wasn't optimized Tol partners, right? So they might have different development processes. They might have different release cycles. They might have different testing on the back end. That would be, you know, more difficult to hook together collections, breaks a lot of that out and gives our partners a lot of freedom to innovate in their own time. Uh, >>release on their own cycle, the down cycle. We just released our new version of software, but you can't actually get the new Ansel modules that are updated for it until answerable releases is not always the thing that you know makes their product immediately useful. You know, you're a vendor, you really something new. You want people to start using it right away, not wait until, you know answerable comes around so >>and that new artifact also creates more network effects with the, you know, galaxy and automation hub. And you know, the new deployment options that we're gonna have available for that stuff. So it's, I think it's just leveling up, right? It's taking the same approach that's gotten us this foreign, just taking out to, uh, to another level. >>I certainly wouldn't consider it to be like that. Partners air separate part of our They're still definitely part of the community. It's just they have slightly different problems. And, you know, there were folks from all sorts of different companies who are partners in the contributor summit. Yesterday >>there were >>actually, you know, participating and you know, folks swapping stories and listening to each other and again being part of that feedback. >>Maybe just a little bit broader. You know, the other communities out there, I think of the Cloud Native Computing Foundation, the Open Infrastructure Foundation. You're wearing your soul pin. I talk a little bit of our handsome How rentable plays across these other communities, which are, you know, very much mixture of the vendors and the end users. >>Well, I mean and will certainly had Sorry. Are you asking about how Ansel is relating to those other communities? Okay, Yeah, because I'm all about that. I mean, we certainly had a long standing sort of, ah fan base over in the open stacks slash open infrastructure foundation land. Most of the deployment tools for all of you know, all the different ways. So many ways to deploy open stack. A lot of them wound up settling on Ansel towards the end of time. You know, that community sort of matured, and, you know, there's a lot of periods of experimentation and, you know, that's one of the things is something's live. Something's didn't but the core parts of what you actually need to make a cloud or, you know, basically still there. Um And then we also have a ton of modules, actually unanswerable, that, you know, help people to operationalize all their open stack cloud stuff. Just like we have modules for AWS and Google Cloud and Azure and whoever else I'm leaving out this week as far as the C N. C f stuff goes, I mean again, we've seen a lot of you know how to get this thing up and running. Turns out Cooper Daddy's is not particularly easy to get up and running. It's even more complicated than a cloud sometimes, because it also assumes you've got a cloud of some sort already. And I like working on our thing. It's I can actually use it. It's pretty cool. Um, cube spray on. Then A lot of the other projects also have, you know, things that are related to Ansel. Now there's the answer. Will operator stuff? I don't know if you want to touch on that, but >>yeah, uh, we're working on. We know one of the big questions is ah, how do answerable, uh, and open shift slash kubernetes work together frequently and in sort of kubernetes land Open shift land. You want to keep his much as you can on the cluster. Lots of operations on the cluster. >>Sometimes you got >>to talk to things outside of the cluster, right? You got to set up some networking stuff, or you gotta go talk to an S three bucket. There's always something some storage thing. As much as you try to get things in a container land, there's all there's always legacy stuff. There's always new stuff, maybe edge stuff that might not all be part of your cluster. And so one of the things we're working on is making it easier to use answerable as part of your operator structure, to go and manage some of those things, using the operator framework that's already built into kubernetes and >>again, more complexity out there. >>Well, and and the thing is, we're great glue. Answerable is such great glue, and it's accessible to so many people and as the moon. As we move away from monolithic code bases to micro service's and vastly spread out code basis, it's not like the complexity goes away. The complexity simply moves to the relationship between the components and answerable. It's excellent glue for helping to manage those relationships between. >>Who doesn't like a glue layer >>everyone, if it's good and easy to understand, even better, >>the glue layers key guys, Thanks for coming on. Sharing your insights. Thank you so much for a quick minute to give a quick plug for the community. What's up? Stats updates. Quick projects Give a quick plug for what's going on the community real quick. >>You go first. >>We're big. We're 67 >>snow. It was number six. Number seven was kubernetes >>right. Number six out of 96 million projects on Get Hub. So lots of contributors. Lots of energy. >>Anytime. I tried to cite a stat, I find that I have to actually go and look it up. And I was about to sight again. >>So active, high, high numbers of people activity. What's that mean? You're running the plumbing, so obviously it's it's cloud on premise. Other updates. Projects of the contributor day. What's next, what's on the schedule. >>We're looking to put together our next contributor summit. We're hoping in Europe sometime in the spring, so we've got to get that on the plate. I don't know if we've announced the next answer will fast yet >>I know that happens tomorrow. So don't Don't really don't >>ruin that for everybody. >>Gradual ages on the great community. You guys done great. Work out in the open sores opened business. Open everything these days. Can't bet against open. >>But again, >>I wouldn't bet against open. >>We're here. Cube were open. Was sharing all the data here in Atlanta with the interviews. I'm John for his stupid men. Stayed with us for more after this short break.

>> Live from San Francisco. It's the cube covering IBM thing twenty nineteen brought to you by IBM. >> Welcome back to the Cube here in Mosconi North at IBM. Think twenty nineteen. I'm stupid. And my CLO host for the segment is Day Volante. We have four days, a water wall. Coverage of this big show happened. Welcome back to the program. Jason McGee, who is an IBM fellow, and he's the vice president. CTO of Cloud Platform at IBM. Jason, Great to see a >> guy to have fair. >> All right, So, Jason, we spoke with you at Que Con Way. We're saying it's a slightly different audience. A little bit bigger here. Not as many hoodies and jeans and T shirts a little bit more of a business crowd were still talking about clouds. So let's talk about your kind of your role here at the show. What's gonna keep you busy all week? >> S o? I mean, obviously, cloud is a huge part of what's going on. I think talking a lot about both public and private, about hybrid and some are multi called management capabilities. You know, my role as the leader called Platform. I'm talking a lot about platform as a service and communities and containers in the studio and kind of all the new technologies that people are using to help build the next generation of applications. >> All right, so we've had a few interviews today already talk about some of the multi cloud pieces. We had Sandberg on alien talk about eternity. So first you're gonna help correct the things that he got >> anything. Gang >> and service measures have been a really hot conversation the last year or so SDO envoy and the like t talk to us about where IBM fits into this discussion of service meshes. >> Yeah, so you know, I think >> we've been on this kind of journey as an industry of last year's to build anew at platform on DH service meshes kind of fit the part of the problem, which is, How does everything talk to each other and how to actually control that and get visibility into it? You know, IBM has had a founding role in that project. My team at IBM and Google got together with the guys, a lift to create it. Theo, what I'm most excited about, I think a twenty nineteen is that's that technology is really transitioning into something people are using in production and their applications. It's becoming more of kind of the default stack that people are using Really helping them do security invisibility control over their applications? >> Yeah. What? One thing that I heard just from the community and wonder if you could tell me is, you know, is dio itself. The governance model is still not fully into CNC s. Yeah, I heard a little bit, hasn't he? On some envoy? Of course. Out there in the like. So, you know, where are we? What needs to happen to kind of >> move forward? Yeah, you're right. So we're not there quite yet. We're pushing hard to make that happen. Certainly. From an IBM perspective, we absolutely believe that CNC F is the right home for Osteo as you mentioned some of the pieces like Envoy or they're ready. You know, C N c f has done such a tremendous job over the last eighteen months. Really rallying all the core technologies that make up this new coordinate A platform that we're building on costo is no out there's one. Oh, it's been sure people are using it. You know, that last step needs to happen to get into the community. >> So I have to ask you So things move so fast in this world, you go back to the open stack days, and that was going to change the world. And then Dakar Containers. And then Cooper netease, usto I can't help but thinking, Okay, This isn't the end of the line. What's Jason? What's the underlying trend here that's going on in the coding world? Yeah, sure. I'll put it in, maybe in >> my own lens. Given my history, you nominal WebSphere app server guy. You know that in the first half of my career I built that Andi, >> I think the fundamental >> problem solving is actually exactly the same. It's like, how do you build a platform that's app developers focus on building their APS, and I'll focus on all the plumbing and the infrastructure for running those aps. We did that twenty years ago in Java with APP servers, and we're doing it now with cloud, and we're doing it on top of containers. Things like usto like, while they're important in their own right there really actually Mohr important because they're just part of this bigger puzzle that we're putting together. And I think for the average suffer developer, they shouldn't really have to care about. What part of this deal will part is is Cuban eighties. And which part is K native like all that needs to come together into a single platform that they can use to build their APS and run them security. Right? And and I think it's Seo is just recognizing that next piece. You know, I think we've all agreed on containers and communities. We all talk about it all the time, and it's tio Is that next layer I catalyze securing >> control things. Yeah. So you teed it up nicely because we want out. Developers just be able to worry about the application. So you mentioned K native. The whole server list trend is one where you know the idea, of course, is I shouldn't have to worry about the infrastructure layer it just be taking care of me. We've talked about it for pass for a number of years. There are various ways to do it. So at, uh, Cube Colin and we've been looking for about the last year. Now you know, Where does you No, Crew, Burnett, ease and surveillance. How do they fit together? And K Native looks to be a pieces. Toe bridge. Some of those barrels? Absolutely. Where are we and what? What? What's? What's IBM doing there? >> So I think >> you rightly say that they should fit together like they're all part of this continuum of how developers build APS. And, you know, if you look at server, less applications, you know, there's the servos to mention I'm personally not a big service terminology fan. I think they're Maura about event oriented computing. And how do you have a good model for event oriented systems today? With Cuba Netease, anise Teo, I think we've built the base platform, I think, with a native what we're doing is bringing server lists and also just kind of twelve factor applications into the fold in a more formal way on when we get all those pieces together and we integrate them. I think then developers really unleashed to just build their application, whatever way it makes the most sense for what they're doing. And some things like server lists of Anna Marie. And it's going to be easier. And some problems. Straight containers will be an easier way to do >> it. You know, you say you don't like survivalists you like event better a function. So so explain that to the audience, like Why? Why should we care? And why is that different? How is that different? Yeah, I think, for >> a couple things. First off, the idea of server lists applies much more broadly than just what we think of this kind of function based program. You know, like any system that does a good job of managing and masking the infrastructure below me, you could consider a surveillance system, right? So when you just say server Lis, it's kind of like secondhand for functions. I'd rather we just kind of say, functions because that's actually a different programming model where you kind of trigger off of events and you write a functional piece of code and the system takes care of those details. You could argue that caught foundries, a server list system in the sense that you just as a developer anyway, you just see if push your code and it just runs and its scales and it does whatever you need, right? So part of my mission, you know, part of what I look at a lot is how do we bring all these things together in a way that is easy for the developer to stay focused. It steals a great example. You know, one of things were announcing this week is managed osteo support as part of our community service. What does that really mean? It means the developer can use the capability Viste without worrying about How do I install in Rennes D'oh, which they don't really care about? They just really care about how they get value out of its capability. >> Yeah, that's one of the things that having watched all these crew Benetti system and the like is how many companies really need to understand how to build this and run that because can I just get it delivered to me as a service? And therefore that you know that whole you know what I want out of cloud? I want a simple model to be able to consume, Not necessarily. I want to build the stuff that's important to me and not the rest of you. >> And I think if you look at the industry, there's really, I think, kind of two dominant consumption models that have actually emerged for people really using these things, there's public cloud platforms you're delivering things as a service. And then there's kind of platform software stacks like open shifts like I've been called private, which take all of these pieces and bring them together. And I think for most developers, they'll consume in one of those two ways because they don't really want the task of how to assemble all these pieces together. >> Tio, go back to the service piece like what? One distinction I heard made is okay. If I can really scale it down to zero, if I don't need to make it, then that can be serve a list. But there there's alternatives coming out there like what K native has. If I want to run this in my own environment, it's not turbulence because I do need toe. It might be functions, but I need to manage this environment. The infrastructure is my responsibility, not some >> service provider, right? And I think if you'll get server list to me, I was personally, I always think of it in kind of two scenarios. There's like surveillance as ah program remodel in a technology and surveillance as a business model, right? As a consumption model for payment. I think this programming model parts applicable in lots of cases, including private clouds. And in Custer, the business model parties, I think, frankly, unique to public. I'll thing that says I can just pay for the milliseconds of CPU, Compute that amusing and nothing more. >> That's a good thing for consumers. For >> the consumer, it's actually good thing for cloud providers because it gives us a way Tio reuse our infrastructure and creative ways, Right? But I think first and foremost, we have to get Mohr adoption of it as a programming model that developers used to build their applications and do it combined with other things. Because I think most realistic APs aren't gonna all be cirrhosis or all B Cooper nineties. They're going to be something. >> Yeah, right. It's like everything else. It's it's you know, what percent into the applications? Will this takeover? We had this discussion with virtual ization. We've been having this discussion with cloud and certain list, of course, is is pretty early in that environment. K native did I hear is there's some announcement this week that IBM >> so Soak a native, obviously is a project is kind of much earlier in its maturation and something like Castillo is. But we're making that available as part of our Republican private cards as well, Really? So people can get started with the ideas of K native. They can have an easy way to get that environment stood up, and they can start building those applications on DSO. That's now something that, you know, we're kind of bringing out as we work in the community to actually mature the project itself. >> Excellent. One of the things everybody's, of course, keeping an eye on. I saw Arvin Christian talking about the clouds. Tragedy is how red hat fits into all this. So we know you can't talk about kind of post acquisition. But red hats involved in K native. They're involved in a lot of the >> services and developers you gotta be exciting for. Yeah, >> it is. And obviously, like, Look, we've been partners for many years, you know, in on the open source side of things. We've worked closely with Red Hat for a long time. We actually view the world in very similar ways. You know, like you said, we're working on a native together. We've been working on Open West Feather. We obviously work in Cuban eighties together. So personally, I'm pretty excited about them coming in IBM. Assuming that acquisition goes through, they, you know, they fit into our strategy really well. And I think we'll just kind of enhance what we've all been working to build. >> All right, Jason, what else? What's looking? You talk about the maturity of these solutions, give us, um, guide post for the people watching the industry that we should be looking at as twenty nineteen rolls through >> us. So I think there's a >> couple things that, you know, I think this unified application platform notion that we've been kind of touching on here, I think will really come into its own in twenty nineteen. And and I would really love to see people kind of embraced that idea that we don't need. Three container stacks were not tryingto build these seven things. You know, one of things I'm kind of excited about with a native is by bringing server lists and twelve factor into Cuba Netease. It allows each of those frameworks to be kind of the best they can be at their part of the problem space and not solved unrelated problems. You know, I looked at the kind of server less versus coop camps, you know, the purest. And both think all problems will be solved in their camp. Which means they tried to solve all problems. Like, how do I do state full systems and server, Wes. And how do I bring in storage and solve all these things that maybe containers is better at. So I think this unification that I see happening will allow us to have really high efficiency, twelve factor and surveillance in the context of Koob and will change how people are able to use these platforms. I think twenty nineteen is really about adoption of all of this stuff. You know, we still are really early, frankly, in the kind of container adoption landscape, and I think most people in the broader industry or just kind of getting their feet wet they all agree that they're all trying, but they're just starting, and he knows a lot of interesting work. >> Jason, are there any anything that air holding people back? Anything that you You know what? What do you see is some of the things that might help accelerate some of this adoption? >> Yeah, I think one of the things that's >> holding people back is just the diversity of options that exists in the cognitive space means you guys have all probably rising like the C in C F landscape chart. I've never seen so many icons on something in my life. That's really frightening for the average enterprise. To look at a picture like that and go like which of these things are going to be useful, which are going to exist in a year like how Doe, I bet, make that sort >> of those things. So I think that's actually >> help people back a lot. I think that kind of agreement around communities that happened in the last eighteen months or so was really liberating, for a lot of people have helped them kind of move forward there. I think if we can all agree on a few more pieces around this deal, reckon native like it'll really help kind of unlock people and get them trying actually doing it. And I don't think it's anything more than picking a project and starting. I think a lot of enterprises over analyze everything, and they just need to pick something and go and learn. And they'll >> so pick some narrow use case pick, pick an app, pick >> a use case and go do it right and you'll learn and you'll figure out how it works for you. And then you do the second and the fourth in the tenth. And before you know it, you're on your way. That's what we did at IBM ourselves, and you know, now we're running our whole entire public out on top of communities. >> Jason and any any warnings from that kind of experience that you trade to users? A CZ. They looked forward. >> Yeah, we had a >> lot of learnings from music. One is we could run a heck of a lot more diverse work less than we thought when we started. You know, we're running databases where any data warehouses, running machine learning. We're running Blockchain. We're running every kind of application you didn't think could ever work on containers on containers s so one of the lessons Wass. It's much more flexible than you think. It isthe right. The >> other thing is you >> really have to rethink everything. Like the way you do compliance, the way you do security, the way you monitor the system. Like all of those things I need to change because the underlying kind of container system enables you to solve them in such a powerful way. And so if you go into it just thinking, Oh, I'm just going to change this one part of how I do aps and the rest will change. I think you'll find in a year that you're changing the whole operating model around your environment. >> Well, Jason, rethink everything we're here at IBM. Thing up twenty nineteen. Thinks is always for catching up with Thanks for everything going on for David. Want a, um, stew? Minutemen got three more days of live coverage here for Mosconi North. If you hear, stop by and say hi or reach out to us on the interwebs. Thanks so much for watching the cues.