Kubernetes SIG Contributor Experience, 29 Jul 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: [SIG ContribEx] GitHub Administration Subproject BI-Weekly Meeting for 20220729

Description

[SIG ContribEx] GitHub Administration Subproject BI-Weekly Meeting for 20220729

A

Hey everyone uh welcome to the contributor experience, github management, sub project meeting um of 28 july 2022, um just a few things before we get started with the agenda, uh to remember that this meeting is covered under the humanities code of panda, which essentially boils down to please be nice to everyone, and this meeting is being recorded. So please be aware of what you say and do in this with that. The first agenda item is from myself and the other github admins, so new contributor coordinator selection is underway.

A

We are yet to get a few acts from other data admins. Once we get them, we will reach out to the prospective candidates and start the rotation program.

A

Does anyone have any questions, comments or concerns on this.

A

Okay, I think, let's get to the next point. uh The next point is from mother.

B

Yeah hi, um so this is sort of in the gray area between guitar management and contrabex, but I wanted to bring it up here uh to cover this side of the gray area. um So I know that bob assigned a few folks to look at this one, but I wanted to know if there have been any discussion since then, and what can be the possible next steps like do?

B

We need to get consensus on something or do we need to discuss something, because this is for sure, like a very very user, it will improve user experience way a lot, but it also has a few implications if enabled on kubernetes kubernetes. So for that aspect of things um you know like what can we?

B

What are the next steps? Basically.

A

So on this there's a pr open to add community search kubernetes uh to enable that plugin and the action item is only few of us to write an email to kdf and ask for thoughts, comments and concerns and decide on a lazy consensus deadline. Maybe we will keep it open for three weeks or so because we anyway plan to enable it for kubernetes 1.26, and we will.

C

A

That uh time, when code is frozen, to enable this change, um that is just on that is just from me, but the consensus right now is that we will write a draft and then we will send it over to the community and see feedback as in what does everyone think about adding uh this feature? I do.

D

A

Personally, that this would ease a lot from reviewer's side as in we do ask people to scratch. Their comments into meaningful uh chunks and lgbtm goes away uh the current state and we would really benefit and.

D

Reviewers would really.

A

Benefit from this.

D

Yeah, do you need so I mean that sounds like a very clear path forward. It seems like contrivex is on board with it um from the pr do. Do you need any help? Writing the email or anything like that, or can I help out there.

A

um Yes, we would need some feedback so.

D

A

I think what we can do is we can start up with the draft of the email and then send it over to the contrabax uh slap channel and then get feedback from people like.

E

Hey, what do you think about the email and then just shoot the email through.

D

A

Awesome does anyone have any further questions comments or concerns on this topic.

A

Cool uh we will go forward thanks for taking the notes, whoever is taking the notes. um Thank you for volunteering. um That's really appreciated. um The next topic is from serif um order level. Github token permissions for creation of pr's with github actions. um Do you want to talk about it.

F

Yeah, so uh in in the previous meeting, um abhinav joined and talked about this the same issue. I just wanted to uh hear for myself one more time, uh so we are having difficulty creating prs in our classroom: api provider, aws repo with uh using github token, although we have all the permissions um in the repo itself and we add the permissions in the workflow.

F

So what we are suspecting is that there's some restrictions in the org level, uh github token usage, so who can check who have access to kubernetes six organization level settings? You know.

G

We already have this conversation and the problem is we don't want to change permission at the org level and we suggest to basically do that using a pro job and because pro job already have token establish to basically do whatever you want the thing we want to avoid basically and grant permission at the org level for a specific repository. I think that's the issue, because that's gonna basically open the door for escalation, privilege.

F

Okay uh yeah, so I we didn't even have the answer of it is not parameter in the ord level. Then then, that's fine, that we are not doing anything wrong uh in our repository and in our workflows. That means it is restrictive in the arc levels. Am I understanding curry.

G

Yeah, the the the way github setup will set up. Basically the will define. The token is basically, if basically, let's say, give a token right now at the orc level, which means anyone using that token will is capable to do something at the orc level.

G

I think that's the issue for us, like we don't want to provide a token to a specific sub-project with access to the entire organization. I see.

F

And so is there a way to create a pr using the github token, with the projects like do we have a bot that we can use yeah.

G

They are, they are basically token existing in github token existing on the basically on the kubernetes infrastructure, and you you just have to mention the secret of that talking in the project, and you will be capable to use that.

F

That's okay and are: are we gonna use a bot? I saw uh that there's a bot in the yeah.

G

Yeah yeah we can, we can use, we can create a new bot for you if you, if you want and basically create a token from that bot and put that in the communities infrastructure or we we use basically the token from because we have multiple bots and multiple tokens from those parts. So basically we can just use whatever you want, as you see provided by those bot.

F

So I think ebina reached out to you directly and asked about using the existing pose, and I think the answer is those are specific to certain um verbs and we might it. But it may not be easy for us to use those spots. So is that why uh it is preferable for us to request a new bot for pr.

G

Creation feel free to basically request a new button. We create one for you.

F

Okay in in the.

G

Kids org repository.

F

Okay sounds good. Thank you.

G

Let me do you have the issue somewhere.

D

F

We just have the question as issue. I I linked on the document. Let me find that post it in the chat.

G

Okay, okay, I found it.

G

I will basically create a new token from about that dozen.

G

We have but not used right now. We can create a new token from that. I think that's what we we can use like uh number one. We can use the token from trish product right, no one using that.

E

A

I am a real uh like property of uh separation of concerns, um so I feel like adding a new bot if it's not way too difficult, maybe.

