Kubernetes Community, 15 Oct 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Community Meeting 20201015

Description

The Kubernetes community meeting is intended to provide a holistic overview of community activities, critical release information, and governance updates. It also provides a forum for discussion of project-level concerns that might need a wider audience than a single special interest group (SIG).

0:00 Welcome
1:40 Release updates
8:33 SIG Instrumentation update
18:10 Steering committee update
26:04 SIG Storage update
36:26 SIG Service-Catalog update
38:44 Open discussion & Shout-outs

See this page for more information! https://github.com/kubernetes/community/blob/master/events/community-meeting.md

Like what you see here? Continue the conversation on https://discuss.kubernetes.io

A

Hello, everyone and welcome to the kubernetes, the october kubernetes community meeting. My name is dan pop and I'm your I'm the honor and privilege to be your host today for the kubernetes community meeting um today, where agenda is we're going to be speaking to uh the various sigs uh as well as, but first let me just shout out to our uh our notetaker was cody cruddington.

A

The first people that will be speaking to us will be from the sig instrumentation team. Then we'll have the steering committee we'll have some release updates and then we'll also talk to the various upstate uh for the folks in sig storage, as well as service catalog, open discussions, announcements as well as our shout outs.

A

So with that I'll hand it over to our first speaker, who's going to be from sig administration. uh Excuse me: sig instrumentation, it's han kang, take it away han.

A

Looks like han hasn't joined as of.

A

Yet all righty.

A

So in in lieu of that, maybe we can skip over to- I guess the the release team at this point or okay, george. Are you good with that all right? No problem, all right, so we are going to hand it over to uh mr nabarun paul for him to talk about the release. Details go ahead. Take it right now, baron hey.

B

uh Thanks dan for uh hosting the meeting today and thanks cody for taking the notes uh so I'll give the 1.20 release updates on behalf of the release team.

B

So, in terms of timeline, we are in week five of the release and we are almost halfway through yeah and code. Freeze is on november 12th and test freeze being on november. 23Rd test race is a new event in this release.

B

You can read more about that in the meeting notes. I have put a link to that.

B

Also docs pr should be ready to be reviewed by the same day, which is november 23rd, and they should be merged by november 30th, which is the dox freeze deadline and we plan to ship out kubernetes v 1.20.0 on december 8th, uh also just a small note. We will be having a small short break in november due to kubecon. uh Everyone will be busy in preparations uh going ahead. uh We have a new uh meeting conducted specifically for the europe plus epec region.

B

uh We had the first meeting this week uh and we plan to like develop it more as we go through and learn from the experiences the meeting happens at 12 noon. Utc 5 30 ist or 5 a.m. Pacific time feel free to join in. If you want to tune into the conversation coming to release cuts, uh a patch release of kubernetes 1.19 1.19.3 was released yesterday and there was some little snag in 1.17 and 1.18 and they're in progress and going to be released really soon.

B

uh Coming to the current uh release, uh 1.20.0 alpha 2 was released on october 13th.

C

Which was, I guess, tuesday,.

B

Two days back two days back and alpha three is planned to be cut next tuesday, which is, I think, 20th of october. You can find it in the timeline itself going forward. uh We had a notable event last week, which was the enhancements freeze.

B

uh Basically, right now we are tracking 56 enhancements out of which uh 23 are graduating, as alpha 17 enhancements are graduating, as beta and 16 enhancements are graduating as stable. The exceptions process is still going on. We had five exceptions raised as of today all of those are approved and they are being tracked as part of the release uh coming to the shadow program, uh the shadow bro, the shadow orientation is complete and we have 29 shadows this release cycle.

B

I want to thank all people all applicants for the shadow program and, like we look forward to see you in the future teams, as well as you learn and grow, and just a plug to for sick release. uh We are always welcoming new contributors uh feel free to hop into the sig lease channel on kubernetes slack. uh We are always there with that. uh The release updates are done. I will hand it over to stephen for a short update on uh the kubernetes kubernetes release. Cadence uh stephen. Do you want to take it over.

