 Welcome everyone. This is Jenkins office hours September 24, 2020 for Google season of docs documentation. Thanks for being here and let's look at the agenda. And here's what we've got noted so far. Oh, nothing on the agenda yet. Let's create one and be sure that we got it. Hey Mark, how's it going. Hi Kristen, how are you doing good. I've been able to join for a few minutes I was worried that I would not be able to open the zoom so I'm glad. No, yeah. And we probably should get you registered into the into the CDF account so that you can start it if it's one of a, if I and Mark you're both not available because there's no reason for you to be blocked from using that remove. There we go. Okay. We all did. Alright. So, we've got the three of us today. So topics. Last time, let's bring them in. Here are the links with the doc mailing list properly. So Xena, would you like to. Are you at a point where you'd like to discuss the draft Google doc that you've got created. What would what else would you like on the agenda. Yes, yes. Because it leads to on the draft on the spelling Jenkins on people and it is. Let's see and do we have other pull requests we've gotten so we had a discussion. That's that one is you know, Mark. We can certainly discuss that. I haven't seen a share of that link. How about if we move that underneath the graph draft Google doc, and then my usual nervousness is still working okay, etc. Okay. The link to the draft. Oh, very good. Okay, so it's in the chat. Okay, so here's the draft. Let's go large cluster. Create a namespace. Service account and helm is it. And if I remember correctly, helm is a different approach. Yes. Okay. All right. So do you would you like to us to spend the time here reviewing in detail Kristen certainly has experience in this space that I lack. Okay. Or would you rather we we just review it offline and give you feedback in the document. Um, whichever one works for you, what is fine for me if you drop comments, I'll go through them and work and work on them. Okay. Yeah. And also, is that shared out to, I guess, the docs channel as well. It hasn't been or hasn't. No, it hasn't. Okay. But but the link is the link is available and so we we just need, I think, Zeno if you want to send a message and email us to the docs channel. That would be great. Okay. Welcome other people to review. Okay. With the comments. Yeah, because that was what we were talking about on Monday, like making sure that it has like the comments only. Right. Yeah. Yeah, and it's a strong one. This one is already. Yeah, it's already set up that way. So it is already configured to allow anyone can comment. Perfect. Very cool. Okay. So I just wanted to find the link. So it's like, if it's in the stock of it also on the channel, it's good to share out and maybe. I'll help step through it too and like make sure that it makes sense from the perspective of like, if you're starting from scratch. Very good. Okay. And let's see, shall we check the status on the poll requests. So I think we had comments from Oleg on one of the poll requests. Yeah. Some kind of this one was his right where, and I agree with this one that we should postpone into publishing until tomorrow because today we need to keep the social media focus on the Jenkins elections. That launched and get people involved. Now, now this one on helm and Kubernetes helm, at least helm charts are mentioned explicitly in in your install guide. Yes. And so I now, but I didn't see anything yet on the Kubernetes operator. Anything on the Kubernetes operator yet. Would that be a good thing to add as a maybe a phase three, like just exploration. I did add the links to the ones who are the office hours notes from like where the presentation for Kubernetes operators if you want to watch it. I know there's repository, but maybe it's something that's later after like the basics. Sorry, Christine I didn't get that. Oh, sorry. Maybe adding the Kubernetes operator is that like a month three or like a month to piece because the helm chart I know that you're working on now but maybe the Kubernetes operator is, if it hasn't been looked at yet is something for Maybe not right now but maybe for the next month or so. I think I think that makes sense put it later because you're on the helm chart now. Yes. If it's just an introductory section, I could just probably read up on it and put probably like an introduction. But I think I'll just have to figure out probably somewhere in the timeline where I'll be working on Jenkins operator and put like an introduction. Since I kind of put a brief timeline on what I'll be doing through the internship so I actually don't think it's a bad idea to just put like an introduction on what helm is and Jenkins operators also. That's a good idea. Okay, so include an introduction. The intro description of the operator. Now am I using the correct term there Jenkins Kubernetes operator. Zina, did I capture what you're what you're describing there in the Yes. And I do like the idea of putting the intro description into the into even the the guide is currently developing your draft Google Doc that sounds really attractive. That way at least people are aware there is a concept of a Jenkins Kubernetes operator. And if if they are using operators, that's one for them to consider. Okay. The other topics there that you would like to discuss Zina. Yes. I don't know. I was able to resolve the issue I had with service account on Monday, but I noticed I was having issues with user group. Sorry, you had an issue with I missed the word there with user user group user group. Oh, okay. Use a group. Got it. So when I read about it and I did some research, I found out what I got was that I was probably using a different user group to run the container than what was in the file in the value file. I wasn't able to resolve that at the end of the day. I don't know if you understand what I'm saying, but let me just paste the configuration here just to give context. Okay, so I've decided configuration in the chat. Oh, good. Okay. First paste it without marks failed. Sorry about that. There we go. Okay. So I this this is not at all familiar to me. Maybe Kristen can. I don't know where we just plan for need discussion with market on Monday. Yeah, let me look at this a little bit more I was like, I've, yeah, to make sure that this is not familiar with home. So that's the issue with that. But yeah, I was like, yeah, that does seem like, I think that you should probably have that defined as something but I will double check that like it shouldn't be zero. I actually found a temporary solution configuration. This configuration here is a temporary solution. So what is in Jenkins. Chem chart is run as user is 1000 FS group is one default in Jenkins value, chem chart values rather, but when I run it as that I'm having permission issues so after doing research and trying to maintain I found a post on stack overflow that said, but implication would be that I'm running all commands in the container as roots. Yeah, that's. Yeah, that's. So, and I'm not really sure I don't think this would be the best ways to solve this. That's why I decided to raise it. Right. And I, at least my, my, my innate response to running as root, even inside of a Kubernetes container running Jenkins as root in particular is. Oh, I don't want to do that because of all the things you will discover that Jenkins mistakenly did this or did that and had previously relied heavily on operating system protection to defend you. And as an example, I've written tests in particular plugins I maintain that depended on never running as root. And so, so, yeah, I agree with Kristen that's run as users zero is is a sort of a red flag. It's good, I guess for now, like, and then let's figure out like how to like just like to get the stuff started and then we'll figure out like I, I bet there's something where it's just you have to be able to give the agent, the permissions that user 1000 or like the level 1000 but so I'm, I'll look into this so there's probably like one maybe one extra step and then definitely make sure to add that to the guide. Great. So, you know, it seems like we've got either we work it with, you can try working it with Marty chat, like tomorrow because DevOps road finishes today, or we will, we will for sure address it on Monday in our docs in our docs office hours then. Okay. Great. Any other topics you'd like to bring. No, it seems like the big issues there are. Kristen and I need to review the Google Doc sorry that I'm behind we've got hacked over fest coming and things are busy. And then the schedule for the doc to go out. I guess. Oh, right. Right post the blog post. Yes. I'm trying to make the changes to be so you can have time to reveal and still push it out tomorrow. Great. All right. And for my comfort, could you when you make those changes, adjust the adjust the date stamp on the file name. Okay. Okay. I'm going to do that tomorrow. That way I don't have to do any manipulating a file names myself. Okay. All right. Good. I think that covered the topics that were on the list. One more check anything else you know. No, thank you. All right. Thanks Kristen. Thanks. You know very much. I'll post a copy of the recording. Bye.