keptn Community, 1 Oct 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Keptn Community Meeting - October 1st, 2020

Description

October 1, 2020
Diary - what happened last week?
Kubernetes 1.19 support
Bridge Heatmap Evaluation Tile improvements
CommunityBridge - Mentoring Program from CNCF: selection to be made soon!
Hacktoberfest - we are part of it as well as contributing.today
Keptn mailing list / google group: https://groups.google.com/forum/#!forum/keptn
Keptn on Civo marketplace: https://www.civo.com/kube100
Good first issues: https://goodfirstissue.dev/ or start here
Noteworthy Issues & PRs (Review)
For each PR, please tell us if you updated the docs, or in case it was not necessary please say so.
Supratik Das:
Add build and run targets in the makefile https://github.com/keptn/keptn/pull/2418
Ankit Jain
keptn auth --export command https://github.com/keptn/keptn/pull/2417
Keptn install - fixed infinite loop bug https://github.com/keptn/keptn/pull/2426
Anukul Sangwan
Add Keptn cluster version to cli https://github.com/keptn/keptn/issues/2412
Bridge: Show actual state in approval finished events: https://github.com/keptn/keptn/pull/2427
Add Pluto to CI https://github.com/keptn/keptn/pull/2441
YAML Support in CLI https://github.com/keptn/keptn/pull/2447
Florian
Endpoint for triggering evaluations https://github.com/keptn/keptn/issues/2387
Fixed Integration Tests for release-0.7.2 branch https://travis-ci.org/github/keptn/keptn/builds/731865451
Updated spec of evaluation-done events https://github.com/keptn/spec/blob/master/cloudevents.md#evaluation-done
Ermin
https://github.com/keptn/keptn/pull/2424 - Highlight comparedEvents in Heatmap
https://github.com/keptn/keptn/pull/2432 - Show labels on xAxis in Heatmap
https://github.com/keptn/keptn/pull/2406 - Evaluation tile rework
Johannes:
Open PR: Improve documentation about Quality Gates https://github.com/keptn/keptn.github.io/pull/646
Roadmap → KEP / SPEC / Issues
KEP 06: The next generation of Shipyard: https://github.com/keptn/enhancement-proposals/pull/6
Work in progress:
https://github.com/keptn/keptn/projects/29
Release-checklist (Christian):
https://github.com/keptn/keptn/wiki/Release-Checklist
https://github.com/keptn/keptn/issues/2404
Backlog Refinement / Next Sprint:
https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Akeptn+user%3Akeptn-contrib+label%3A%22next-sprint%22
Planning Board: https://github.com/keptn/keptn/projects/29

Learn more: https://keptn.sh
Get started with tutorials: https://tutorials.keptn.sh
Join us in Slack: https://slack.keptn.sh
Star us on Github: https://github.com/keptn/keptn
Follow us on Twitter: https://twitter.com/keptnProject

A

So welcome everyone uh to another captain community meeting. um We are pretty excited uh to have a lot of folks uh joining this time um and uh we have a lot of content also to share. So, first of all, thanks everyone for uh participating in the community breachment bridge mentoring program. We received a lot of applications, really a lot of them uh thanks so much uh for all your interest. uh It was, uh most of them were really high quality applications and we are uh still in the process of going through those uh applications.

A

So we will make the decision and uh inform people with the normal procedure that is, um is given the normal timeline that is given by the sorry that is given by the cncf uh so just uh make sure to to watch the the cncf um uh page and github repository, because uh it's basically there uh the mentees will be uh also announced there uh with the projects.

A

uh So thanks a lot for all the contributions that we received here. We really appreciate that uh another part. uh If you want to start contributing to captain, um we are also part of the hacktoberfest, so we are going to label some issues with oktoberfest, so it's easier to find them, uh but also if some issues are not labeled with october hacktoberfest, you can still contribute and uh we are also featured on the website contributing dot today.

A

uh So that means you will find the video there uh a short video on captain it's about five minutes and we will explain a little bit. What captain is how you can contribute uh which skills you should bring to contribute. So, if you're interested uh please check out contributing dot today they have their own virtual meetup um tomorrow october 2nd, but uh it doesn't mean you have to be there tomorrow, uh but you can still.

A

The whole month of october is open for the hacktoberfest and we are happy to see your contributions um and then another thing. If you want to test captain- and uh you don't want to spin up a full-fledged kubernetes cluster on on gcp or aws or some other um public clouds, there is a very interesting um new kubernetes distribution out there based on k3s and it's from sibo and captain is listed. Also in their marketplace, um so it's a one-click installation of captain in the supermarket place. uh If you're interested, um please take a look there.