D

Hey everyone how's it going uh um so yeah. So during the 119 release cycle, we got um the. As you may know, the 119 release cycle was an extended extremely extended cycle for uh for the year um and we got a lot of feedback, uh whether it be via a direct message or um twitter threads uh emails. Things like that um about whether or not the kubernetes release the kubernetes kubernetes minor release.

D

Cadence uh would be uh three releases for the year going forward um and I think that it's time that we it's been quite a bit of feedback, so I think that it's time that we discuss this in a more official manner, this is something that affects the entire community. This affects not just the sig leads the contributors reviewers approvers, but also the consumers, the downstream consumers, both as uh end users as well as integrators for the project. So it's it's. It's really important that we get as much feedback as possible uh for uh this consideration.

D

um If you are, if you care about this, we've opened an issue in the sig release, repo that has some details, also some links to previous twitter threads. I did an extremely scientific poll on twitter and about 709 people uh voted on that poll, uh mentioning that they would love to see three releases for the year. So that's one of the options that we're considering, but there are lots of other options to potentially consider. I think that's the one that is closest to what we're already doing today.

D

um So I think that having some additional time throughout the uh throughout the year to in between cycles gives us an opportunity to uh one minimize churn for end users uh to uh minimize the amount of uh effort that it takes for us to spin up a release team. There are about uh 40 people on a release team that we have to train, recruit and and uh retain across cycles um that we have to consider. There's also the release management work.

D

The work across ci to maintain these branches across the the in support cycles for the minor releases, um so lots of things to consider as well as uh deprecation cycles, the uh progression of enhancements through the various alpha beta and ga stages.

D

So again, if you have feedback on this effort, please let us know: please try to direct as much of your feedback as possible into the issue, because that's kind of where we're going to be aggregating all the opinions um and yeah. If you have any questions, let us know.

A

All righty is that, are we all set from the uh the release team alrighty? Next? Next up we have uh from instrumentation, we have han kang from sig instrumentation.

E

Awesome cool hi, hi everyone, I'm han, uh I am the official representative for sig instrumentation. um I am one of the two chairs, um along with elena hashem, so uh for those of you who are unaware about rsig uh a little bit about us. uh Sig instrumentation is a horizontal sig. uh We're responsible for the infrastructure and best practices for observing kubernetes clusters and kubernetes is pretty complex.

E

It has a lot of components, a lot of binaries and each of these have to be instrumented and sig. Instrumentation basically provides the mechanisms to systematize these observability tools so that we have a consistent and comprehensive story.

E

E

We like to think of instrumentation as falling under three distinct pillars: metrics logs and tracing. So very briefly. Metrics are time series data which are emitted by the individual kubernetes components. These can be scraped and stored in a storage backend like prometheus or stackdriver logs, which people are probably more familiar with in some shape or form. These are immutable time step records of events.

E

These can be in plain text or structured or binary format in kubernetes. It's mostly plain text, but we have some initiatives to move towards structured logging and we're going to get that into go into that in a little bit.

F

uh Are you sharing anything? Are you showing any slides sorry.

A

Yeah, I was hoping that I didn't want to interrupt you there, but yeah. If you could show your side that'd, be.

E

D

I don't do that.

E

A

Not sure how to do this, all right, would you like me to share, and, and uh I can do that that would be great.

E

A

E

All seeing this, oh yeah, that's great!

E

A

No problem, just let me know when to advance.

E

uh Awesome so yeah, uh the last pillar of observability is uh distributed tracing, so this one is a more sophisticated and nuanced pillar of observability.

E

We are really excited about what we do in this space, but uh imagine since uh you were to modify a replica set three raffles or four replicas. uh Basically, what tracing would be to do is just all of the requests and all the things like a kubernetes cluster did up. Until that point- and let's say uh fourth pod, a replica set was created uh to be able to chase all the things that occurred uh that led up to this are not being created, so that should be rather helping you debug a misbehaving.

