 Good Morgan. Good morning. How is everyone? Yeah, good good. So who wants to see a couple demos this morning? Yeah, a little bit of technology. Great. Great. Well, I'm gonna start with some slides. How about that? I Always start my keynotes With a slide that looks something like this and there's a reason for that The reason is that in the Cloud Foundry community. We're extremely focused on developer experience I shorthand that as DX and think about the user experience of the applications that are built but for a developer their experience working with Software that's supposed to support the development life cycle is incredibly important and Ansi from from Pivotal everyone should know this haiku by now Wrote the haiku that describes really what that experience looks like for the Cloud Foundry application runtime Are there any poets in the room? So Alex and everyone else I have a challenge for you Come up with a haiku that covers our container runtime So you can send it to me later. I think that would be a lot of fun So let's transition and and just talk a little bit about the philosophy that the open source Cloud Foundry community has Around what we're doing We're not a bucket of tools It's a comprehensive open source platform That allows a lot of room for differentiation for the distributions and the services that use it But the level of maturity in the open source community that actually builds this software that shared is is really high And so I think about this is what does it mean to be open source? That's enterprise ready and it really boils down to four things and we're gonna spend time Both talking about as well as showing you How we're focused on security Deep integration not just into other platforms, but into the enterprise Scalability and then again that great developer experience and that's across any of the surface area the developers touch So let's let's start by talking a bit about the application runtime and some of the things we're doing around security Within Cloud Foundry there a lot it is a platform of microservices that work with each other in order to support that developer experience in order to Support the the upkeep and the telemetry that you need to manage your applications and One of the things that needed to be done and is complete at this point is that all the communication between those components had to be secured Now that's that's complete at this point, but more interesting though is how can a platform actually support The applications themselves that are being pushed into it. How can we provide those applications with credentials? With certificates, maybe the certificates even auto rotate for them. So there's a lot of work that's going into that If I dig deeper, I just I like this my favorite team the garden team I want to take a minute to talk about the level of focus they have on security So the garden team is is within the application runtime one of the lowest levels of the architecture It's not something that a developer directly interacts with But it's perhaps one of the most important components of the system because they're focused on being the most secure Environment for containers for a multi-tenant application platform The other thing I'd say is that I love the collaboration that the Cloud Foundry community has with other open source projects Run C is the library that was donated by Docker to the open container initiative and What's really interesting is how the Cloud Foundry community dove into that project in order to really make sure that its ability to run containers in a rootless way Right not not requiring root Would work and it would work well So now let's talk about credentials. I mentioned them meant in the moment ago When you think about what you need to do with credentials These are credentials of any type whether you're talking passwords or whether you're talking about Certificates you really need to do four things with them You need to be able to create them you need to persist them you need to encrypt them both in transit as well as in storage You need to be able to rotate them super easily Now credit hubs a project that if you haven't looked into you should because it's increasingly becoming a core part of how Cloud Foundry systems are deployed and managed But also increasingly becoming a key part of how Cloud Foundry can support the application developers need for certificates and credentials management it exposes Credits to operators the infrastructure itself and applications. I Also like to spend time to fit to just really congratulate the way that our open-source projects Think about and deal with vulnerabilities If you were to try to put together By using a number of different parts by yourself a platform that did everything that the Cloud Foundry platform does You would have an enormous amount of responsibility that you're taking on for your organization So our open-source community Handles this for you because we're providing a comprehensive platform again That the vendors are going to add a lot of value to but the core platform that's delivered by the open-source ecosystem is tracking all of the upstream operating systems Different services that are being supported all the languages that includes things like the Node.js framework the Java Spring community anytime there's a vulnerability in any of these projects that are brought together It's very quickly integrated and kicked out from the open-source community and on average We're releasing about twice a month and that velocity actually is very variable because if there's a critical vulnerability in Ubuntu, which is what our stem cells are based on today In about 48 hours you can expect to see a new stem cell get released That's pretty impressive especially for for an open-source community Switching topics. Let's let's talk about performance and scale Our application runtime changed architectures and one of the one of the ways that it one of the things it had to do when it Was switching to the new architecture was to hit a scaling target for one of the largest environments That's a public Cloud Foundry provider It got to the quarter million application instances mark and that's great For me though, it's much more important to understand and dig into the way that testing was done. This wasn't This wasn't a test that would just said hey, how many containers can we boot right? This was actually what does it mean to have a platform that's running a quarter million application instances? some of which are unhealthy and How does it continue to keep the promise that it made to the developers to restart to monitor the health to ensure that? Logging and telemetry data makes it back to you. So this was really important the entire framework All of the project teams were impacted in one way or another and they've all been focused on that performance Picking on one team because there's one release that was in February of this year And I know this is old news because you know last week is old news in the tech industry But just one release is an example if you focus on that five milliseconds of latency target for the go-router That one release improved over three times But more importantly every time that routing project team does a release They run the same benchmark and release only if they improve or stay the same Now I've mentioned a bit about how we bring together a number of different upstreams But I really want to land to this point with everyone when you're talking about the cloud foundry collection of platforms We harvest innovation from throughout the entire open-source ecosystem That includes projects like OCI where I talked about Run-C and we also collaborate with them It also includes things like the container networking interface that's happening at CNCF And I'm sure they have a logo for it that I didn't didn't put in here That's key to our container networking project, which is gonna will allow us It actually does already today allow us to make it easy for a developer to let one microservice communicate with another That includes things like open tracing and now kubernetes with the cloud foundry container runtime. These are all upstream projects for us We think of them as as part of our ecosystem And then we have the open service broker API which spun out of cloud foundry And we embrace the other platforms and found ways to let them govern it along with us So going back to this command line tool, we're gonna we're gonna dig into the developer experience a little bit first It's kind of in use right it's seeing about 200,000 downloads a month So a lot of people enjoy it a lot of people know it But there's some things that we can do with it that extend that basic CF push experience And the plug-in model is neat How many of you have already toyed with CF local? If you haven't you should So CF local is a project that was started by our lead for the build packs project in a spare time And it allows a developer to install this plug-in And now it can work locally on your laptop in a way that behaves like cloud foundry You can push and pull applications out of a live cloud foundry environment You can also have services stubbed out for you including SSH tunneling back to the cloud foundry environment So you can use the live service. It's really neat It starts to solve the some of the problem of how do you get a better flow as a developer in your local environment and interact with the larger system I'm also really happy to say that as of today It is our newest project at the cloud foundry foundation was accepted into incubation. So congratulations to Stephen and And I highly suggest that if you're looking for a way to get started Contributing to the cloud foundry community. That's a great project for you to dig into so go take a look at it You can check it out on the cloud foundry developer mailing list. You'll see some information about it there Alright now we're gonna start inviting guests up here