A

We are not affiliated with sivo uh in in in any other kind. It's just that we receive the contribution from the captain community that lists us in this marketplace and we are really happy to share this also back with the community. So if you are interested in, uh please take a look right now they have kind of a free trial month or they will give away a couple of three credits, but I said we're not affiliated with zeros just to let you know, I was just going to ask there's a price involved.

A

As far as I can see, or is there any special deal that we can? Maybe I don't know ask them um so right now there is no special deal um if you are using captain, uh because I said we are not affiliated with them. um What you can do is uh sign up, for they call it cube100 uh and I did it as well. I got the free voucher for um uh I'm not sure about the the the whole thing, but it it's it's enough to run a cluster for a for a whole month.

A

What I'm doing is I kill the cluster at the end of the day and then start at start again. So I can really. um I yeah I'm not even sure how much I've already used but yeah. That's interesting, nice yeah, it's a pretty cool thing, so check it out. There will also be a webinar uh coming wednesday, where uh I'm invited uh from the civil team or to to the civil team, and I will uh just present this a little bit uh if there is interest.

A

I can also present this in uh maybe the next captain community meeting, but we just did a polishing of the of this marketplace integration. I was not sure if I can finish by today, um so this was uh mostly from my side. um I know we have a lot of new contributors to the meeting.

A

I would just take a look here on the uh on the attendee list and I will promote those also to panelists that uh will will be needed to to share something. So just watch out if you're promoted to panelists and uh yeah, I think with this I'm handing over again, if you are contributing during the month of october, uh you can be part of the hacktoberfest and they are giving away some swag again. We also not affiliated with them, uh but it's just uh for you. It's a nice.

A

uh Maybe it's a nice gift if you want, if you want to do this so with this, as I don't see david on the call I'm already handing over to socratic thanks so much for your contribution and I'm stopping here, my screen sharing and uh if you want to go ahead and share your stream you're most welcome.

B

Yeah sure so hi everyone. So uh what what I was working on recently was. The uh intro uh was the introduction of the make file. So uh previously the make file was empty, didn't have any targets and all- and I will just share my screen here-.

B

So, uh can you see the screen.

A

B

Yeah, yes, so uh so the makefile was empty and uh what I did was to add certain commands to it. That was uh to build a cli to start the bridge and format, lend clean and also some commands to one of the commanders to test to perform unit tests on the cli and another one was to prepare the prepared code for the pr. So these are all fairly simple. We just need to run the commands and what they actually do.

B

I will show you the code a bit, so uh the targets are somewhat like this, so the bill cli is a simple. uh It does a go, build and sends the binary to a bin uh bin folder right and the start bridge.

B

There is a certain script to start the bridge, it installs the it checks for the uh node dependencies and installs them and starts the angular server uh for the linting and all I install I check whether golem is present and install goland and then perform the linting uh cleaning is also similar for uh testing.

B

uh I uh like before testing. It runs a simple go test in the verbose mode, and uh currently it supports only testing for the cli, because rest of all uh kubernetes, based and uh like some discussion, is needed on how to include them in the make file currently so currently only for the client is present and for prepare for pr what it does. uh It first uh formats the code and then links the code and then checks whether there are uncommitted files or not.

B

So, for example, let's say uh I want to lend the code, so I just uh type out make link, it will install uh google and it will link since it was already linked. There wasn't any changes in the code, you did it: okay, okay, there were some changes, so here it links the code and shows all the errors and make format it will format the code and uh make prepare for pr. It will perform the lend format and check for uncommitted.

A

Files a little part that could be improved here, because I just see all the errors uh that are turning up with our code. You can actually tell go lint and go thumb to only check for files that have been modified, similar to what you did with the git div index command. Here, if you want I'll comment that on the pull request, because then it will only check the files that are part of the pull request.

B

Yeah sure that that would be, I guess better, because it is truly overwhelming. So many you know, uh your changes have been shown at once.

A

Yeah also we're not going to fix all the old errors anyway, they will be.

B

A

We touch the file.

B

Yeah right cool, so uh this was it I had. I have another pr open, but it hasn't been reviewed, so I may be presented in the next meeting. So uh do you have any questions for this.

A

Thanks of, of course, for the pull request- and uh I think uh this is a good start uh for us- that we can extend the makefile afterwards for integration tests and such.