E

Cluster uh next slide, uh yeah, so statuses of caps. uh So, uh since the last community update meeting uh the event, the events api has now graduated. uh This is the v2 events api. This is um a mechanism which kubernetes has provided for.

E

Probably at least five over five versions, um but um it is a variant of structured logs um and if you want to read more about it, uh can there's a link to the cap in the slides um in beta. We have the metric stability framework. uh Recently, we overhauled a bunch of metrics in uh open source kubernetes.

E

um This was backwards incompatible. uh We now have a framework in place to prevent uh slo type metrics from from breaking so um that is now in beta.

E

Structured logging, uh we are also we have an effort for structured logging, which.

E

Basically, moves logs from platinum text into a more structured form. This is beneficial if you want to query against logs for um for for data.

E

This recently went through production readiness review, and so, if you want to read about that, that's also linked. We have a couple things in the pipeline. uh The road alpha as I like to call it one we have dynamic cardinality enforcement for metrics metrics can basically overwhelm kubernetes if they misbehave.

E

This has been a painful process for us historically, since we basically need to make code changes every time this happens.

E

This cap allows us to uh to turn off problematic metrics uh without actually making enough stream change. uh Distributed. Tracing was just uh approved for alpha, so uh we are uh pretty excited about making progress on that this, uh this release cycle. We have uh two caps for log sanitization.

E

So basically, um uh this is a cross-sig effort between auth and instrumentation. um We want to prevent.

E

Sensitive information from being linked leaked in logs, and uh this is a multi-pronged approach, um so the first problem would be to sanitize logs dynamically, and uh the second approach would be to sanitize things before runtime and that would be done through static analysis. If you are interested in reading about those or contributing the links are also provided there.

E

uh Next slide, please, okay, so plans for upcoming cycles were.

A

You have four minutes, I'm sorry to interrupt. You just wanna make sure you know we have four minutes. Okay, thanks yeah.

E

Yeah, so uh the plans for upcoming cycles uh we're moving metric stability to ga uh cube state metrics release releases v2s. uh Soon we have an alpha version currently released. So if uh people who like cubesat metrics, please try this alpha v2 version, uh we need feedback on things that work and things that don't work.

E

Structured log into beta is slated uh for the next uh two releases and we are working on the alpha implementations of the catch that we just mentioned. uh We have also started working on a few tools that will help people debug kubernetes clusters. One of these is a cli that allows you to interact with prometheus endpoints called from queue and another tool which exports systemd logs.

E

That david ashwold has worked on, um and so, if we are happy to accept contributors and and feedback on all of these things um next slide. Please.

E

uh Yeah, so if you want to contribute to instrumentation, we have a lot of things going on we're happy to have new contributors and help keep state. Metrics is seeking new contributors. Lilly would love uh extra hands. Anyone who's interested in this stuff, um especially with v2 rolling out uh metric server, is seeking new contributors, as is structured logging, for both of those you can contact.

E

Merrick promq is also seeking new contributors, and you can contact any one of us down here next slide and where you can find us, uh you can reach me on slack or elena hashman. uh Our two tech leads uh frederick branchack and david ashfold. uh These are they're, github and slack handles.

E

We also have a slack channel and a mailing list which are linked here, so uh that's it for the instrumentation style of things.

A

Thank you. So much hey! You know, I'm sorry. I kind of skipped over this now that we have everybody in the channel and do some housekeeping real quick before we jump over to paris real quick and again this is a live stream. So this is a community meetings being live stream, so it's posted publicly on youtube. So it's going to be, please be mindful of what you say is being recorded.

A

um We have a code of con that so obviously be excellent to each other as we are, and so we're amazing uh community right and also make sure you're muting. uh If you aren't speaking with that, I'm going to hand it over to the incomparable um paris pittman.

C

