Kubernetes SIG Release, 1 Jun 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting for 20220601

Description

Kubernetes Release Team Meeting for 20220601

A

Think in one second.

B

This meeting is being recorded.

A

Hello everyone good morning, good evening good afternoon and welcome to our weekly release meeting um today. We are at week two uh first uh june 2022 and this meeting is under the sense of code of connect which could be boiled down to just please be nice to each other, and I've shared the uh link to the meeting notes in our zoom chat. Please feel free to unlock your attendees here and, let's move to um the open discussion.

A

So there is a link for the 1.25 retrospective dog. So if you have any topic you would like to discuss regarding our release process, please feel free to add the topics there and the things this week is still the beginning of the release.

A

I guess all the teams are still somehow going through the onboarding process and have the shadows on boarded and welcome to all the shadows um who joined the release new or um returned members and they'll use this meeting together with last meeting to welcome all the shadows. So when it comes to the team updates, please feel free to introduce yourself and.

A

um I guess that's all the open discussion topic. Let's move to the team updates enhancements.

C

Yeah we can hear you okay, um so our overall status is green. We have received a total of 27 keps. As of now uh the team has started tracking the kips. um As of today. We have tracked seven of them uh already and out of those seven, we have two alpha: uh zero beta, four going to stable and one deprecation.

C

um The shadow on boarding was done on may 27, and um I have added all the shadows to the releasing contact sheet and releasing document.

C

I have one question or maybe a point where I need help from the group, so there is a cap I have linked here uh for port security policy.

C

This skip is a very old uh issue uh and does not have a like. I don't know if whether to call it a gift, because uh there is no kept document merged into okay enhancements repo. For this there is a archive design proposal document.

C

um As of like, as per our process, we use a marshkep to track any milestone, any uh stages in a cab, so I have started a slack thread in uh release enhancements regarding like getting some gathering some suggestions on how to move ahead with this. Whether I should request the cap owner to migrate the design proposal to a kept document, or maybe since this is a removal and application, we can maybe go ahead with some exception.

C

Also another node. There is another kip. Let me there is port security submission. I think it's two five, seven, nine, that is a replacement for port security policy. So uh can we align these two caps together? I mean I'm open to suggestions how to go ahead with this particular game.

A

Yeah, thank you for the updates. um I guess this one is a little bit weird because they don't have the um currently released as their targeted, unstable release and that's why they already went to beta, um like maybe 10 releases uh ago, so I I'll just maybe reach out to seagulls.

A

This seems like this cap belongs to seagulls and reach out to the sick chairs to see if they have any suggestion, or they have any plan for this one and I'll I'll help always reach out to people on on slack. So we can discuss this one on slack to see like how the sig runner move forward on this one.

A

Does that sound? Okay, uh thanks, cece yeah I'll reach out to you yeah! Thank you for the update and, let's discuss on slack like offline and I'll get the um sig chairs involved. Yeah.

A

Thank you, and if there are any, like enhancement, shadows didn't get the chance to introduce them um last week and I'm wondering to want to do a self introduction now.

D

um Jeremy has his center yep.

A

E

I was just going to say: I think that this is probably a case putting my enhancements hat on, since this is such an old one and it's being deprecated and removed and replaced by the the new cup. I think it's best to track the deprecation. That's part of that.

E

uh I don't think that you're gonna get anybody to make a cap for this, um just because it's so old, uh it seems like not the best use of folks time, um but definitely this is an important one to track and uh I'll go wait on the threat enhancements.

A

So maybe we just added to the enhancement tracking sheet and and they might not need any cap to associate it with, but they do need some prs, I guess associated with and together with the dogs, I assume yeah.

E

I think that's.

C

Yeah, um that's something so just wanted to mention that both the kips are uh in the sheet now uh kept, which is like this uh with the archive design proposal, which is issue number five, and then we have, I think, one for port security summer mission. um So I just wanted to understand whether uh jeremy uh your point was to collect them uh into one kip uh and track them together.

E

C

E

This, I think tracking both separately is good. I don't think you need a separate cap for the deprecation. I think the deprecation stuff needs to be tracked by the pod security admission.

C

Okay, okay got it. Thank you.

A

Yep, thank you. I guess tracking it just separately would be uh great for the other.

B