A

We also had a contribution or a contributor that tested. I think it was david who isn't here, uh but he tested uh captain in kind so kubernetes in docker. That would probably be a very nice uh point for us, then, to extend the make file with kind and have integration tests in kind.

B

Yeah sure like uh currently, it only supports a cli for everything for uh like testing and all the united states. We can extend it to all the services as well yeah.

A

All right, I'll I'll, add one more comment uh because of the uh thumped and lint uh story that I just told, and then we can accept this. I guess all right. Thank you. Thanks for the contribution.

C

A

Okay, so I guess we can hand over to uh ankit uh if I pronounce your name correctly. Hopefully.

D

Yeah yeah hi everyone, uh I'm makit, I'm currently working as a full-time devops engineer at recipe I'm from india, thanks for inviting me to the community meeting. uh So recently I've been working on captain cli uh I have made. Let me share my screen.

D

Are you able to see right recently, I'm I've raised two pairs, one for adding a feature to export, endpoint and api token. So this is a feature request of this issue. uh Captain cla multiple contacts like config, so this issue is currently promoted in community videos, so I haven't uh take over it completely like I, I've been picking some of the definitions of this issue, one of which is to introduce a command to export a current conflict. Current api token and end point so I'll show you uh right now.

D

So this is the current version that we have uh 0.7.1 uh when we use this, when we try to export the command, it shows, no export flag is not found, so uh I've made a pr to add the support for export. So right now, if I it's currently my developed version of captaincy.

D

So if I run this command now, it will export the endpoint and api token that I can easily get it out from my community secrets, but but it's good to have a flag that can easily do the hard working do the hard work for us. This is one of the issue that I've raised up here for and another one is. There is a bug.

D

I have created a comment, so there is a bug in uh like installing of captain uh captain control player on kubernetes cluster, so right now, when it checks for the cluster configuration, uh if you say, uh if you, uh if you didn't enter yeah, why it keeps on asking you which it keeps on asking you in finite time uh I'll give you I'll show you.

D

If I, if I say no, it will keep me asking this if I want enter anything- and it still keeps me asking so- this has been fixed uh in this current.

D

D

If I so, you know it will stop the installation, so this is a this is one of the bug that I have encountered while installing captain- and these are two of the uh for contributions so far, I'm made to captain cli and I'm still doing I'm still working on few of the issues that has been open recently and raised a few pr's looking forward to contribute more to the organization and as well as to more of the cncf projects thanks a lot thanks.

A

Thank you. Thank you. Any questions.

D

Yeah any questions, no, I I don't have any questions.

A

It's actually a funny story about the about the bug that you found. uh We must have recently introduced this because before zero seven, we we asked the user to enter credentials for google or aws or whatever, and then you were asked if they are correct and if you entered no, you could ask again and enter them again, so we've removed this functionality and since we removed it, you end up in this infinite loop, so a very nice catch. uh Also, thank you for bringing this up. Writing an issue.

A

Writing a bug issue in fact, and fixing it by yourself. That's a really nice contribution, or both things are really nice contributions.

D

Thank you christian. Thank you. uh I haven't updated the dogs with the export flag. I will make a pia for it as well.

A

Yeah, we will look at that, although not today sure thank you all right uh who's next, uh a new cool. I hope I pronounced this correct.

E

Oh yeah, that is good.

E

So uh should I start.

A

Yes, which, yes, yes, please.

E

Cool so hi, I'm an adaptive student in india. I just start contributing to the project and uh I will start with the pull requests I have open.

E

uh I don't think I should go to the one that has merged already so I'll skip over, that I didn't get a chance to put down the dots so I'll pull them off.

E

So the first pr I have open is uh regarding the issue where we want to print the version of the caption control plane in the cluster like along with the cli. We also look at this, so in the beginning, I noticed that there was a function that I could use.

E

I thought I could use this to fetch the version of the server, but then later I realized that uh after I noticed a comment on the issue that we should use the swagger version, and then I realized that I cannot use this because, like this function is called when you try to upgrade the helm chart and you can specify the name space that you want to upgrade in in the upgrade command.

E

You cannot specify that for the version command, so I've updated this to use the swagger, the swagger version, which is like we already have a function that retrieves that. So that's the state of this pr.

E

If there's something that, if there's something to discuss, I can, I can do it I'll, let me move to the next one.

A