G

E

A

G

Yeah we uh or an existing, but we can have x token and we can just create a new one and put that as a secret.

G

I don't really see the concern here. That's why I'm asking for trish party we plan to shut down that at some point, so we can. Basically you reuse the token for that from that.

A

I think if the kubernetes such category security policy allows this, uh I mean I'd, be okay, okay,.

D

A

Also, okay, uh speaking as a seeking fraction.

F

Thanks all I will I will reach out uh in the issue itself. Thank you.

A

Thank you for bringing this to the meeting.

A

Does anyone have any follow-ups to this point.

A

Okay seems like we don't um and we don't have.

D

A

On the agenda as well, um is there something.

E

A

People have to discuss.

A

um Omar he's good.

C

Hey uh I just wanted to introduce myself. I work at github, um I'm just gonna start showing up to these things just to see. If I can give you guys, some support, um I think he's having once a month, is that right.

G

Yeah it's each month last week of each month and welcome people. Is I've been looking for you for a long time.

D

C

So I can uh so I'm responsible for projects at github, um but I can certainly try to like and also like, not like an expert definitely on the ci side, but I can certainly like try to point you all in the right direction or at least like find someone who can can help um so yeah. I just want to judge myself. I have this meeting on my calendar now, so I will start being here.

D

Awesome, thank you so much yeah. Of course, it's amazing.

A

Thanks thanks for coming to this meeting, um really appreciate it. We will. We will have a lot of project related questions. Yeah. Do you don't worry.

D

Now I know who to.

C

Go there's, I think, there's I think, there's one now how's it going all right.

A

Yeah, I know go ahead.

G

Yeah it's basically, I saw github issue and now ga the new github is, which means the project now ga I still don't have time to check, but can we get the same workload features from the old version of project like automation, because, right now we there's a an ongoing conversation about using github workflow to automate heat up.

C

uh You should get a workflow, you mean, like you, mean, like the on open move here on close move there, that kind of thing yeah. um We don't.

F

C

But we're gonna be working on that pretty soon um up until recently, we were a pretty small team. We were like two pms and a couple engineers, and now we've grown to be five pms and like something like 60 engineers, so we're slowly, carving out aors and one of those aors is automation. So I anticipate as soon as that dust is settled and someone gets on on that that'll be like one of the first things we do um so yeah things are starting to pick up steam.

C

So hopefully, like trust me, the second I got here I was like: why aren't we doing more automation, stuff? Our developer, like our customers are developers, uh but we had some other stuff. We had to tackle um the other exciting thing I wanted to mention really quickly uh we're shipping. uh This thing called uh we, we call it taskless blocks, it's our solution to hierarchy. Like issue hierarchy.

C

um We were planning on uh releasing it to like all of kubernetes like the whole org, um and I got to talk to um to oh, my god. How am I forgetting his name?

C

uh We were playing, oh bob, uh mr bobby tables. I was going to talk to him about like communicating that out to folks so we'd certainly love if you gave us some feedback on that, it's still pretty alpha, but it's, I think, a feature that has been missing for a long time. um Also talking to the release.

C

One of the release leads on friday to potentially also use that for for their work, um so anyway, lots of stuff coming. I really want to like have a focus on kubernetes, I'm I'm a former uh native contributor. uh I made their getting started guide if anyone has done that that was that was me. I authored that um and uh yeah. I really have a soft spot for open source. I want to make sure we're we're serving y'all. So yeah just consider me your point of contact at github.

C

um I I'm afraid to have just said that but yeah consider me your point of contact um and I'll try to point your questions in the right direction.

A

That it was so helpful.

D

It's going to be very helpful and we'll try not to abuse you.

C

That that is my- that is my hope. As long as as long as you're, okay, with with me uh treating you all, as you would treat a contributor, I think you know, I think, that's probably the the right to write sla for there. You go yeah.

A

That's awesome, awesome, cool.

D

Like I can't tell you how long we've needed this.

C

Yeah, I'm sure I'm sure if you asked we would have found somebody, but I I this is just my personal interest.

C

I did a lot of work trying to get canada into the cncf and um you know so I'd love to get more involved, especially if you all need help with like project management, stuff sort of my strong suit or facilitation. I can help with that, uh not a developer. So don't let me in the code base, but uh I can. I can do other other things uh well. So.

A

You should you should totally try out the release team. The next cycle.

C

Sounds terrifying yeah I'll talk to uh I'm talking to who am I talking to you tomorrow, marc rossetti and uh it looks like priyanka sagu um tomorrow, so maybe they'll, maybe they'll wrote me into shadowing one of their releases that might help to to build some some tooling. That would be. That would be like helpful yeah yeah that'd be cool sweet. Well, I don't want to keep this meeting open for longer than it has to be, but thanks for letting me sit in and um I'll be seeing you all once a month.

A

D

Much thank you so much again. Thank.

A

You um do, I have anything else on the agenda um coming to new member introductions. um I see this here for the first time. Do you want to introduce yourself.

C

We can't hear your audio's coming in a little fuzzy.

E

Oh sorry, for that they say like that now.

E

And they told me to uh they asked me to get involved in sig contributes and it has been a nice place. I've been uh I've been listening to the conversations of the slack channel for quite a while, and I just had to come over this and just with them.

A

Awesome. Thank you for coming to this meeting.

A

um So we don't have anything else on the agenda. I say we can call it early by eight minutes and give everyone eight minutes of their time back. um Thank you all for coming to this meeting and thank you mother for taking the notes today. um I hope you all have a great rest of thursday and for people for whom it is night like night.