Day it got it got merged. uh I see a merchant 28 days ago. Again it got uh just for everyone psp. uh This is a removal. It was deprecated in one 121 and 125 was the target for removal.

A

B

So I can post a merge, um but it referenced the issue 5, which is the old one.

B

A

See, I guess, because we use the old issue for tracking the whole um um lifetime of the feature. So that's why uh even deprecation was referring to the old cab, oh old, like issue which makes sense. Thank you for the background.

B

Yeah so yeah psb, you got you got merged, but um it's one of the well will be one of the major uh themes right, uh removing this one and then the the new one. I don't know, what's the state that one that should be the in the cat.

F

Okay cool, I believe the new one's going to stable or try.

B

F

B

So the idea was to align it both like removable, unstable, okay. I.

G

Believe so, yes,.

A

So um so like, um let's make it clear, so we track it separately. What is for the application and what is for the stable or going stable in 1.25 right.

B

H

B

A

Nice, thank you.

B

And the removal already happened, it's already merged and it's done yeah.

E

B

Worth tracking.

E

For this release, because that's.

B

That's a critical.

E

B

That's what I was.

E

Trying to say yeah.

A

Yeah, it looks like the tracking in the husband tracking shade um is great now and uh thank you for the background. um I guess um yeah we get the agreement on this one and other than that is there anything else you want to mention about regarding the enhancement updates.

A

No, that's all from me. Thank you, cece, thank you, and is there any shadow from enhancement want to introduce themselves.

A

No I'll take this as a no and then we can move to ci signal arch.

I

Hey everyone: uh the current status is green. We have like no failing jobs and I sent out weekly reports on the mailing list and on slack today and leo also made a pr to fix something which was wrong slightly wrong in the tool and add some flags. So thanks for that, uh other than that, I was waiting on uh onboarding and updating the release team page because I was not familiar with one of the shadow slack handles, but they are on the call today.

I

So I know if you wanna, if all of the ci signals shadows want to introduce themselves, that would be great.

J

Yes, hey everyone uh I'm! This is my second time on the release team. Last time I was a ci signal shadow and I liked the rule a lot so yeah, I'm back again looking forward to working with you all thanks.

A

K

Maybe I can go next so hi, uh my name is jyoti. I'm the ci signal shadow in 125. I've been with the release team since 123 in bhaktaraj, in both 23 and 24.. I've been loving it so far. So I'm back again so yeah, I'm looking forward to learn ci signal thing is thank you.

A

That's awesome. Welcome back.

I

Would you like to introduce yourself.

L

Yeah um hi everyone I'm noam. um This is my first time um on the team really so yeah looking forward to onboarding and getting to know everyone.

I

Also, while I have you on the call like there are two people uh with the same name on the kubernetes slack, could you ping me so that I know what your slack handle is and update in the lists?

I

Yeah I'll? Do it right now? Thank you. I also have one more shadow, but it's like 1am for them, so they won't be.

A

Able to join this call.

I

A

Thank you so much for the update and thank you so much for your introduction. um Welcome to the release team and let's move to the bug, triage heba, yeah.

M

Hello, everyone, um so the current status is still green. uh We we don't have any blocking issue and any blocking vr. So far, uh so we started to to track the the issues and prs so so far we have 23 uh issues and um and the 12 pr's, which is good everything, looks good. So far, hopefully we'll be like that, so um the shadows on boarding is still in progress. We will have the kickoff meeting tomorrow.

M

All shadows has been added to their contact sheet and the github release page, and let me introduce first the shadows. I believe all of them are here now, uh so we can start with the um yeah. I think you can start, maybe jose. um You can start.

M

Okay, I think we cannot hear you. Maybe we can move to josem.

M

All right hassam, if uh if, if you can hear us, uh otherwise we can move to justin.

M

uh I believe I need you interview.

N

Since release 122 ci signal and then leading cr signal and the previous release, I was part of enhancement team and now I have the pleasure to work with hubba in bactriage yeah, another tour and I'm looking forward. Yeah learning uh new things in the new team yeah.

M

Thank you, sam sam, can you can you talk now.

M

Okay, we cannot hear you yet so you will move to justin.

M

Right so I think.

A

Her okay, we'll ask like again later yeah.

M

No worries so uh I can. I can move forward. Anyone from the shadow uh is still here and can speak yeah. I can go yeah, okay, perfect.