I think I'll have to take a look at it. uh Thanks for the changes that you made, um that's actually a good catch, that we don't support the namespace and that you changed it to the swagayama, because I was actually thinking. Oh, if you can reuse this function, that's also great, but yeah I'll. Take a look at the at the changes as soon as I can.

E

Thank you. uh The next one is the pr where I add this tool called pluto, which uh parcels demand the kubernetes manifests and tells us if they're running back to their vp versions in views uh in the beginning. I actually used a direct link to the to the archive and then, but that I thought that maybe we want to like we would have to change the direct link whenever this new version, but so I used proof, but then now I think we would prefer to use directly install that button.

A

Yeah, if you, if you can install it directly, we do that for almost all our tools like helm and cube ctl and for a ci script. That's absolutely fine! Okay,.

E

Cool, so I will update this uh in some time today.

E

The next one is, uh I was there's an issue that says we should also be able to allow yaml qris like if I want to send if I want to use a ship shipyard configuration that is not on my local disk. I want to be able to like say that shipyard equals somewhere. like some website. My channel and uh I have put this in, but then I'm not sure exactly how to determine whether the flag is a url or a local path.

E

So I use a package called go validator, but I mean I'm increasingly dependency here. So I'm not sure if this is like the best way to go about this.

A

um I think we'll have to take a look if the dependency uh is is okay, uh usually we're fine with new dependencies, but I think we should just take a second look. uh Also, uh I'm not that familiar with that dependency. Maybe florian has more knowledge, so florian. If I can hand over the pr for you to review, that would be nice.

F

E

I spent some time trying to understand how to best do this, but apparently there's no like clear solution. How you tell whether the string is due alright, like there's a bunch of regulators, but I don't think they always work so for now I use dependency.

E

Okay. I just had one quick question about like this issue is unassigned to me, but I was just going through it before I decided whether I should get like get myself assigned and uh a question I had about this. Is we want to print if any resources that the user is trying to onboard?

E

So when you start onboarding service, they're, providing a bunch of resources right, we want them. According to the issue, we want them to use all the kubernetes recommended labels in those resources. So I think part of this will go in the google google's package.

E

So the part that goes in the kubernetes package is where we fetch all resources from the chart, and the part that we can possibly keep in cap in captain is where we iterate over all those resources and check if the labels are matching.

E

So depending on like what kind of information we want to return, what kind of information you want the user to see, I think, that's, probably a decision which we can use to split this between little packages like if it's just like we would you want to tell them that you know if you don't have all the recommended labels in all resources, then maybe this can just go into captain and into kubernetes.

A

I think we can discuss this on the issue as well.

A

I think andreas krima will also have an opinion on that, um but yeah a good point, and I see you have a pull request for kubernetes utils already so yeah yeah.

E

I uh I use the approach where I put everything in kubernetes details, but then I realized we might want to tell the user that you know a specific table is missing a specific resource. So I just put that on a draft until we discuss this.

A

All right, thank you. Thank you.

A

Cool, I think with this, uh if there are no more questions, uh we're already handing over to florian all right. Thank you just give me a second.

F

All right, can you see my screen?

F

Yes, perfect all right today, I have three pull requests to show you again. So, let's start with the first one, so the other requirement was to introduce a new endpoint within the api service which allows to trigger an evaluation and the reason behind that is first previously. This was done by using the generic slash events endpoint of the api service, where you could send a complete start, evaluation event that was a little bit uh complicated and we wanted to make it.

B

F

To trigger an evaluation, and also it was kind of difficult to get immediate feedback, for example, regarding whether the project or the service or the stage you wanted to perform. The evaluation for was actually here. So, of course, the lighthouse service, as we've shown you in the last week now also returns that information, but still you would need to fetch the evaluation done event containing this information and therefore we have added this new endpoint and let me just pull up this weaker ui for the api service, and here we have included this new evaluation endpoint.

F

So this is reachable under project stage, service and evaluation. Of course, the project stage and service names are required. Parameters within the path and the payload itself for the evaluation looks like this, so you can provide a start and an ends time. That's the first option or what you can also do is just provide the start and a time frame. The time frame is, uh for example, yeah. Basically, the duration.

F

You want to to evaluate the service for so, for example, if you wanted to look at the at your sli values for the last five minutes, you provide the value of 5m to this endpoint and, of course, it's also possible to label your evaluation in order to to have them show up in the bridge afterwards, and this is done by providing this labels property containing all the keys and values that you want to use for your evaluation, and we have also adapted the cli to use this new endpoint. So.

G

F

