Cloud Native Computing Foundation KubeCon + CloudNativeCon North America 2020 - Virtual, 4 Dec 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Keynote: Kubernetes Project Update - Stephen Augustus, KubeCon + CloudNativeCon NA 2020 Co-Chair

Description

Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2021 Virtual from May 4–7, 2021. Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.

Keynote: Kubernetes Project Update - Stephen Augustus, KubeCon + CloudNativeCon North America 2020 Co-Chair & Senior Open Source Engineer - Tanzu Kubernetes Grid Core, VMware

https://sched.co/eoEM

A

Hello, hello, everyone, my name is stephen 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 we believe in, and we care deeply for the people that work on this project day-to-day.

A

I think it would be impossible to talk about what we did for the year without talking about uh the the 2020 of it all and our response uh initially to to covid um to to dealing with uh kind of shifting for for a lot of people shifting the way they worked. Shifting the way they interacted with people and uh moving towards uh more uh virtual content, moving towards less meetings when possible, being more accommodating about time zones about families, so hot tip to everyone in the project that that really is involved.

A

The sub project owners, sig chairs and technical leads uh committee members who were incredibly uh present and conscious about uh how people are kind of coping with everything that's going on in the world, and uh to that you may be uh familiar with the kubernetes dot io website and uh we put up a we put up a banner on the website uh to to clearly disclaim that uh racism is unacceptable racism. It's not something that we tolerate in the project.

A

uh We believe deeply in our code of conduct and enforcing it to protect uh the members of of this project so again, hat tip to all of the folks that actually worked on uh applying uh the ability to to give our website banners the steering committee for um working uh with me on the messaging and uh and delivering that and and holding holding the line.

A

I think that you know it's very it's very easy for um statements uh that can be deemed to be political um to attract trolls, and we had our fair share of that. So again, hat tip to uh to everyone involved code of conduct committee steering committee uh contributor experience um for taking on that burden for for for feeling um feeling it necessary and important to speak about uh something: that's not a political issue, something that is a human issue, so the chairs and technical leads.

A

We recently spun up it's not recently anymore. It's been. 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 uh to sit down chat in in a in a safe space um to to exchange ideas without uh any you know, kind of the the blameless retrospectives and and the um and uh you know having having that safe space to to uh uh create ideas um that you may not feel uh comfortable sharing publicly.

A

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 uh annual check-ins for each of these governance groups, giving us an opportunity to get a better feedback loop um between the the the groups that exist in our community and the wider community. It's very easy to kind of operate in a in a vacuum.

A

um If you are, uh if you don't have uh you know the chance to to to speak about all the the accomplishments that you've been doing and and also um and spread that out to to the community, so so great great work there?

A

um All of the all the moderators again going back into uh just handling um handling, all of the the various uh all the various properties that we own across uh twitter across the the website across discuss, um hat tip to everyone, uh youtube zoom uh for making uh everything that we do uh safe to do, and and and welcoming.

A

Now speaking of twitter, we've added the uh kate's contributors uh twitter handle, um which is handled by uh by contributor experience and uh in the uh the marketing subproject of contributor experience, so very awesome to see us being able to publish uh updates about the community more frequently uh to wider uh the wider internet.

A

um Now the uh the triage kept which popped up now, we have, uh you know, made a lot of improvements in how we kind of decrease the burden uh for you to maintain your areas right- and I think part of it is- was introducing this.

A

This triage cap, something that we discussed for for quite some time to get some of the finer details, worked out and apply the automation to to the process so hot tip to uh everyone that was involved there across uh contributor experience, as well as uh as well as the the enhancements uh sub sub teams and uh sub of of sig architecture.

A

The ingress, uh the ingress uh enhancement, went ga super, exciting, uh long-standing enhancement that has been um has been in beta and, uh and it is one of our earlier enhancements um so great to see the work around delivering that to general availability from the github management side.

A

The github administration management team has been hard at work, deprecating, the the kubernetes incubator org, all the projects that are involved in that org, some of them that may have been made 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 the sunset of of the the incubator org now for some specific updates, we have uh sig usability. Sig usability has been driving a user research study.

A

That's been, uh that has gotten some really great uh data to crunch on and that will be part of their sig update uh during the conference, so hat tip to them uh 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 sig multi-cluster, uh the multi-cluster service apis are in progress they're currently alpha.

A

They represent some solid progress towards normalizing multi-cluster deployments and making the next level of kubernetes operations uh more manageable, and that's definitely you know, that's definitely something that we consider um with you know having all of these disparate environments. It's a hat tip to sig multi-cluster.

A

From the storage side, the container object, storage interface uh was released um for both block and file. uh Kate storage, uh being able to build a similar interface um for for object. Storage is also coming. Pse is is inbound for that, so we should see that soon generic ephemeral volumes uh were progressed across the last few cycles. Csi support for windows, which is huge, a huge step forward for windows, support on kubernetes. Overall, the volume snapshot feature is also progressed and yeah.

A

So you know moving into uh moving into sig docs sig docs did an awesome job on the website, migration, um more modern theme easier to maintain for their contributors and on the architecture side. The production, readiness subproject, as well as the prr reviews as part of caps, are now making their way into the release cycle.

A

From the sig release side, we've been working on uh 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 kate's infra, who has been hard at work.

A

One you'll hear more about the uh the kates.gcr.io cut over from google infrastructure to community infrastructure uh during the conference, um you'll hear more about the image promotion process, how we're handling artifacts moving forward, as we now uh own those artifacts in community infrastructure and then finally, the uh the working group uh naming was formed right this.

A

uh This kind of ties back into the the thought of making sure that this project is, is inclusive and being uh being thoughtful about the language that we use uh across both our our code bases and our and our and our content overall. So stay tuned for more details uh on that later in the conference and a uh as well as a uh community meeting from a new initiative, that's happening on kind of the wider uh community across lf cncf standards bodies, different companies, so stay tuned for that thanks. Everyone later.