O

Hi everyone uh myself and I am an engineering student, and this is my first time being the shadow, so I'm excited to work with all of you. Thank you.

M

Thank you, uh okay, so moving forward, uh josem has submitted an issue for adding uh some notes to the release team uh uh documents. So thank you some for that and uh the only the only thing that we are still working on implementing a pro uh to update the factory uh sheet uh you know like or actually to migrate it to project beta instead of spreadsheet.

M

The work is still in progress and uh you can you can track the conversation here in this part, um but so far we will uh still continue working on spreadsheet and updating the spreadsheet, um no blocker. So far, that's great.

A

Thank you. Thank you. Try.

P

One more time, if you can hear me, oh yeah, we can hear you perfect perfect. That's a good sorry for that uh hello! Everyone! My name is hassam. I'm part of the bacteria shadows. I have been on release 119 and 120 as a ci signal shadow pleasure to be in here looking forward to really contribute to this release and learn from each one of you. Thanks a lot for the opportunity and pleasure to meet you all.

A

A

And thank you for your introduction. um I guess we get all the bike. Trail shadow uh went through if I miss anyone, please uh raise your voice.

A

Otherwise, let's move to the docs team christine.

Q

Hello, uh so we're we're in the uh shadow onboarding phase and all four are confirmed. I had the pr merge to add them to the release team page and added them to the contact sheet, and I believe a few are here today. So if you would like to introduce yourselves now, it'd be a great time thanks.

R

I can go first uh hi everyone, I'm kat, uh I'm new to shadowing, so I'm excited to get started.

A

Welcome cat is there any other um dog's shadow wanna introduce themselves.

S

Yeah um hi everyone, my name, is indian asico. I worked with. I participated as a dark shadow in previous release. Team 1.24 and I am excited to be back and also get to work with all of you again.

A

Welcome and is there any other dog shadows online.

A

If no, then, let's move to the release, notes carlos. If you are here, I'm here, hello, hi yeah. I can't hear you.

B

Yes, uh so for release, notes uh super excited uh for 1.25. um We have the four channels confirmed, so I was lucky that they agreed uh to work with me and got them access to added um the administrative stuff that that reagan city. You asked for adding to the contact lease uh release and they open um prs for the art, memberships and um schedule the kickoff uh hopefully this week, um and then we have some of them here.

B

We have, I see dipto, diva and rodolfo if you can introduce yourself and and we're green, um so redstone's just starting so be doing the draft folder creation next week.

A

Thank you for the updates is any of the shadows want to introduce themselves.

T

Yeah, I can start hello everyone. I am roloff martinez. I am from mexico. This is my third cycle as a shadow and previously with ci signal and dogs in 122 and 123. I'm very excited to collaborate with you all at a release, notes team.

A

Yeah, that's awesome. Welcome back.

U

Yes, okay, uh do you want to go ahead? Go.

H

Ahead, go ahead.

U

Hey everyone: this is divya. I currently work at vmware, and this is my first time on the release team and I'm excited to collaborate. Collaborate with you all. Thank you.

A

Yeah welcome devya.

H

Hi everyone, uh hello, my name is center, I'm participating in the government, letters community and especially with the release process for the first time. uh I'm excited to see you all to see this huge in the divers coming into here so and thank you for the opportunity and I'm excited.

V

So hi I'm ditto, I'm currently a final year student, I'm interning at cisco. So this is my second time in the release team. Earlier I was as a bug, triage shadow and this time I'll be working on the release, notes. So looking forward to contributing to this release and working with everyone.

A

Welcome back and thank you all for introduction uh and thank you colors for updates. um Now, let's move to comms cat. If you're here.

W

Hello, everybody sorry for not being on camera. I am on vacation and my laptop camera is real bad, um but hey. We are currently green, we're all good. All four of the shadows are confirmed. um We have added them to the contact sheet and the relevant mailing lists and a doodle is out for an orientation meet and greet talk through the handbook answer. Any questions situation, uh two of them y'all met on the meeting uh last week and I think the other two are here. uh Frederico. Do you wanna, introduce yourself sure?

W

Thank you. Kat.

X