Me just quickly pull up a terminal in order to show you the advantages of that. So here.

E

B

F

Let's just clear it and, for example, one one reason we did this as I've previously described. For example, if you did a typo in the project name, for example, or the service, and you were afterwards wondering why you didn't get any evaluation results, it was necessary to get the evaluation done event and then see if the error message in that case told you: if the service wasn't there or the project or the stage, and now you get this immediately.

F

So in my cluster I have the project dynatrace with the stage qualitygate, and I want to evaluate the service bridge which isn't there and, as you can see, I now get immediate feedback telling me that the service doesn't exist and, for example, if I do the same for a service that actually does exist, I just have to look which one is there.

F

So, for example, I have the lighthouse service within my project, then I will get the id of the captain event that was sent to the evaluation service and then I can use this captain context study to fetch the evaluation done. Events all right. Are there any questions about that? For requests.

F

Okay, if not, I will continue with the next pr, so this one was about fixing the current release, branch pipeline and yeah. Let me just show you the pipeline here, as you can see, it's all green now again and basically, what was necessary to adapt was because of the changes I showed you earlier.

F

We had to adapt the quality gates, use case integration tests, because previously, if we did, for example, an evaluation for a project that wasn't there, we validated the use case by fetching the corresponding evaluation done event and since no event is now sent out. In that case, when you want to trigger evaluation for a project- that's not here. Yet we got the immediate response from the api and that needed to be accounted for in the integration test, and now that has been yeah updated.

F

Now, it's green again and one other thing that I stumbled upon uh today is when we tested micro kubernetes in version 1.19.

F

We stumbled upon a bug that caused the helm installation to fail because of a connection refused error and therefore we have removed the test for micro, kubernetes 1.19 for now, and we've also discovered that there already is a corresponding issue on the micro cube and at this repository, so we'll keep an eye on that and once that issue has been fixed, we will integrate those integration tests again.

H

A

F

A

That uh well david, isn't here, uh but david basically introduced the 1.19 support uh so david. If you're watching this afterwards uh 1.19 works. uh It's really just that micro cubanitas has a bug so yeah uh johannes. We might have to update the docs about that. If I just think about it,.

H

That's true yeah, because, right now we we say that we support 1.19, but um that's a good point in a good catch. We should um I mean actually yeah.

A

I mean we do support it. It's a micro q, a needless bug, but.

F

True, all right, uh let's finish uh with my uh third per request. This was uh quite a small one. So if you recall the last meeting in the evaluation or in the lighthouse service- and we now also send back a list of event ids that were used to compare the evaluation results against and that also has had to be uh reflected in the in the spec in the spec repository and therefore I have updated the spec for the evaluation done event.

F

And if you go through that specification now you will see the compared events property within the evaluation details, and this is basically a string array containing all the event ids that were used for the comparison, and maybe it's a little bit easier. If you look at an example of that, so here's an example of the of an evaluation done event and there you can see here. We now have this compared event: property that contains all the ids any questions about that.

F

All right. If not, I will hand over to amin.

G

Thank you very much. um I'm going to present you uh three pull requests uh regarding uh enhancements in the bridge today. uh The first one is based on the one we saw right now from florian. um Now the bridge or actually the heat map will highlight also the compared events from an evaluation.

G

So um when you select an evaluation in the heat map, you will also see the ones that it was compared to uh slightly highlighted uh with a dashed border.

G

um The next one also regarding the heat map, is showing labels on the x-axis of the heat map.

G

Previously we had no details on the x-axis here and now we show the time of this evaluation event on the x-axis or if the build id is provided as a label, so a label with the key build id, then we use that value to yeah uh show this on the x-axis.

G

uh I will do a demo uh after I present my third request.

A

I mean the request you just presented: you had a have a backboard for that as well. uh The backboard is failing with the unit tests just.

G

Oh yeah, of course we'll have a look at that, so I will have to.

A

G

The back part and also update the screenshots in the documentation as well, is still on my to-do list. Thank you for that and the third one is also about evaluation tile. So we had a rework of the evaluation tile um since um actually that's that one.

G

uh Since the information of the evaluation tile, uh when we have a look at the old one was split here into uh two parts and the heat map was like in between and the the result was not uh yeah, um it was not not all information was there, provided we have a enhancement now here and okay. I don't have a screenshot here of the latest one, but that's the place where I can show you the demo of the improvement here.

G

