 Hello, everyone, and welcome to day two of KubeCon Cloud NativeCon Open Source Summit China 2021. My name is Jasmine James, and I'm an engineering manager at Twitter and a KubeCon co-chair. I'm here to present to you today Kubernetes project updates. These updates might seem familiar. They're essentially a rerecord of the updates that Steven Augustus, head of Open Source at Cisco, and former KubeCon co-chair gave at our Los Angeles event in person in October. There are a few additions that I'll be also talking about today. So let's dive right in. First up, Code of Conduct Committee. The COC is a governance group, and here are some of the things that they've been working on. A project transparency report is a critical evidence point for this large community's numbers to understand the presence of a code of conduct is not simply a token or something hollow, but rather a representation of the project culture and that there is active accountability and restoration to ensure a safe space for all who collaborate within the project. What this means for end users is that their supply chain dependency on Kubernetes is a dependency on a project with foundational governance aspects which foster project health and sustainability. This decreases their business risk and depending on the project. Next, make sure you read the code of conduct and internalize it, and if you see behavior that is different than what the code of conduct says and contradicts it, speak up. This might be directly in the moment if that feels safe to you or to the SAG working group lead in your area to a steering committee representative or even in private through the conduct at kubernetes.io email address. As with the technical debt driven bugs and software engineering, the hardest conduct issues aren't typically ones where there's something done deliberately wrong, but rather ones where we allowed together a situation to grow into something larger. Shift left and start those conversations earlier before what might be just a simple communication grows into a negative pattern or establishes unprofessional culture. Also, as Steven mentioned in his address in October, thank you to Tasha and Ava who are now emeritus members and welcome Valerie and Navarone to the Code of Conduct Committee. All right, steering committee updates. Reiterating, read that transparency report. Also go and check out the annual reports for all groups within the kubernetes community. To see what they're up to, you can actually access it at the kubernetes community GitHub. Steven gave the update that the steering election was in progress in October. We're happy to announce that it's been completed and here are the results. Congratulations to the new steering committee members. Christoph Blecker from Red Hat, Steven Augustus from Cisco, Paris Pittman from Apple and Tim Pepper from VMware. Their two year term begins immediately and they are joined by continuing members of the everyone's front of us from VMware, Jordan Ligget from Google and also Bob Killen from Google. Thank you all so much for serving and doing this important work. SIG Security, this is a newer SIG and it works to improve the security of kubernetes project and the ecosystem as a whole by building bridges both internally and externally. It provides a safe space for community collaboration, knowledge sharing and learning and also raising security awareness. Horizontal initiatives include cross cutting documentation, tooling development and facilitation of a regular third party security audit. SIG Security is a community effort driven by people who show up and do the work. The sub projects have started with interest community members showing up with an idea, bringing other contributors to do the work, coming into their own as leaders and building that community and making it a space for others to grow. SIG Security is really proud of their updates to their sub projects. Our docs, the docs of the project has been improving the kubernetes documentation to help users run their cluster in safer ways. And it's also producing and hardening guide to raise adoption of practical security improvements which is really, really needed by the community. I'm super excited about that. The tooling sub project is helping kubernetes maintainer ship safer code by developing tooling and procedures to find and reduce common issues like vulnerable dependencies or data leakages. The audit sub project is making it easier for security and auditors to engage with that massive kubernetes code base and it's finding more opportunities to improve kubernetes for everyone. These are all great opportunities in sub projects to get involved. So please reach out to the SIG if you're interested. End users often have a lot of questions about hardening their clusters. So the sub SIG is very excited for them to get their hands on the docs hardening guide. This guide gives users practical advice that will increase their understanding about how to make their clusters more secure. SIG security has also collaborated with SIG auth to replace deprecated pod security policy with pod security admission which provides an easy built in way to ensure that dangerous pod features are only used when they're needed. Pod security policy was an important effort to a lot of users, but it was hard to use and maintain. And figuring out what would replace it took years of time and effort. So pod security admission gives PSP users a path forward and helps kubernetes be more secure in its default state. As I mentioned, SIG security is always looking for security minded contributors, including ones who are new to the kubernetes project. Bring your gifts ideas and help make kubernetes better. Next up, SIG release. SIG release has a roadmap and vision of what they would like to see happen in the project related to delivering kubernetes, which is very exciting. They've also introduced more release managers in artifact promotion chat with SIG release to get started pushing artifacts to a secure location. They've also started to look into securing the supply chain. SIG release is trying to lead the pack by working across the SPDX community and those that deliver S bonds. The salsa framework allows them to see where the artifacts are going and gives more insights. SIG release will be building out that framework over time. SIG storage. So SIG storage is responsible for ensuring that different types of file and block storage, whether it's ephemeral persistent are available wherever a container is scheduled, including provisioning, creating, attaching, mounting, unmounting, storage capacity management, influencing the schedule of containers based on storage and generic operations based on storage. CSI windows has moved to general availability in the 1.22 release. Windows is not currently support privileged containers yet. So to solve this problem, the CSI proxy enables CSI node plugins to be deployed as unprivileged pods to use a proxy to perform privileged storage operations on the node. This allows end users to use the CSI driver to prevent persistent volumes to use in their workloads. SIG storage always needs new contributors. So I will echo here again. Please reach out if you're interested in contributing. Working group API expression. So this group improves mechanisms to serve open API from Kubernetes API server and API's authoring and expressiveness to allow APIs to properly and programmatically describe their mechanisms. Server side apply and graduates to a GA and allows new paradigms for controller authors, making it easier to implement and actuate their intent. Server side apply helps users control. Users and controllers manage their resources via declarative configurations. It also allows them to create and or modify their objects declaratively simply by sending their fully specified intent. After being in beta for a couple of releases, server side apply is now generally available. Congrats. We are looking forward to the improvement of API documentation into practices. So if you are looking to contribute to documentation, you can reach out to this working group. All right, working group naming. Working group naming was dissolved because the initial objectives were achieved. They sought out to create a framework and process for the Kubernetes community to change language that was not inclusive. The goal was to change all of those names and it was done. So thank you to Steven and Celeste, who are the co-founders of this working group. Thank you. Thank you. Thank you. All right, working group Kubernetes infrastructure has transformed itself into a SIG. This is the first time that this has happened, as Steven mentioned in October. And the journey was started to convert the infrastructure owned by Google to community-owned infrastructure. They found that it was so important that it needed to be a SIG. So if you're looking to get involved in this project, please reach out to the Kubernetes Infrastructure SIG. The Product Security Committee is now the security response community. This is a name change. Thank you to those on the security response committee who participate in this on-call rotation and do a lot of work behind the scenes to keep things going. SIGDocs is a place where we need a lot of contributors. And it's a fantastic way to get started in the community and it's many folks' entry point into the community. We're looking for help. So please reach out if you're looking to write documentation or even contribute technical writers to any of the areas that you're leveraging from the Kubernetes project. Lastly, join us. The community repo here is the number one link. It offers an overview of governance groups and how to get started. The second link is a contributor-focused website. So if you want to know what it takes to get involved with contributing to Kubernetes, you can check that out. The last link is the production-level documentation managed by SIGDocs. So this is our end-user-consumed documentation that really everyone knows about. Check all of them out and see how you can contribute today and make Kubernetes even greater than it is right now. Thank you.