um Yeah, can you hear me sure, can yeah perfect so yeah, I'm I'm fred, and um this is my first time in the community release team as a comp shadow, a long time user but first-time contributor and uh well. I just uh appreciate the opportunity- and I'm here to do my very best.

W

Welcome and we're super excited to have you uh garima. Are you here.

Y

Hey um hi everyone, um I'm grima based out of san francisco, and this is going to be my first time with the shadow team, really appreciate the opportunity looking forward.

W

Yay, I'm really excited. I think I think we have a great great group of shadows this time around. So um that's it yeah comms is uh all good for now. Thank you so much and enjoy your vacation.

A

Yeah, thank you and let's move to the release branch management, I'm not sure if um veronica, if you're on call.

A

No um I'll just give a brief update, um so we haven't, we didn't, have a release branch manager for 1.25, yet we have a release. uh We have a brand manager shadow now and uh I guess we will uh select the branch manager within about two weeks and.

A

Anyway, like the branch manager, um the work hasn't started for them. So we still have time and I'll give the brief update like in next meeting and let's move to the emergency advisor ray. If you're here.

Z

Hey folks, I'm ray I'm your emeritus advisor for 1.25, I was the 1.23 release lead. I want to welcome all new and returning release team members, especially all the new shadows. uh This is a great way to start your contributor journey in the kubernetes project and what I like to say, as well as former rowley told me, is that what you get out of the release team uh correlates with how much you put in to the real esteem as well, um so just want to say, hello feel free to reach out to me on slack.

Z

If you have any questions or any concerns, um you know I may not reply right away, but uh but just feel free to reach out and I will get to it. um So, as my update uh all shadows are have been um added to the release team shadows, google group, uh and because of that, I will send out a doodle to that google group for a shadow orientation uh with some possible time. So that's going to go out today.

Z

I'll have a few spots for those for the shadow orientation, because since we are a global release team, uh uh there won't be a perfect uh golden time. Slot for a shadow orientation so probably have at least two uh for those. That's gonna be the next few weeks seconds.

Z

I want to remind shadows to continue the onboarding like uh submit the the issue to have the org membership and also to review the role handbooks as well, and if you, if there's anything, that's not clear in the role handbooks after you know, you might you've asked the role it or, if you ask myself or any delete, shadows or or or cc, uh feel free to make a pr to update the uh the royal handbooks.

Z

uh It's always a work in progress to make the roll handbooks better to make them more clear, all right and that's it for my updates and, like I said before, feel free to reach out to me. If you have any questions.

A

Thanks for the update, I'm sorry, um I got cut from the sharing um the sharing screen. um I hope everyone is okay with that things were towards the end of the update, um somehow it's disabled for me, but I'll just give a brief update, um since we are still on week, two and we're still going through the onboarding process, as we mentioned before, please feel free to encourage all the shadows to um keep working on the onboarding process like grind the org membership and review handbooks uh and I'll add everyone into the release.

A

Augs um like, after all, the shadows become the kubernetes og members because they will get complain.

A

If I add a non-org member into the list so uh and please feel free to ping, either re or me for, like the sponsor um to become the community org members, we are really happy to help and I'm not sure, um I'm not sure. If any of the lead shadows is on call, I saw grace's uncle since um they might go, they might introduce them last week, but since this week there are more shadows during the call, uh if any of you wonder, uh introduce yourself again, please feel free to speak up.

A

I saw jesse and grace his uncle well.

AA

This is I'm in class um hi hi, I'm grace, I love enhancement for 1.23. Now previously we had some teams as well excited to meet all the shadows on the team.

A

Hi great to have you and enjoy your class.

AB

um I'll say a quick hello, also I'm uh I'm xander! I I've been around for five cycles now something like that. So I'm super excited to have you all here and uh yeah, looking forward to working with everyone.

A

Yeah great to have you here um is there jessie you'll, hear me yeah.

G

Can you hear me.

A

G

I'm having as I'm having a zoom freak out, so I can't I can't turn my camera on sorry. um I think I introduced myself last week, but I am jesse. uh I've been on a few release teams now um this is, I think, technically the first time I've shadowed, which is amazing. um Oh no! Actually I shadowed last last on 124 too. So I was. I was a.

G

I was a lead shadow for last cycle, um but I led uh I led comms for 122 and docs 4123, so coms and docs folks, if you need any specific help that I can smoke jump in and help you with please ping me anytime, um and I'm just I'm happy to keep helping out.

