 All right. Welcome, everyone. This is October the first. It's Google season of docs office hours. Let's take a look at our, our notes. Excuse it. Kristen today she's out of the office on vacation. So we've got a topic for the draft Google doc. Okay. Okay. So we're just ready for review incremental delivery of segments into a larger structure and transfer of org admin. Should all those remain on the agenda? Anything we need to add. For work admin. Remain. It's still an open item. I know it is on Oleg's to do list. All right. Then let's go ahead and start from the top. Okay. Okay. So you want to tell us how it's going and let's, let's discuss that. Okay. So, um, for installing Jenkins, I worked on two different, um, option that's using helm. Um, the first part just actually explains, gives a brief introduction of Kubernetes after that I gave two options. Um, some YAMO files. That's deployment file and the service file for those that might not want to use helm. So those are the two options I currently have right now on installing Jenkins on Kubernetes. And then Marcus suggested adding, um, a bit of explanation about on cluster old minding and cluster old. I did that. So I'm not sure if anyone has had the chance to review it yet. I did look that over and I think that is perfect. We can mark that as completed. So that's this one right here. Okay. Great. Excellent. Well done. Anything else you know. Um, no, for now I'm working on Jenkins. Um, so the helm section is complete. And now is that included in the pull request? Yes, it is. And you're working on Kubernetes operator. Yes. Markey helped me with that. What's the official, is it Jenkins operator for Kubernetes? I was a Kubernetes operator. Jenkins Kubernetes operator. Thanks. And also I wanted to ask for the Jenkins Kubernetes operator. Would you be better to have it on that, the managing Jenkins session or under a new Jenkins on Kubernetes section. Can you remind me how you're doing the helm section? Is that a separate section or is that under managed? Um, the helm section is on that installing Jenkins. Uh, isn't Jenkins Kubernetes operator also an installation option? Or have I misunderstood this? That's why I was asking that. And the reason is this, I think if you, if. If I recall correctly from the code, it is installing Jenkins. And if that is the case, then it should go under installing Jenkins. That's just my opinion. Okay. Which even, even puts even more emphasis then on your, your concern, Zenab about G is the, is the installing Jenkins page going to be just too huge. And yes, we'll have to, it seems like we'll have to re rework it so that it presents subsections. But I'm still of the opinion. We don't want you to do that because there are lots of us who don't want to do that. Okay. Now, are there, are there in your experience with Jenkins Kubernetes operator, are there things that are done with it during runtime where it's, it's also an administrative tool or is it mostly an installation tool? Was that question for me? Either of you, I guess. I don't want to interrupt Zenab. So do you want to answer it? If not, I can. I can answer that. Yeah. So the Jenkins operator does two things. Number one is it will do your installation. Number two, it will do administration of various things. Okay. And now is that different than Helm? Can I use Helm to administer as well? Or. No. Helm is a different way of doing things. Okay. Okay. Okay. The Jenkins operator is another way of doing things. It just has more to it. Okay. Got it. Thank you. Hang on just a minute. I need to go close my door. I fear the sound is going to bother. Okay. Thanks. Thanks for the clarity. Excuse my getting a Kubernetes education while, while we're doing this. No, it's okay. Totally. Okay. So. Installation of Jenkins and administration parts. That's on Jenkins Kubernetes. Both of them be. On the same page. That's installing Jenkins page. That's a good question. I think for clarity. In. The use of the operator, they should just remain. On the same page. Or if there's a possibility to break out. The, the, the, the, the, the, the, the, the, the, the, the, the, the, the operator. You know, that's an entry, but maybe we break it off. Or becomes now another sub entry about the administrator. Administration part. But I think that's. You know, it's just an, it's an option. Or if you put it somewhere else, you could. You know, have some, have some type of. In the ASCII dock linking to the other area where it talks about operator administration. That's another option as well. Okay. Yeah. Yeah. My preference would be. Limit the administration. So I think of install as in. As the first administrative operation, but then future administrative operations. They go elsewhere to answer them. But with that work, if you've said, Hey, I'm going to do the install portion of Jenkins Kubernetes operator in installing and all the admin functions. I'll put elsewhere. Or is that going to make your writing very difficult, you know. No, it's not going to make it difficult. So I think. After the installation section. I could just do probably like a brief introduction and put a link to where the administration is properly explained. Okay. So all the information is not on the installing Jenkins page. And I think that's an idea. Yes. That was one from Mark. No, it's not going to make it difficult. So I think after the installation section, I could just do probably like a brief introduction and put a link to the installation section. That's one from Mark. Great. I like that very much that way. We know that the installing page is going to be huge and we'll split it. Or it will be split. Not by you, but it will be split. Still the admin material. There, I assume that the Jenkins Kubernetes operator has lots of admin things that are unrelated to installation and more about configuration or modifying setup. Yeah. Right. All right. See now back to you. Um, I think also for me, or did you ask a question? Nope. Nope. Just are there more things you wanted to discuss with us on installing Jenkins on Kubernetes for the install portion? No, no. So the next topic was pull request ready for review. Congratulations. So the PR is there. And I'll do my best to review it. It may be a day or more before I get all the way to it, but I will do my best to have it done before. For sure before our Monday meeting. I'll have it reviewed by my review will be in by today. Great. Thank you. I've basically moved all the content from the Google doc to the pull request. So you don't have to review. Both the Google doc and the pull request. You can just review everything in the request. Agreed. Thanks very much. Anything else on the pull request? No. Okay. We had another topic incremental delivery of segments into a larger structure. Yes. So about the structure. You know, I suggested a pull request where we add sections and puts work in progress, but I didn't want to merge everything in a single pull request. That was why I didn't add that to this pull request. So I'll do a different pull request just for the structure alone. So this is not too clumsy or confusing. Great. Okay. And that, that sounds good to me. That separate pull request because we can get different conversations going already get the benefit of the install material. Merging and being the users while you're still working through. Hey, here are the other things to do on this, on this structural pull request. I like that. Yeah. Okay. Markey. Is that okay for you? Perfectly fine. All right. So then the goal is, I assume as soon as you get that submitted, we want to get a review of that and then discuss. Discuss at the next meeting. Yes. Very good. Okay. Anything else on the structure for request? No. Markey, you want to take that last topic, transfer of org admin. Yeah. I'm still waiting. Not only for the transfer of the org admin, but also to be added on as a mentor. And that's not by any fault. I know that. Oh, I guess it's got a lot going on. So I will ping him, ping him about it before the week is out. Great. Yeah. And. And the, if that is at Markey as a mentor. That's great. Thank you. Excellent. Anything else that we need to, any other topics that have come to mind or that we need to discuss. There is no topic, but I would like to say. You're doing an amazing job. Thank you so much. And I echo that. I'm delighted. Thank you for your contribution. Thank you very much. If you haven't registered for October fast, by all means, you should. You should open source. So congratulations. That's wonderful. Thank you so much. And thank you for being amazing mentors also. Thank you, Markey. Thank you, Mark. Thank you so much. It is, it's delightful. Thanks a bunch. I think that covered all of our topics for today. Is there anything else we discuss before we close our session? No, nothing else from me. All right. Thank you. So good luck reviewing pull requests. We'll talk to you to talk to you in the next meeting. Awesome. Have a good day.