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

>> Narrator: From around the globe, it's theCUBE. With coverage of KubeCon, and CloudNativeCon Europe 2020 virtual, brought to you by Red Hat, the Cloud Native Computing Foundation, and ecosystem partners. >> Hi, I'm Stuart Miniman, and this is theCUBE's coverage of KubeCon, CloudNativeCon, the European show, which of course for 2020 is virtual. Always love when we get to talk to the practitioners, as well as many of them heavily involved in what happens at the CNCF, you know, all these open source communities. Happy to welcome to the program, first time guest Katie Gamanji. She is a Cloud Platform Engineer with American Express, and she's also a member of the CNCF's TOC, which is the technical oversight committee. Katie, thanks so much for joining us. >> Thank you for having me today. I'm quite excited to be here. >> Excellent. Well, you are, as I mentioned, you're part of the TOC. You also present at the show last year. You presented at one of the KubeCon shows this year. As I mentioned, you were with American Express now. I believe it was Conde Nast, You shared some of the journey along those lines. Maybe for our audience, give us a little bit about, you know, your background, and what's got you involved in, you know, some of these projects in communities. >> Absolutely. Oh, such a good question. I can talk forever about that. My passion about Cloud Native. So, my name is Katie Gamanji, and I am one of the Cloud Platform Engineer for American Express. I joined American Express around five months ago, and I am part of the team that aims to transform the current platform, by embracing the Cloud Native principles, and making the best use of the open source tools. As mentioned previously, I've been working for Conde Nast. I've been in that role for almost two years. And as part of that role, we aim to create a centralized globally distributed platform that had Kubernetes as a central piece. And that was the role which actually got me involved more into the Cloud Native tooling, and I've been exploring them quite heavily since then. And that's why I wanted to get more in terms more contribution to the community. I've been doing that previously for different talks, and actually writing blog posts on different, giving different guides on how to start using some of the tooling. However, this year I decided to apply for TOC. And I've been elected as a TOC from the end user perspective, so I'm representing pretty much the overview of what end users think that the next direction should be within the Cloud Native landscape. And for the last, actually for the past five months, I've been on the TOC, with the CNCF, and it's only 11 of us. And we are in charge to make sure that we can guide, and set this technical vision for this year for the CNCF landscape. >> Yeah. Katie, I definitely want to talk about the TOC piece, but I want to back up a little bit. And you talked about some of the tooling, you talked about the community. Help me understand a little bit, you know, from a business standpoint, why you know, Conde Nast, American Express, looking towards using, Kubernetes and all of these open tours toolings. What was the charter, the challenge put before them, that felt that doing things this new way would help them. >> I think this actually goes a couple of years back. In my previous role before Conde Nast, I was in a team which aimed to provision infrastructure, but it was in a more, how can I say old fashioned manner? We had to configure our data centers manually, configure the VMs and processes. We had (indistinct) of automation. But at the time, this was maybe three years ago. I started to look into Kubertetes, and it was still baby steps, like, there was interest from the community, and I really wanted to, kind of get my hands on it more. And when I was looking for a role, which was at Conde Nast, I was looking for something which aimed to introduce containers in the entire infrastructure. And I think Conde Nast actually was very appealing as a role because not many expect for a media company to invest in technology, and actually the underlined infrastructure. So, from that perspective, I thought it's actually quite a good use case to change this perspective in the community. As well, with Conde Nast, it was a very international company. We had different business units around the world. All of them had different tech stacks. So, the challenge itself, how do we unify that? How do we centralize the deployment process of the application and serving our requests? But at the same time, have these individualized layer for every single market to still personalize their content. So, it was a very good project, I think, for me to further go into the Cloud Native to link, and actually definitely proved to be the right role for that. And currently I am in a different role. It's actually a financial company. But I think this is my personal challenge. I think there is a perception of financial companies moving towards modernization of their infrastructure, but it's still going quite slowly. And I think my personal challenge in this perspective is to make sure that actually FinTech is a thing, but FinTech in Cloud Native, actually using open source tooling is possible. Obviously, we can transition that to some of the secondary base, maybe not the core base of the business, but this transition, actually getting the change going is the most important bit. Once actual goes, it's just a boulder like, downhill, which is going to take everything around, and refactoring bit by bit. >> Yeah. Katie, you brought up a really important point. You know, in today's world, especially, you know, this year 2020 with the global pandemic going on, being able to react fast is so important regardless of what industry you're in. You talked about in your previous role, you had a global rollout to work across a lot of environments. Help us understand a little bit underneath the covers. You know, using this tool set, how does this help you move faster? How does it, you know, in some ways unify teams, regardless of what challenges they have? >> I think for us at least at Conde Nast, it was quite important to have one platform, so actually centralized all of our required, actually gather all our requirements, and translate them in within the platform. So, what we actually wanted, was to us to have Kubernetes as the gravitational point. Now, with Kubernetes, we'd have some of the main functionalities such as portability or flexibility. We'd be able to scale to very easily without, actually with minimal effort, but more importantly, we'll be able to transport our platform to different regions. So, to actually replicate the entire tech stat. So once we have these centralized platform, it was very easy for us to distribute them. For example, in regions across the US. And that time I was working there at least. There was an intentional strategy to replicate the tech stack in China. And that'll be very easy because with Kubernetes you just have this lifting shift capabilities. As long as you have BMs, you'll be able or compute, you'll be able to run the entire Conde Nast tech stack. So that was a very kind of big point for us to move to Kubernetes. Whilst I think in American Express, the strategy is completely different. It's still a lot of heritage infrastructure we have at the moment, actually we are running on Kubernetes. There is but the provider itself is Open shave This proving to be showcasing some of the issues for us moving forward, and we'd like to transition to a more neater way to run Kubernetes. And this potentially means, we haven't finalized the decision yet but it might we'd be using probably a cloud provider, or it might be the case of actually running Kubernetes self service. So we've actually got to maintain our clusters. This is not defined, but the underlying idea is that we want to be more kind of modern version of Kubernetes or managing Kubernetes moving forward. So this is one of the strategies. But I think within American express, the main underlying idea is that we really want to inner source most of the configuration. Historically we had different contractors and vendors working on our bits and pieces, we'd like to actually get all of these in house and have a centralized way to manage our infrastructure. So this is the underlying project which I think is going to take a while, but again there is an intention to include Cloud Native to link and technologies, and I think it's a very healthy thinking in terms of technology. >> Well Katie, you highlighted two really important topics that we've seen out there. Number one is exactly where my infrastructure is, it's going to change and I don't need to think about it. So you talked about public cloud, data centers, it might change in the future. And number two, making sure that you have the skill set in house. Something we definitely learnt from the outsourcing trends of the past was, when things need to be changed, if I had to rely on someone else it became very difficult. So if you're leveraging Kubernetes and you have the developer chops to be able to respond to the business in an agile way, you're going to be much more ready to be able to handle whatever happens in the future. >> Exactly >> So important. >> I want to switch and talk a little bit about your TOC work, presenting at the show. It's great to see companies enabling their employees to participate in this sort of thing. Help me understand how for you personally and what is the support that you get from your last job, your current job to participate in these open source projects in communities. >> Right. I think both of the companies, Conde Nast and American express, they're quite interested in been part of the Cloud Native community. With Conde Nast, they actually a part of end users. With American Express I think there is a thinking to actually join the end user community. So this might be something which will happen in future. I cannot guarantee but I'm hoping. This is going to be again one of my personal challenges, making sure we get in the community and share some of our used cases. But for now I think both of the companies actually understand the value of been part of actually using Open Source, but more importantly, understanding how other companies use that. Not one use case, especially when it come to Kubernetes, not one Kubernetes platform is going to be the same. There's always going to be different underlying technologies that plug in into it. There's always going to be different ways to use different tooling. And having these concentrated community and source of information, I think the companies actually understand the value in that and contributing to that. So I think, this is something which I've been quite passionate about to actually understand some of the strengths, to understand how some of the tooling are used, and if there is an actual hope for a project, or it's something which actually specialize into a very minimal kind of niche problem, and is going to be useful for maybe one or two big companies, it depends. So I think this is something I've been passionate about and I've actually had a support throughout. In my previous company and my current company I have very strong support from my higher ups to actually contribute more and be part of the end users community, and as such being a TOC as well. Which comes with a bunch of responsibilities as well. But I think in terms of either support, definitely I had the necessary support all the way through which I'm quite thankful. >> Katie, you mentioned some of your passions, I know from what I've read online that you're passionate about some of the tooling there, and that's some of what you're sharing through your presentations. So, I'd love if you could share a little bit about what we're going to be talking about at the Europe show right now and any other kind of tools that are getting your time and attention these days. >> So I think lately, I've been exploring Cluster API the new release. I've been waiting for new release. Actually everyone has been waiting for the new release for a couple of months. Now we actually have v1L for three end points with some of the cool features such as, manage control place for Cluster. And the second tool or set of toolings I'm working lately are the ones which concentrate on the Gitops model. So during the session at Kubecon in Europe this year, I will be presenting Cluster API, a guide on how to get started. So an overview of all the components necessary to create your own Clusters. In different cloud providers as well. But I will crown that presentation by delivering a demo of how can you provision your Custer with Gitops. And I'm going to use Argo CD at the moment. And the end result is going to be provisioning your Cluster in AWS by having maybe one click, and you have a Cluster refill masters, maybe five nodes and you just wait. Pretty much you can have a coffee while your Cluster is provisioning. But more importantly with Cluster API, again we have usable manifest which will allow us to have this one interface to integrate with different cloud providers. So we actually have this interoperobility Of manifest across different cloud providers. So look forward to that. >> Excellent. Katie, last question I have for you, what advice would you give your peers? Where do you see need for more participation, as people that are getting into this environment. Where do you think they can help? >> Oh such a good question. I think contribution is necessary in most of the sags In the Kubernetes community. So, I think it depends on the passion everyone has, if they're quite passionate about the networking, or storage or even service, there is going to be a group of people that have the same passion and interest with you. So please reach out and contribute. I think I never think I'll like to mention, you done necessarily need to be an active coder to be part of the sags or to be part of the Cloud Native. Because being in technology of course is an advantage, however, most of the ideas in actually making sure that we cover used cases for different tooling, comes from a diverse user base as well. So if you have an interest I think that's going to be very good engine for to further enable different ideas within the sags. So I wouldn't be able to recommend a particular project, I think this is very specific to everyone's daily role (indistinct) But yeah I think within the CNCF, we have a collection of sags for which you pretty much would find a place for yourself and your skills. >> Well Katie thank you so much for sharing your journey and participating so actively in the community. Thanks so much for joining us. >> Thank you for having me today. >> All right stay tuned much more coverage from Kubecon, CloudNativeCon Europe 2020 virtual edition, I'm Stuartt Miniman, and thank you for watching theCUBE. (gentle music)