A

Yeah great to have you here, thank you and leonard, if you're here, and want to introduce yourself.

Z

Audio is low leo.

Z

You need to lose your mind.

F

Hello, hello: now it's better.

AC

I think I'm gonna look at the room now. Yeah.

F

Okay, awesome, okay, um hello, yeah! My name is new. I also introduced myself last week, but um nonetheless to make the cycle complete hello.

F

I was involved with ci signal quite a bit and I did a couple of prs and stuff to improve. Also the ci signal, reporting tool and so on and um great to have everybody here, I'm seeing a lot of uh faces familiar faces. um I also want to point out one thing: um maybe some of you already know the linux foundation, inclusive, speaker, orientation training course, which is, um I think it only takes a couple of hours like one one hour, two hours or something like this um for going on from 1.26 going forward.

F

This will also be one of the onboarding tasks for the release team leads. um So I can drop the link in the chat. I think this is just an awesome short training to work in open source, so.

A

Yeah, thank you so much for sharing the link.

AD

It's almost it's also worth mentioning that that is free training as well.

A

Yeah and it's worse to do so so um please feel free to get the training done.

Z

Also does not take.

AC

That long yeah yeah it it yeah it's not hours, I I'd, say yeah. I thought hours and hours.

F

I did it, I did it five days ago. I I thought it was an hour, but maybe it was not that much.

AC

You might have been tired after kubecon, maybe.

AC

um Shall I I'll do a quick intro and my name is robert kealty? I am uh here in dublin in ireland. I am was a shadow on ci signal. I think on 119, and I think it was 120 that I led and I've been away from the release team for a time, but I'm returning doing some work with leo on um some process: automation um around reporting on ci signal activity, I'll be looking at some other things in the coming weeks and so yeah.

AC

If you have questions about ci signal and just ask and ask in the room and we'll all weigh in and help you out.

A

Thank you, robert robert sorry, thank you so much for introduction and welcome back yes, and is there anyone um in the chat want to introduce themselves. Even you are not part of the release team, but we are like.

D

I think you can say hi so uh hello, everyone, my name is adolfo garcia. I usually go by puerco and all of these meetings- I am one of the tech leads or with sick release.

D

I oversee the release engineering tooling and uh which is the tooling that release managers run to cut the releases, and um I usually try to be in all of the releasing meetings to hear about problems, cutting the releases and uh the tools that you run and if you have any questions whatever uh feel free to ping me at any time, on slack or on the channels, and I'm so excited to see you everyone here and welcome, welcome, welcome and thank you.

A

Thank you for speaking up and thank you so much for your continuous support.

E

I'll say hello too, um I said hello earlier, but I'm jeremy, I'm also a tech lead for sick release. That was the 120 release lead. I think, and I've been an ea. I was an enhancements lead. I also did bug triage.

E

So if you need help with like pretty much anything, I'm here to help uh try to come to all these meetings. It was my birthday last week, so I was off and did not do anything that day.

A

Happy birthday and thank you for speaking up and introduce yourself.

A

Is there anyone want to introduce yourself it's a perfect time, because we got all the shadows joined and did we go to the team here and you want to introduce yourself, please feel free to do so.

AD

I'll introduce myself I did last week, but my name is mark gucci jackson, I'm having problems with my camera right now, so I can't turn it on. uh I've been uh a shadow for plug triage a few times. I was the uh lead, uh but then I moved over into to sort of just continual release management but then stopped and I'm now back so I'm happy to see all the familiar faces and and meet all the new people.

A

Yeah hi welcome and thank you for introducing yourself again. um Anyone else.

A

I'll take the silence as a no.

J

AE

Yeah I've introduced myself last call, but again I knew uh hello. My name is: I have been contributing to the controversial contributions. I've worked with paris ray uh and josh and bob a lot uh and so yeah. This is my first time being an enhancement shadow or maybe uh this is my first time in the abyss team so happy to be here.

A

Yeah, it's great to have you here, thank you and anyone else.

A

Cool um nice to see you all here and I'm so sorry I uh randomly assigned it somewhere else as a host. So I cannot stop the recording mark r. If you are on the call, and if you want to stop the recording for me or grant me the host, if no.

F

A

Guess everybody still, I.