So, as you can see in the bridge now we have here an evaluation. You can also see the three evaluations it was compared to slightly highlighted when I click through the evaluations. You will see like this. One was compared to that one on the most left side, uh since we just take the past once for evaluation, comparison and yeah. When you scroll down, you can see here also on the x-axis, the labels in case that multiple evaluation done events have the same name in the build id or also they were executed.

G

At the very same time, then yeah we will add, or that the bridge will add here account and uh when you click through the heat map, you will see the result uh down here. So this is the evolution, tell rework where you have the slo, since that could also change in between here. So you can yeah have a look at the slo file and you see the evaluation result with this core and also the limits for this uh comparison.

G

So, for example, if there is a pass limit, you can see uh that one and also if there is a warning limit, then you would see also the pass and the warning limit in case that it's in warning state. You would see both uh limits here. You see also the result, the evaluation time frame now with the duration, and you also have the info that this evaluation was compared with the last three past evolutions.

G

This depends on your slo configuration.

G

A

Any questions yeah the text compared with the last three past evaluations, is that dynamic, depending on whether you say, include all results with pass or warning or pass or, however, like this is a dynamically built string. I guess.

G

I have to check on that one, since I just saw when I click here. It should not say compare to last three past actually.

A

G

Because in this case, any information this will be taken from the slo file and it will say uh compared with three last past evaluations or just with the three uh with last three evaluations. So without the past, depending on the configuration.

G

But of course this count should consider the number of compared events in the list that is provided here. So, as you can see, this evolution had only two events that it was compared to so it should save.

A

G

Last two past actually.

A

I think it's okay, the way it is. I think we should just rephrase it like. uh I don't know, target uh comparing with last three past or whatever evaluations.

A

Because the target, that's the target, that we aim for based on the slo config.

G

That's it currently, it reflects the target. It's three past evaluations before the configuration is several results, including the.

E

G

Ones, and the number is three so.

A

G

Take the information from.

A

Yeah or you could use uh like the the what florian has shown and what you've already shown. Last week, you have the compared event ids in the payload yeah.

G

That's what I said I could use the length of that one. So.

A

G

Here two elements or just one element in here, then I could say it's just one uh evaluation compared with, but the information passed or it could be also passed or worn, is depending on this uh yeah configuration here in the slo, so yeah the.

B

G

Could be adopted here.

A

G

A

Keeps keeps looking better and better every time.

G

Yeah, improving and improving.

G

uh Yeah. Thank you very much. That's from my side, I'm handing over to johannes.

H

H

Actually, I don't have a pr or um or an issue to to demonstrate because it's still in progress or actually I had the first review of of my improvement regarding the documentation about the quality gate. Andreas already got uh or provided feedback on that I worked on it and but it still takes a second round.

H

This brings me now to the point that I will jump over to the working items, and here let me close that one um here we have a couple in ready for review, but this they were already discussed throughout this meeting.

H

Except of that one florian. Do you want to show us the polling for new services based on a dynadress tag? The next time.

F

Yes, please because currently it's in review and it's not been merged yet, but of course, I'm looking forward to show you this next week because it's a really cool feature.

H

Great all right and um then hopefully daniel- is- will join the next meeting so that he also can show his contribution in regard to supporting kubernetes 1.19 I mean, should we pull back the evaluation tile rework as we now discussed that we want to slightly change the number.

A

I I think we can just open up a new issue, because.

G

A

This one, this one is like done.

G

Actually, it's already merged so.

H

Yeah, okay, then, let's.

A

Let's open cool could be a good first issue.

H

H

Okay, then, let's take a look into the items that are in progress. The first one is about enhancement or improvement of the documentation. It's listing all installation options, christian and what's the status of that one.

A

The status is that I should inform andreas that he should help me with reviewing it okay, unless he already did that, and I didn't see it so yeah. I need to talk to andreas about it. Yeah.

H

Okay, that has a lot of review tasks right now, but yeah it's the case.

A

H

Because the same is true for for my issue. I also need feedback from him uh yeah in this meeting we discussed the make file and that there are one or more small changes required and uh yeah.

A

We we just said andreas too often, because he just joined hi andreas hi,.

C

My previous meeting uh finished early. It's.

A

Yeah, it's okay. We just blamed it all on you.

H

We just we were just discussing those two issues that are for the documentation and uh we would like to ask you for a review on that. One.

C

So, uh for the first one, if I can quickly follow up, um I already did the review.

A

Then it's my fault.

C

All right, at least I've extended the pr with one commit or something like this and yeah. The second one is a little bit bigger. I need him more time.