The incomparable hi everyone: how are you I'm paris uh for those who don't know me? I sit on the kubernetes steering committee. uh I am gonna share my screen. If that's okay pop for one second hold, um let me make sure I'm sharing my right screen, yeah. Okay, all right, so um I wanted to at least go through before I started. um Some folks on the line might not be familiar with the steering committee, so I at least wanted to say this is where we live.

C

This is our uh this is our github on reap uh get our github repo. So if you ever need anything from us, whether it's uh to talk to us file an issue or correct something help us correct something, be a pull request. This is where we live, so you can find out more about us who sits on us and how you could uh actually run for uh run for syrian committee.

C

Next year we have elections every year, which actually brings me into one of my first um one of my first topics, which is we had an election thanks so much to everyone that ran congratulations to bob jordan and welcome back dims. uh We had so many people that ran every year. We always think wow what an awesome community we have that uh folks are stepping up into these chalk water and carry wood rolls.

C

um These are not your standard contributor type roles, so it's very heartwarming uh to see that kind of to see these folks rise to the occasion uh and we're just so blessed to have these folks a part of our community.

C

I did want to take a minute to uh and also say thank you to all of our contributors and community across the globe. These are trying times for everyone uh and it seems, like our community has really banded together. We've had nothing but kindness and camaraderie over the last few months, uh as we all work uh and focus on. um You know trying to get ourselves out of this this trying time together.

C

So thanks for everyone for everyone being awesome, really we just wanted to say that, because we're still just so grateful that we have the community that we do and you all are in it. So thanks so much um so there's actually two elections uh that we had this year.

C

uh The second one was the code of conduct committee election, congratulations to karen chu, tim pepper and celeste hogan there um and then also a quick thanks to a quick thanks to jace and carolyn who um who rolled off this year and for their service for the code of conduct committee, um some new things that were on our plate this year. So new things uh we did install a unconscious bias, train for our chairs tech leads and working group.

C

Organizers, uh we've had an awesome success rate we've had almost all of our chairs and tech leads and working group organizers. Take that unconscious bias, training we're talking about over 75 people. So it's definitely not just a small group of folks that have done that again. It's a true testament to our community's principles and values.

C

Other things that we've been doing is working out and working through a very new process for us, which is the annual report process for community groups.

C

If folks are hearing that for the first time, that's just a way for us to check in with community groups, community groups being special interest groups, working groups uh and uh and other committees, and things like that.

C

Other bodies of folks that are working on upstream uh and these uh reports are going to really talk about the health of those groups uh and give also end users kind of a uh just a like a bird's eye view if you will into what's been going on and and what are some good uh good things that we should highlight with accolades uh and what are some challenges that the group has that we should bubble up.

C

So we started with our working groups this year next year, we're going to move on to our sigs in the beginning of the year. So this is also a quick uh weight. uh Six for coming uh kind of thing uh steering committee also has liaisons now, which is how we're carrying out these uh annual reports. The liaisons are really just to help us as we grow. Our community is even larger. Now we're talking about over. I think 37 community groups um and there's only seven of us.

C

So now we have liaisons where we've divided and conquered, uh and we've matched up syrian committee members with some of those folks in those community groups, so that we can help out with annual reports and pretty much anything. That comes up throughout the rest of the of the year, um that would be governance related or anything that we could help with funding, etc.

C

um Speaking of working groups there's a new one. That's just formed uh that is the working group for reliability check them out if y'all haven't they're working out their charter- and I know their uh their first meeting and things like that. So if you are looking for ways to get involved, that could be a good group, uh especially if you're coming from uh maybe large end users um and then speaking of other working groups. We had a working group. uh Security audit recently moved to become a special interest group.

C

uh Ian coldwater and tabby sable are going to be chairing that group. So if anybody uh that's another contribution opportunity, if you're looking for ways to get involved or if you are currently involved with a project uh and care about security uh and any other security related kubernetes matters that would be dealt with upstream, please feel free to reach out to that group on slack or on their mailing list, they're trying to shape their group right now um and then, of course, we're still doing our fun game thing.

C

