 Hello, hello everyone. My name is Steven Augustus and I am one of your co-chairs for KubeCon Cloud NativeCon and A Virtual. I'm here to talk to you about the Kubernetes project and we're going to do some project updates. So let's jump into it. Now the Kubernetes project is comprised of people and we believe in and we care deeply for the people that work on this project day to day. I think it would be impossible to talk about what we did for the year without talking about the 2020 of it all. Now our response initially to COVID, to dealing with kind of shifting, for a lot of people shifting the way they worked, shifting the way they interacted with people and moving towards more virtual content, moving towards less meetings when possible, being more accommodating about time zones, about families. So hat tip to everyone in the project that really is involved, sub-project owners, CIG chairs and technical leads, committee members who were incredibly present and conscious about how people are kind of coping with everything that's going on in the world. And to that you may be familiar with the Kubernetes.io website and we put up a banner on the website to clearly disclaim that racism is unacceptable, it's not something that we tolerate in the project. We believe deeply in our code of conduct and enforcing it to protect the members of this project. So again hat tip to all of the folks that actually worked on applying the ability to give our website banners, the steering committee for working with me on the messaging and delivering that and holding the line. I think that it's very easy for statements that can be deemed to be political to attract trolls and we had our fair share of that. So again hat tip to everyone involved, code of conduct, committee, steering committee, contributor experience for taking on that burden, for feeling it necessary and important to speak about something that's not a political issue, something that is a human issue. So the chairs and technical leads, we recently spun up, it's not recently anymore, it's been quite some time now, spun up chair and technical lead meetings. So giving an opportunity for all of our leadership across the project to sit down, chat in a safe space to exchange ideas without any kind of the blameless retrospectives and having that safe space to create ideas that you may not feel comfortable sharing publicly. Now we also started the annual report process, so the steering committee kicked that off. The annual reports essentially starting with the working groups, having annual check-ins for each of these governance groups, giving us an opportunity to get a better feedback loop between the groups that exist in our community and the wider community. It's very easy to kind of operate in a vacuum if you don't have the chance to speak about all the accomplishments that you've been doing and also spread that out to the community. So great work there. All of the moderators again going back into just handling all of the various properties that we own across Twitter, across the website, across discuss, hat tip to everyone, YouTube, Zoom for making everything that we do safe to do and welcoming. Now speaking of Twitter, we've added the Kate's contributors Twitter handle, which is handled by contributor experience and the marketing sub-project of contributor experience. So very awesome to see us being able to publish updates about the community more frequently to the wider internet. Now the triage cap which popped up, now we have made a lot of improvements in how we kind of decreased the burden for you to maintain your areas. And I think part of it was introducing this triage cap, something that we discussed for quite some time to get some of the finer details worked out and apply the automation to the process. So hat tip to everyone that was involved there across contributor experience as well as the enhancements sub-teams and sub-project of CIG architecture. The ingress enhancement went GA, super exciting, long-standing enhancement that has been in beta and it is one of our earlier enhancements. So great to see the work around delivering that to general availability. From the GitHub management side, the GitHub administration management team has been hard at work deprecating the Kubernetes incubator org, all of the projects that are involved in that org, some of them that may have been, may no longer be maintained. We built something bigger and better and it lives somewhere else now, so kind of wrangling all of that information and kind of bringing us to the sunset of the incubator org. Now for some CIG-specific updates, we have CIG usability. CIG usability has been driving a user research study that has gotten some really great data to crunch on and that will be part of their CIG update during the conference. So hat tip to them for one forming over the last year as well as all of the work that they have done to better understand the people who consume Kubernetes day-to-day. From CIG multi-cluster, the multi-cluster service APIs are in progress. They're currently alpha. They represent some solid progress towards normalizing multi-cluster deployments and making the next level of Kubernetes operations more manageable. That's definitely something that we consider with having all of these disparate environments. So hat tip to CIG multi-cluster. From the storage side, the container object storage interface was released for both block and file, CATE storage being able to build a similar interface for object storage is also coming. PSE is inbound for that so we should see that soon. Generic ephemeral volumes were progressed across the last few cycles. CSI support for Windows, which is a huge step forward for Windows support on Kubernetes overall. The volume snapshot feature is also progressed. So moving into CIG docs, CIG docs did an awesome job on the website migration, more modern theme, easier to maintain for their contributors. And on the architecture side, the production readiness sub-project as well as the PRR reviews as part of CEPs are now making their way into the release cycle. From the CIG release side, we've been working on tooling to make our lives easier, to make your lives easier, to make it easier to release Kubernetes overall, to make it safer to release Kubernetes, as well as the working group CATE's infra who's been hard at work. One, you'll hear more about the CATEs.gcr.io cut over from Google infrastructure to community infrastructure during the conference. You'll hear more about the image promotion process, how we're handling artifacts moving forward as we now own those artifacts in community infrastructure. And then finally, the working group naming was formed. This ties back into the thought of making sure that this project is inclusive and being thoughtful about the language that we use across both our code bases and our content overall. So stay tuned for more details on that later in the conference and as well as a community meeting from a new initiative that's happening on kind of the wider community across LF, CNCF, standards bodies, different companies. So stay tuned for that. Thanks everyone, later.