H

No worries, okay, then ankulou is working on that one. It's the include bluetooth to automate automatically check for deprecated kubernetes api versions, and then we have here one from um no here. Anukulu is working on that one, and on that one, two, all right. Thanks and andy.

A

I've left both of them on uh in progress, because there is some work still to be done, but they are basically almost done already in review. So I'll move them when they are going to review.

H

Okay, thank you very much, and then we have two. uh There are two pull requests and issues for the dinette sli service. Has someone an update on those two issues.

C

um The the pull request is already approved by florian right.

F

Yeah I had a look through it yesterday. I saw that you also had some questions. Did they get answered already.

C

They already got answered, so um I'm fine with merging. So I didn't had a look in the source code, but all my questions are answered.

H

Is there? um Is there one pr that covers both issues? Let's have a look.

C

This br even covers me issues more.

H

Issues and this one increased test, curvature, update, documentation, feature flag and reduce logging.

H

Okay, it's approved yeah. Then I think we are ready to merge it by tomorrow or let's have a final review.

C

Should we merge it um even though the github action failed, the refill dock or house zip code.

A

Yeah review dog has some comments left on it, uh but I think that the one that's failed is sonar cloud and I think.

B

A

Some duplicated code sonar cloud is very strict, but it's not mandatory to pass so we can merge it unless you want to. Unless you want to improve on on that sonar cloud issues I mean yeah, so sona keeps track of them anyway, so we can always fix them.

H

Cool, I will leave it as it is, and let's merge it by tomorrow, then I will skip the signed and committed issues because we already discussed them and yeah. They are waiting for getting implemented and I just want to jump over to the backlog itself.

H

Here I have identified a minor issue, a minor bug issue in the bridge, because when I click on the captain api link, it forwards me to an end point that has a slash at the end, and this should not be the case because then I get a page not found by removing this um slash. Everything works. Fine, I think it's a quick fix and as we are touching this part, I would like to change the order of the links to have.

H

It then also um nicely ordered where we have the yeah api, then the cli api and.

C

Click all right, a big shout out to this small feature. It's so convenient now to simply copy the auth command yeah. I use it daily.

H

Super convenient true yeah. I think this is also a candidate for a good first issue, because it's just removing the slash and changing the order of the link is someone out there who wants to work on that. One.

A

H

A

We should label it and leave it in the backlog, because we have so many people asking for for.

G

A

G

That's what I wanted to say: you could label it with good force, first or hackathon, or some clue.

H

uh Yeah hacked over oktoberfest.

G

Oh, there is no.

A

Probably you should do that just yeah just create it. Oh, it's! The right, color, even like cool.

H

All right yeah, then, let's jump to the second issue, that's related to the bridge a little bit a bigger one, because what we want to provide the user is a new menu item which is called integration.

H

And when the user clicks on that menu item, he or she should get an explanation of how to use the cli and how to use the api with all the instructions to download it and to authenticate and then also get to access the api and further down. There is also an example: how to use it, for example, to trigger quality gate.

H

This is kind of static content and then further down.

H

There is a feature flag that says: uh load more information about integrations and what- and here is then also more information about this feature flag, because what we want to build is a polling mechanism that loads content from from a third party tool into this ui, because we want to show them the user which custom integrations are available, and you can imagine that the list of integrations is growing and growing as more and more people are providing in building integrations and we need the flexibility to customize this content, and this is also the reason why we want to dynamically load.

H

This part from the outside and yeah. The feature flag is, is enabling disabling this feature.

A

H

Yeah true, we also need to be gdpr conform, and this means that we need to inform the user that in at this part, we are pulling information from from somewhere else, and he or she can turn it off when the when it's not not needed.

A

Is it enabled by default, or is it disabled by default.

H

A

H

A

Well, I think it should be disabled if it's gdpr related but yeah in the screen. It obviously looks like it's enabled, but maybe we should clarify that in the.

C

H

And the issue itself.

C

I would have a question to yeah, I mean: is it by default, enabled that we check for new versions no.

G

No, you get a notification from the bottom if you haven't used the feature yet where.

F

G

Opt in and opt out, and once you choose one option, then you can change it in the user menu in the top right.

H

Thank you I think to be gdpr conform. We will disable it by default yeah, because then the user has to take an action, and when he toggles the feature flag, then he agrees on doing that.

H

All right, yeah here, are the tasks that need to be implemented for this issue and also the content. The static content that should be provided right here, as well as the dynamic content that is then fetched and visualized.