So if there's any groups out there that need any kind of funding, uh testing credits, cloud credits or anything like that, we do take those requests at that repository right there under our funding repository.

C

So what's on the schedule for us right now, we are talking about term limits for ourselves right now. We don't have any, um should we have some, so we have a p our draft pr in for what that would look like. uh We have to discuss this with the new members now uh and then we're also untangling the various uses of the term member, because number can be conflicting depending on what that means. Here, it could mean github, org membership. It could mean voting right membership.

C

uh It can mean a couple different things, so we're working on untangling, some of the language that we use in our governance stocks. Our next public meeting is november, 2nd. So if you're a contributor that has any kind of issues that you would like to bubble up or even just stuff that you'd like to say or celebrate, please come visit us come hang out. uh We also have a slack channel.

G

C

List uh and like I showed you before with the with the github repo, we also live in github too, so you can reach out to us there, but we've had a lot again. Thank you so much to the community, you mean so much to us. um I mean I think we just hit like 50 000 contributors recently, if I can, if I can recall it's humongous, uh probably one of the largest in the world, so thank you so much. Everyone really appreciate it.

A

Thank you so much paris again. It's amazing the community is contributing it's phenomenal. So um thank you so now over to our next speaker, which is um xin yang zing yang from the sig storage uh team group,.

G

Can you please share the slides for me, it'll be easier.

A

Yeah no problem hold on one sec thanks.

A

A

Y'all, seeing this okay.

G

Yeah, okay, right, hello, everyone, my name is xin yang, I'm a co-chair of kubernetes uh six storage, so I will be giving an update today next slide, please! So! First I will talk about what we have done in the 1.19 release.

G

There were a few new, a few features that went beta in 1.19, both azure disk and vbsm. Migration was promoted to beta in window 19. This is part of an effort to move entry cloud provider plugins to auto 3 seaside drivers.

G

The next one is csi windows that was also promoted to beta system. Windows relies on a css proxy to perform privileged operations such as mund and format disks, because windows containers are not privileged.

G

The other feature that got promoted to beta with immutable secrets and config maps. This allows secrets and config maps to be read-only, and we also have both the voting. Expansion and volume snapshot features in beta in 19, but we made a lot of improvements forward extension. We added the offline extension support detection and for running snapshots. We added a validation. Web click to validate api objects, move the snapshot, apis and client library to a separate. Go package in 1019: we also introduced a few new other features.

G

uh We added a new feature um for csi storage capacity tracking. This has a new css 3d capacity. Api object with this csr drivers can report available capacities associated with node, topology and stored class through the get capacity csr function and coordinated scheduler will make placement decisions based on this information.

G

This feature is a stepping stone for sporting, dynamic provisioning for local volumes and the next one is the generic ethmoid ethmoidal volume. So this allows an ethmoidal volume to be provided by any storage driver that supports dynamic provisioning. So this means all features supported by pvc are also supported by this generic ethanol volume.

G

This includes this new csi storage capacity, tracking feature and snapshots and restore and volume resizing.

G

The next new feature introduced in 1.19 is csi voting health. The suture enables css drivers to share abnormal volume conditions from the underlying storage system with kubernetes so that they can be reported as events on pvcs or pots. This feature serves as a stabbing stone towards problematic detection and correction of volume. Health issues by kubernetes and the next feature is the csi driver policy for fs group.

G

So this allows csx drivers to specify whether they support morning ownership and permission modifications to the next slide. Please.

G

So now I'm talking about our plans for upcoming cycles, including 1.20 and beyond. We continue to work on csi world expansion trying to bring it to ga in 1.21 or later we plan to deprecate the online offline world expansion plug-in capability in a future csi stack release online offline, one extension will still be supported. It's just this particular plugin capability will be removed from the seaside spec and uh the next one is avoiding snapshot. We are trying to bring it to ga 1.20 release.

G

We are working on tightening the api validation, adding metric support in snapshot, controller and adding missing eq tests.

G

