>>From San Francisco. It's the cube covering get lab commit 20, 20 Raji you buy get lab. >>Hi, I'm Stu Miniman and this is the cubes coverage of get lab commit 2020. We're here in San Francisco. It's a little bit chilly but uh, my first guests, uh, on the program are used to the weather cause they're coming to us from Wisconsin. Uh, both from Northwestern mutual, uh, sitting to my left here is Kyle person who is a senior engineer and sitting to his left is Sean who is also a senior engineer. Gentlemen, thanks so much for joining us. Thanks for having us. Alright. We thought, you know, both of us coming from colder climates that may be coming to San Francisco would be a little warmer, but they have hand warmers, they have warm drinks and it is the warmth of the community that will warm our innards. I'm short right there. It says get warm. That's what we're here to do. All right, Kyle, let's start with you. Northwestern mutual. I think most people are familiar with the organization, but give us a little bit of a, you know, how people should think of Northwestern mutual in 2020 and, uh, your roles. >>Yeah. So obviously we mean we're a large insurance company but also into financial services and products and we're really trying to become more of a digital company as well. We think that that's going to be a differentiator in the marketplace. You know, having apps that our customers can interact with, um, trying to speed up underwriting, things like that. So we're really just trying to be a technology company as much of an insurance company. Okay, >>great. And Sean, I understand you're, you're on the same team as Kyle helping you along with that digital transformation that that's been all the buzz for the last couple of years. Yeah. He can't get rid of me. We flew, you know, 1200 miles and I'm still sitting next to, uh, but yeah, at Northwestern mutual, I mean, going back a number of years now, the, the company started down this path of doing a digital transformation where we wanted to be, you know, a software company that is providing financial service and financial stability for our clients. So it was a big shift that we, we started, we knew we needed to modernize everything. So we started down that path. Great. So we had that. So Kyle, maybe if you, it can, you know, when did get lab enter the picture, what was kind of the initial use case and, uh, let's, let's go from there. >>Yeah, it was before my time. I'm, Chad has been there for a long time. Most of the ride, but uh, yeah, it's been several years and it's been, uh, you know, starting out with SCM, moving into CEI and then, you know, adopted sustainer journey that you hear about even in the keynote today. That's pretty much how we charted our course. Okay. >>So Sean, you've been there since the beginning of a, uh, to get lab usage? Pretty much it, it showed up a couple months before I got there. But, uh, going back to your early mid 22, yeah, 2015, uh, we had kind of a more of a pilot group of engineers that were, were starting out, you know, to get us down this path to where we wanted to go and they needed a new tool, something that worked better than what we currently had at an M and a, they settled on, on get lab because it provided, you know, one being open source was a huge selling point for us. Um, and it was just ever-growing. So it allowed our developers to really get going and get going much faster. Okay, great. And in the keynote, okay, Kyle, they were talking about how it's not just about the dev, the second the ops, but really not allowing everybody into the same tooling, even marketing and finance. What's kind of the breadth of the organization is it is mostly devs that dev and ops does security, you know, who, who's involved in using this tooling. >>It's everybody. We're a, we're figuring out our, you know, everyone's kinda got their own spin on things. So we're in that, um, classic position where I think we have the tooling sprawl that everyone talks about and we're, we're constantly evaluating, you know, how does Gilad fit into that picture? What do we bolt on? You know, we have the luxury of being able to integrate with other things as well. But then if certainly if we can get an economy of scale where we can just use get lab, it's to provide that seamless interface. That's something we always look to do too. All right. >>So Sean, my understanding is a NM is also using Coubernetties and that's something that you're involved in. So very money you bring us in people, you know, sometimes get misconstrued as to the scope and the purpose of, of Kubernetes. We've been at the cube con cloud date of con for a number of years, but uh, why don't you set the stage for us and kind of walk us through the, the what and the why of Kubernetes? Yeah. For us at least being able to leverage something like Kubernetes, which when you really back out and you know, do the 10,000 foot view, it's container management and being able to go into a more modern architecture. We're leveraging containers for pretty much whatever we can, or at least what makes sense. Um, and that's kind of how we started down the path with get lab moving into Kubernetes. You know, we were, we were trying to figure out like, where do we want to go so, you know, let's not just push the boat out a little, let's drop, kick the boat off the end of the pier and see where we end up. >>So we started working down that path of deploying get lab into Kubernetes cause it allowed us to easily expand and make the application highly available. So even if some easies go down in AWS, which knock on wood never happens. Uh, we're still good to go. Our users are, wouldn't even notice. Okay. Um, so you mentioned AWS. Is that your primary cloud, your only cloud? What, what is your cloud situation? Yeah, that's, that's a Northwestern mutual is public cloud. Okay, great. And speak a little bit to, you know, Amazon does have plenty of its own tooling. Uh, maybe a little bit about how get lab and, how those fit together for you. Um, well, I mean, we use get lab CIS specifically to be able to provision different services in one, not that we need as long as they fit near within our security requirements. And, you know, everything we do, we get vetted out through our internal processes, but it's really allowed our developers to move forward so much faster. >>You know, it's kind of gone are the days of, let me fill out a request for, you know, X, Y, Z and, you know, wait two as it goes through somebody's work queue and they eventually get around to it. Um, allowing our developers to just, you know, do their commits, get their, you know, peer review and just deploy and provision right away, allows us to get our applications to market just so much faster than even a few years ago. Alright. So Kyle, the two of you are presenting here at the show, uh, you know, we, we love, we heard GitLab talking on stages. You know, customers don't just use it, they commit, they add feedback in and they speak at the show. So maybe speak a little bit of, uh, you know, NMS, you know, involvement as to uh, you know, are you committing code and what, what are you speaking about? >>So we're here to speak about our journey on Kubernetes. I'm trans covering the application side and I'm going to talk about our, our dabble in Kubernetes CII. So we're, we're really looking to, um, we're looking for efficiencies I guess in, in density. That's a primary driver behind trying to explore the trail. But also, um, one of the things I'll talk about in the talk is, is boosting our security posture using Kubernetes. So a lot of times people are using API keys and they're getting stale and not being rotated. Uh, we can do some neat things with Kubernetes and it's native. I am offerings to boost our security posture by moving towards role based access and getting those credentials that are rotating and providing us, uh, you know, non stale sort of authentication credentials, things like that. >>Sean, yeah, pretty much covers it. Uh, uh, and beyond with the CIA, you know, being able to run and get lab itself within Qube and having the different components broken out and we're alive. It's, it, it's enabling us to limit any kind of attack plane that could exist. You know, it's, you have to get through a lot to even get to it. So it's really just been a huge, a huge plus for us. OK. I, I'd love to hear both. Both of you have been to these events a number of times. You're speaking to event. What, what, what's the value of coming to get loud commit? I mean, for me it's a, a huge networking thing and being able to relay our experiences that we've gone through to other people that are out in the community. I mean, I know lots of, you know, everyone wants to see, you know, what can you do in Kubernetes and like, here's some of the things that we've done. >>Here's some of the things that you know, works that didn't work. You know, we would recommend you going this kind of route if we were to start it over again. And beyond that, you know, meeting people from all over the world, like, uh, we were talking with some, uh, some guy, gentleman Nico from white duck who is from Germany. It's not something you get to do, you know, face to face all the time. Alright. Sean, can you share with our audience any of those? You know, if we could do it over again, we'd change something. Is it an organizational thing or technical piece or until don't don't use EFS for getting repo data. It will not end well for you can take away. All right. Kyle, how about you? You've been to a number of these shows, uh, you know, the networking, the piece or you know, what else, what, what, what, what for you personally and for NM, uh, you know, brings you back. >>Yeah. Networking is a big thing. I think it's also getting feedback on, you know, what we're doing. Does it make sense? Just like get lab is throwing things out there early, trying to tighten up that contribution loop. We want to get our ideas out there and then this is an opportunity for people to ask questions about our presentation. If maybe we're off in the wrong direction, maybe we can get that steered back on course. Um, you know, we're just really here to get the feedback. Yeah. I always love talking to people in the financial industry and you talk about open source, you know, if, if you went back, you know, five years ago, you'd probably get a little bit of sideways looks as to wait, you know, you're doing what, um, are we past that? Do do you feel are most people, uh, you know, really understanding where we are with, with cloud and open source in general that it, you know, it makes perfect sense for a financial institution to be part of it. >>I'd say at NM we, we've finally gotten past that curve and now we're, we're trying to, you know, make it even easier for our internal developers to easier participate in open source, you know, their internal products and contribute more to the community. Uh, we've completely done an about face from, you know, probably 15 years ago where it was open source. You wanted to, what to, yeah, let's go. How can we make things better? It's, it's all about, you know, our, our customers. So we want to make sure we create the best product and experience for them. That's awesome. Yeah, there's still some barriers there. I mean, it's all about managing risk, right? So you have to do things diligently and make sure that your bases are covered. And so it's not like it can be a free for all. We have to do our due diligence, but we, you know, we love to contribute. And we love to get up without their there as we can. All right. Well, Kyle and Sean, thank you so much for sharing with our audience. Best of luck with your presentations and, uh, have a great time at the show. Thank you. All right. Uh, thank you to, to NM for joining us. I'm Stu Miniman and thank you for watching the cube.