G

Yeah you can assign that one to me actually, I'm on I plans to be on vacation next week, monday and tuesday. I think I will have time for that. One.

H

Cool. Thank you very much through.

G

The rest of the week.

H

Okay, uh well then, we still have this meta issue, that is, for the documentation, as there are a couple of things that need to be done before releasing 0.72.

H

It's yeah improve the installation structure for a dynadress service, then double check that the documentation does not contain distributors as we move them in most or for from for most of the services.

H

We move them into the deployment of the of the service itself so that it runs as a sidecar and then here I want to point out that, as as we already discussed in this meeting, we should we should also update the screenshots for a bridge, especially for the download download link, the enable disable version check feature and, as we saw today, the cool enhancements for the evaluation tile. This should also be reflected now by the documentation.

H

All right yeah um should we should we keep it like that, or should we assign this issue to.

H

A

I mean you can assign it to me if needed, I'll, be release manager, so I can keep track of that and run to people. If I need anything.

B

If I can do it.

H

All right thanks a lot, then um that is further down.

H

ah Okay; okay, thanks for for bringing in that one, um it's as we discussed in this meeting the improvement of the bridge where we want to show the true count of compared evaluations, in other words, use the count of or use the length of the list, and then I show it in the text or in the in the label.

H

I agree, that's also a good first issue and then maybe relevant for a hacker heck of hacktoberfest. I think we will leave it as it is yeah.

H

What I was looking for was actually this issue, uh because today I got um or um christian hackman pink me that he has no time to work on this issue anymore, but he had already.

H

He made good progress, even though he could not finish it, and this is the reason why I want to bring it now in the backlog again also to show it to everyone who is joining this meeting, that there is a feature available, it's for promisers and their goal is to change the promiser service in a way to not install promises as part of the service, but just to um reference an already existing promises. Installation.

H

When you have knowledge about promises, then please- and you want to work on that- one. Please leave a note there and then we will assign you to that issue.

H

All right, then, last but not least, let's open the release checklist for 0.72. I think this will. This will be the focus for the next next days.

H

Yeah um christian, you will be the release master of the. uh After of the release.

A

Yeah I'll be the release manager.

H

Okay, thanks thanks a lot.

A

More better term.

H

Okay, yeah uh the release manager and, as we do it as usual, um the release manager is keeping an eye on on on the progress.

H

But whenever someone has time left and wants to contribute also in the releasing process, please assign you to a task by just leave, but just um by just providing your git handle there, and this means that you then reserved the task for yourself and you are then responsible for doing all these things like getting all feed all pull requests merged, then cleaning up inactive branches or and delete them also check the release, notes and maybe ask for feedback and also inform the release manager about the release notes, because their release manager will then be responsible for exact approving those, and when this is done, you can then trigger actually.

H

You can then create a release branch and also inform that the person or the release manager that the branch is created and you are also taking it yeah, taking into account the proper.

H

Yeah, don't want to go through this list just want to make a shout out when someone wants to contribute in the releasing process. Please feel free to to show or to leave your kit handle there and then um you're welco we would like to. We would like that. You will then um finish your task.

H

All right, that's from my from my end as someone questions.

A

uh Just a note, if you're working on any of the issues or if you plan to work on any of the issues, please always comment on the issue. First and let us know and uh wait for us to assign you. uh This is just to avoid that. Someone else also maybe thinks that they want to work on an issue, and then you have two people working on the same issue. It's like yeah wasted time.

A

If two people do the same issue, so just comment on the issue and we'll assign you and also for the issues regarding community bridge, please be aware they are kind of reserved, so we'll make a decision regarding the community bridge, mentees and uh we'll let you know uh as soon as we can.

H

And what I figured out today is that it's not um that it does not work when someone refers to someone else, like christian did here for anukul.

H

Really the person who wants to work on that issue needs to leave a comment there, so that I can then uh assign you the issue, because now uh it's not possible for me to assign this issue to anukul.

A

Yeah that that's, even though there is a pull request link that is made by anukul. So I don't know what github is thinking.

H

Thanks all right: okay, we discussed the working in progress. We had a brief discussion about the release checklist and we talked about the next print. I think we are good to go for the next week.

H

All right all right, then,.

B

H

For joining this meeting, see you next thursday at 5 p.m and have a nice rest of your day. All right, bye, see you bye thanks. Thank you.

A

Thanks everyone for contributions, bye, bye,.