 Welcome, everybody. So how are you doing? Good, good. Very happy to be here. Hi, Cube call. Hello, everyone. So Elulita, I'd love to kick off today talking about developer experience. Can you share some of your wisdom with what's going on with you in the developer experience area? What are your thoughts? I keep hearing a lot about it in the hallway draft. Yeah, I think, again, developers are key to the cloud-native ecosystem. And there's a lot happening in the CNCF, as well as other foundations of the LF, such as CDF with developer tools and projects. Couple of the projects that are really getting adopted as you transform your business into cloud-native infrastructure are Argo and Flux CD. Many of you may be using it already. And what I have seen is that these two projects are really driving some of the adoption for new, modern, integrated infrastructure out of the box for CI, CD, which is Kubernetes native. Yeah, I think that, hi, I'm Kailin from Shopify. I think one of the really amazing things about using cloud-native tools and technologies in your developer experience is that you invite your developers to participate in a community. I mean, look at how many people are here. And when you're part of that community, you learn from each other and you share. So as end users, we have so many opportunities to get together and hear from each other what we're using, what's working well, what's not. And at Shopify, we use that to really empower our developers to not have to worry about infrastructure at all. The cloud-native universe has allowed us to build a whole bunch of really great tools that support our cloud platform, which is just the best. I think most developers at Shopify would say infrastructure just works, which is wild. It's a great answer. We at BlackRock, we're looking to drive developer experience through velocity, right? So developers are happy when they're shipping their code quickly. We're getting the business value out to the business quickly. We've already adopted things like Argo for our GitOps control plane and driving the cloud-native adoption. Really now it's about how do we get to that point where Shopify is where access to infrastructure that's external to the cloud-native infrastructure is easily available, readily available, and is imperative to our success because these developers need this access quickly and efficiently so that we can maintain those velocity numbers and ultimately get the business value out to the people that need it the most, the business and our customers that we're supporting. Hi, everyone. I'm Mukulika from Intuit and founding member of Argo. So at Intuit, actually using cloud-native technologies, our development velocity increased 9x in five years, which is amazing. We actually have a common platform which all developers in the company use to build not only microservices, but also platforms on top, whether it's ML platform, AI platform, stream processing platform and all of it. The whole company runs using the same standard with security and compliance built in. So it's amazing. Well, speaking of security and compliance, you're actually, that's a great segue into our next section, security. Oh my goodness, don't say that five times fast. What are you doing in the cloud-native security space? I would love to hear more. I always lock my door at night. Am I doing the right thing? Yeah, sure. So, you know, as Kailin said earlier, each team was managing their own infrastructure. So developers had to patch their AMIs with security patches and they used to hate it. Now, the entire, so we have around 350 Kubernetes clusters running thousands of microservices and actually monthly we upgrade these 350 clusters automatically with security patches. Developers don't even have to do anything. It's like get commit by the platform team and all the clusters are upgraded. Similarly, all our containers come from base images which are actually created by security teams. And then we have runtime security tools running in all clusters, build time security tools. Security teams love cloud-native. So we're doing something very similar. We're not quite at 355 or whatever you said yet, but we're in the hundreds and thousands of apps or hundreds of clusters, thousands of apps. We run it as a platform. We want the platform to provide the batteries included for our developers so that no strings attached, low touch. We've got a highly competent platform team, ops team that deliver it. But it takes adopting new practices, more policy as code, shifting more things left so people developing the platform, building on top of the platform can get early indicators that maybe they're doing something outside of compliance. And as a highly regulated company, security is absolute table stakes. And so we are very, very deliberately approaching it. Taylor. Wonderful. I mean, security is my jam. I am a infrastructure security engineer at Shopify. So secure everything, obviously. Developers don't need to build. No, I'm just kidding. We try really hard. Like Shopify is a company of builders. Our CEO is a builder through and through. And it is top of our mind to make sure that our builders are empowered to create whatever they need to, whenever they need to quickly. We really want to foster that creativity so that we're doing what matters most to us, which is making commerce better for everyone. And the way that my team does that is through building really, really strong guard rails on a wide paid path. So I know, like we've been saying, shift left for ages and ages, but sometimes I am getting used to the fact that we maybe need to shift right to allow developers space and make sure that we are supporting that creativity. We use all of the baked in security features in the platform that we use to support Kubernetes, but we also have a whole bunch of services that we've built internally that we call buddies that support a bunch of things like RBAC and network policies. And of course, we use secure based images. And we just kind of make sure that again, the people who are building things don't have to worry about it. We have it covered for them and CNCF allows us to do that. Definitely, and in fact, echoing what Kailin said, I think infrastructure and security kind of go lockstep. You cannot think about one without the other. And security in one sense has several good practices that can be used, which absolutely have to be considered and rolled out day one as you roll out your infrastructure. Some of them are really making sure that your developer pipelines, for example, your development pipelines are enabled with code scanning and foundational vulnerability scanning, which actually really helps in mitigating many of the security issues that you can prevent back out in production. So building day one with security in mind and having an comprehensive security architecture is just top of the list. The other part that is super important is to be able to have secrets management as well as other key core areas built in into your entire infrastructure pipeline so that you can really deliver security at scale for your production systems. Amazing, wonderful. Well, unfortunately, that's all the time that we have today for our end users and we'll have to pick up this conversation in the hallway track because I have some questions and some things to check on. Oh, wonderful. Thank you so much for stopping by today. Yeah, catch us in the hallway track. Great to see all of you and thank you again so much to all of our end users. You are what make cloud native run. Thank you so much everybody. Thank you. See you later.