 The Cube presents KubeCon and CloudNativeCon Europe 2022, brought to you by Red Hat, the CloudNative Computing Foundation and its ecosystem partners. Welcome to Valencia, Spain, and coverage of KubeCon, CloudNativeCon, Europe 2022. I'm Keith Townsend, your host of the Cube, along with Paul Gillum, senior editor, enterprise architect for SiliconANGLE, on Recode, senior ready, senior IT analysts for giga-owned. This has been a full day, 7,500 attendees. I might have seen them run out of food. This was just unexpected. I mean, the escalated, from what I understand, it went from capping it off at 4,000 gold, 5,000 gold in it all, finally at 7,500 people. I'm super excited for, today's been a great day of coverage. I'm super excited for tomorrow's coverage from the Cube, but first off, we'll let the new person on stage take the first question of the wrap up of the day of coverage. Enrico, what's different about this year versus other Cubans or CloudNativeConversations? I think in general, it's the maturity. So we talk a lot about day two operations, observability, monitoring, going deeper and deeper in the security aspects of the application. So this means that for many enterprises, Kubernetes is becoming real critical. They want to get more control of it. And of course, you have the discussion around FinOps, around cost control, because we are deploying Kubernetes everywhere. And if you don't have everything optimized, control, monitor it, you know, cost go to the roof. And think about deploying the public cloud. If your application is not optimized, you are paying more. But also in that, on premises, if you are not optimized, you don't have a clear idea of what is going to happen. So capacity planning become the nightmare that we know from the past. So there is a lot of going on around these topics. Really exciting actually. Less infrastructure, more application. That is what Kubernetes is in the end. Paul, help me separate some of the signal from the noise. There is a lot going on, a lot of overlap. What are some of the big themes of takeaways for day one that enterprise architects, executives need to take home and really chew on? Well, that Kubernetes was a turning point. Docker was introduced nine years ago. And for the first three or four years, it was an interesting technology that was not very widely adopted. Kubernetes came along and gave developers a reason to use containers. What strikes me about this conference is that this is a developer event. Ordinarily you go to conferences and it's geared toward IT managers, towards CIOs. This is very much geared toward developers. When you have the hearts and minds of developers, the rest of the industry is sort of pulled along with it. So this is ground zero for the hottest area of the entire computing industry right now. It is in this area, building distributed services, microservices-based, cloud-native applications. And it's the developers who are leading the way. I think that's a significant shift. I don't see the managers here, the CIOs here. These are the people who are pulling this industry into the next generation. One of the interesting things that I've seen, when we've always said Kubernetes is for the developers. But we talked with Anacond from MoneyGram, who's an end user. He's an enterprise architect. And he brought Kubernetes to his front-end developers and they kind of rejected it. They said, what is this? I just want to develop code. So when we say Kubernetes is for the developers or the developers are here, how do we reconcile that mismatch of experience? We have enterprise architect here. I hear constantly that the Kubernetes is for developers, but is it a certain kind of developer that Kubernetes is for? Well, yes and no. I mean, the paradigm is changing. Okay, so and maybe a few years back, it was tough to understand how, you know, make your application different. So microservices, everything was new for everybody. But actually, everything is changing to a point and now the developer understands, you know, is neural. So, you know, going through the application, APIs, automation, because the complexity of this application is huge. And you have, you know, 7.24 kind of developments or sort of deployments, so you have to stay always on, et cetera, et cetera. And actually, to the point of, you know, developers, you know, bringing this new generation of decision makers in there. So they are actually decision makers. They are adopting technology. Maybe it's a sort of shadow IT at the very beginning. So they are adopting it, they are using it and they are starting to use a lot of open source stuff and then somebody upper in the stack, the executive says, what are, you know, they discover that the technology is already in place is a critical component and then it's, you know, transformed into something enterprise, meaning, you know, paying enterprise services on top of it to be sure, support contracts and so on. So it's a real journey and these guys are the real decision makers. They are at the base of the decision making process, at least. Cloud Native is something we're going to learn to take for granted. You know, when you remember back, remember the fail whale in the early days of Twitter when periodically the service would just crash from traffic or Amazon went through the same thing, Facebook went through the same thing. We don't see that anymore because we are now learning to take Cloud Native for granted. We assume applications are going to be available, they're going to be performant, they're going to scale, they're going to handle anything we throw at them. That is Cloud Native at work. And I think we forget sometimes how refreshing it is to have an internet that really works for you. Yeah, I think we're much earlier in the journey. You know, we have Microsoft on the Xbox team talked about 22,000 pods running, NinkertD, some of the initial problems and pain points around those challenges. Much of my hallway track conversation has been centered around, as we talk about kind of the decision makers, the platform teams. And this is what I'm getting excited to talk about in tomorrow's coverage. Who's on the ground doing this stuff? Is it developers as we see or hear are told? Or is it what we're seeing from the Microsoft example, the MoneyGram example, where central IT is kind of getting it? And not only are they getting it, they're enabling developers to simply the right code, build it and Kubernetes is invisible. It seems like that's become the holy grail to make Kubernetes invisible, Cloud Native invisible. And the experience is much closer to Cloud. So I think that it's an interesting, I mean, I had a lot of conversation in the past year is that it's not that the original, traditional IT operations are disappearing. So it's just that traditional IT operation are giving resources to these new developers, okay? So it's a sort of wallet garden. You don't see the wall, but it's a wallet garden. So they are giving you resources and you use this resources like an internal cloud. So a few years back we were talking about private cloud. The private cloud as, you know, as a, let's say the same identical paradigm of the public cloud is not possible because there are no infinite resources or well, whatever we think are infinite resources. So what you're doing today is giving these developers enough resources to think that they are unlimited and they can do automatic provisioning and do all these kind of things. So they don't think about infrastructure at all but actually it's there. So IT operation are still there providing resources to let developers be more free and agile and everything. So we are still in a, I think an interesting time for all of it. Kubernetes and Cloud Native in general, I think are blurring the lines, traditional lines. Development and operations always were separate entities. Obviously with DevOps, those two are emerging but now we're moving, when you add in shift left testing, shift right testing, DevSecOps, you see the developers become much more involved in the infrastructure and they want to be involved in infrastructure because that's what makes their applications perform. So this is going to cause, I think, IT organizations to have to do some rethinking about what those traditional lines are, maybe break down those walls and have these teams work much closer together and that should be a good thing because the people who are developing applications should also have intimate knowledge of the infrastructure they're going to run on. So Paul, another recurring theme that we've heard here is the impact of funding on resources. What have your discussions been around founders and creators when it comes to sourcing talent and the impact of the markets on just their day to day? Well, the sourcing talent has been a huge issue for the last year, of course. Ever since the pandemic started, interesting, one of our guests earlier today said that with the meltdown in the tech stock market, actually talent has become more available because people who were tied to their companies because of their stock options are now seeing those options are underwater and suddenly they're not as loyal to the companies they join. So that's certainly for the startups, there are many small startups here, they're seeing a bit of a windfall now from the tech stock bust. Nevertheless, skills are a long-term problem. The U.S. educational system is turning out about 10% of the skilled people that the industry needs every year and no one I know sees an end to that issue anytime soon. So, Enrico, last question to you. Let's talk about what that means to the practitioner. There's a lot of opportunity out there. 200 plus sponsors I think is worth, the project's 200 plus. Where are the big opportunities as a practitioner is I'm thinking about the next thing that I'm going to learn to help me survive the next 10 or 15 years of my career. Where do you think the focus should be? Should it be that low-level cloud builder or should it be at those levels of extraction that we're seeing and reading about? I think that it's a good question. The answer is not that easy. I mean, being a developer today for sure grants you a salary at the end of the month. I mean, there is high demand but actually there are a lot of other technical figures in the data center, in the cloud that could really find easily a job today. So, developers is the first in my mind. Also because they can serve multiple roles. It means you can be a developer but actually you can be also with the new roles that we have, especially now with the DevOps, you can be somebody that supports operation because you know automation, you know a few other things. So, you can be a CIS admin of the next generation even if you are a developer, even when you started as a developer. QCon 2022 is exciting. I don't care if you're a developer, practitioner, a investor, a IT decision maker, CIO, CXO, there's so much to learn and absorb here and we're going to be covering it for the next two days. Me and Paul will be shoulder to shoulder. I'm not going to say you're going to get sick of this because it's just all great information. We'll help support all of this. From Valencia, Spain, I'm Keith Townsend along with my host, Enrico Signoretti, Paul Gillan. And you're watching the QV leader and high tech coverage.