The next one is non-recursive volume ownership feature that is the targeting beta in 1.20 release. This allows volume, ownership and permission change to be skipped during month.

G

Next, one is the csr driver policy for fs group, so we are targeting beta in 1.20 release. This was just introduced as another feature in 1.19 and for azure files is an aggregation, we're also targeting data in 1.20 release next slide. Please.

G

uh Under 201.20, we also plan to introduce the ability to pass part service account token to csi. This feature proposes a way to get service account token for the parts that the csr drivers are mounting volumes for.

G

We also have quite a few features that are in design and the prototyping phase. The first one is recovery from water expansion failure, so this allows recovery from one expansion failure caused by insufficient quota. This feature right now, is still in design discussions.

G

uh Next, one is non-recursive secret, secure linux. This proposes a way to speed up container startup by mounting volumes with the correct, simple linux label. Instead of changing each file on volumes recursively, which could take a long time, it also allows the csr drivers to opt in to this feature. This feature is also still under design discussions.

G

Next, one is the saf csi migration that is also been designed. Next, one is volume groups. This proposes to introduce a newborn group, crd that puts multiple volumes together and a new group snapshot crd that supports taking a snapshot of all volumes in a group to ensure right order, consistency.

G

We are also looking at how to use this volume group concept to support fader domain spreading, for example, how to place volumes in the same group across different disks in the same storage system.

G

Next one is generic data populator that allows a pvc to be provisioned from an external data source, not just a one snapshot or another pvc, but it could be a object, store, a github repo, an image or something else and there's already a feature gate and alpha feature kit that was introduced in 1.18 release and design and poc are ongoing to have a external data populating implementation in the 1.20 release.

G

The current proposal is to introduce a validation web hook to make sure that the external data source used by the pvc is a supported, valid source and the last one on this slide is the container object, storage interface of cozy. This allows an object that keeps should be provisioned and used by a pod, so there have been weekly design meetings for this project. This now is a sub project. Under six storage reports are created under kubernetes six for prototyping next page, please.

G

So now I'm going to talk about classic working groups and projects. We have a data protection brain group, which is a collaboration between sig storage and seagaps. In this working group, we have been discussing a number of features, including volume groups, generic, then populator, and so on that I just mentioned earlier.

G

One feature the working group has been working on is how to require an application before taking snapshot and unquiets. Afterwards we have a proposal called containing notifier. We are working on that proposal with the seeker node. There is a cap that is being reviewed. Currently, we also have a few features that we co-only seek apps. The first one is how to support one expansion for safe sets.

G

The second one is trying to figure out how to clean up pvcs used by the staple set when the staple set is being deleted or scaled down.

G

We also work with six scheduling on the prioritization on volume capacity future, and this one is targeting by far in 1.20 release next slide. Please.

G

So here are some general information about the sick, uh sad ali and myself are co-chairs of seek storage, nishan yan are tech leads, and we also have this uh home page for six storage. That has a lot of information about it. We have a slack channel and we have main list. We also have bi-weekly meetings.

G

My next meeting happens next thursday at 9am pacific time. So join us. If you are interested. Thank you. That's so funny.

A

Thank you so much zenyaka great great stuff, great thanks for sharing from sig storage. um Next up we have mr jonathan birkin from sig service. Catalog. Are you out there jonathan.

H

uh Yeah, I don't know there, you go I'll, see you, I don't have any slides. Our updates are pretty brief. um So for those of you who don't know sync service catalog is an extension project for kubernetes.

H

uh It's an implementation of the open service broker api, which is a specification to allow cloud platforms like kubernetes to talk to service brokers, which are external servers that implement the api to offer some sort of services like uh relational databases or such to offer them up in a way that can be provisioned through.

H

uh You know, native tooling, within the platform itself uh to provision those resources on the back end and we've been pretty much in maintenance mode for the past six months, just kind of keeping up with uh kubernetes updates and updates to the the osb api itself. We haven't really had any new major features that people have wanted or that we've been pushing for um other than that uh we've had to deal with the helm, chart kerfuffle uh the home chart repositories are going away and it was something that we depended on us.

H

We've had to come up with our own solution, which we've implemented as pages that we're going to maintain ourselves off of our main repository and aside from that, the only real announcement I have is that one of our co-chairs, um such stock from sap, is stepping down he's, moving on to new opportunities, uh still sort of like the open source cloud platform space, but uh not directly related to his previous role. So he's stepping down and we're nominating uh constantine seminole. I think, is here from vmware to be his replacement and.

D

Other than that.

H

We don't really have any big plans for the immediate future. uh Pretty much gonna be more of the same. We've got some some updates from the spec version coming out that we're gonna have to get in, uh but we don't really have any any big plans for the immediate future.

A

Excellent. Thank you jonathan for the update. We appreciate it. Is there any open um discussions that anyone wants to bring up. Let me open up the floor.

D

uh Just really briefly, I wanted to base uh king off of paris's update. I just wanted to give a shout out to the release team leads, jeremy and uh and his team, for uh it wasn't a requirement, but they made it a requirement to do inclusive training for the team moving forward. So that's it to you yeah. That's it.

A

Anyone else, besides our esteemed colleague stephen augustus,.

A

All right, I got george smith's laughing, that's a good thing, all right. uh Any open announcements.

A

um All righty well we're gonna have, uh I guess, we're gonna call that we're gonna have a next community meeting um and we'll talk about the. I guess the dates are still somewhat in flux, but uh you know that those are something there and, I think we'll have. uh I think cody cartington will be the co-host for that. So just a heads up on the next community meeting.

A

Next up, we have um shout outs, so we have five active, shout outs that I kind of want to call out here. So let me just share this out. You all seeing my screen. Okay, so we have uh robert kitely and I'm sorry kitey.

A

If I'm not pronouncing that correctly, uh give me a shout out to laurie apple, shout out to laurie apple uh and katie, robert heidi, um for just again the shadows to managing the whole collection of cici signal, experience and document formula, all the work we do in goal-oriented manner, which is awesome and also uh it was a response from uh from lori to rob keith for a fantastic work on onboarding for uh for the the process and creating mechanisms for automating. So again, shout out to you both great mutual shout out again.

A

That's what I love about this community is everybody is, you know, just is always complementing each other and we're always you know fighting for each other. Just a fantastic thing. I give a shout out to gfe. You know during the um uh the steering committee updates.

A

uh Just stepping up last minute to be able to do streaming was fantastic, a lot of us who couldn't either join or join live, and you know have really you know he stepped on a table so fantastic for that um it looks like 52 tracked enhancements that mr bobby tables again congrats to him for his nomination as well, for the steering committee uh for oe kiki uh for wrangling enhancements, beautiful awesome, uh mr bobby tables also again shout out to jay burkus, jace and ehor for serving the community for running the 2020..

A

Let's all give them a hand, obviously right so for doing a fantastic job um yeah. So that is pretty much it. um I want one more yeah one more go ahead. The esteemed colleague.

D

Against this has the floor.

A

D

Mr uh mister, but wait there's more um so uh community, I'm going to be doing the uh kubecon cloud native con and a virtual keynotes on kubernetes project updates. I sent an email to the leads and steering requesting some feedback. If there are things in your governance group that you would like, potentially featured on the keynote stage for kubecon, please send me an email with some of those points by the end of the day, so we can roll those in thanks.

A

Thank you, mr augustus. Is there any other announcements or any wait, there's mores for anybody else.

A

All righty um yeah, I would ask you all to take some time to update the agenda or you know comment before we send it um before I kind of give you some time back on your day. I just want to thank you all again. I I said this on twitter and I'll say it here. We are kubernetes everybody. That's in this room, that's contributing is phenomenal, the best in class- and I I am so honored and privileged to be hosting this today, and I thank you all for all of your.

A

D

D

Great job today, pop.

H

Good job thanks, everyone.

A

Bye, you did amazing.