keptn Community, 20 Sep 2023

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Keptn Community & Developer Meeting - September 20, 2023

Description

Meeting notes: https://docs.google.com/document/d/1y7a6uaN8fwFJ7IRnvtxSfgz-OGFq6u7bKN6F7NDxKPg/

Learn more: https://keptn.sh
Get started: https://lifecycle.keptn.sh/docs/getting-started/
Join us in Slack: https://slack.keptn.sh
Star us on Github: https://github.com/keptn/lifecycle-toolkit
Follow us on Twitter: https://twitter.com/keptnProject
Sign up to our newsletter: https://bit.ly/KeptnNews

A

Yes, I, like the spirit, if you.

B

Don't mind I share my.

A

A

So I don't have much news for the community blog today. I just wanted to point out that Stacy did a noome job and uh she put the latest meeting the new meeting we had for new contributors where Andre was explaining how to set up the dev environment and uh she was so kind to also add the time time stamped.

A

So if you are interested in anything like how do I set up my GitHub or how do I start the test and stuff like that, it's in here you can check it out and uh if something is missing, maybe this could be topic for the next meeting. So also feedback on that is well come and do we have anything else for the community block.

C

We don't have. None of our new contributors are here right. I was wondering if any of them got started with this, but yeah.

A

What about the documentation, then, since you're talking about.

C

I don't have much either anybody have anything they're interested in. um We could take one quick, look at one thing can I share. My screen will I take it back.

A

Yeah sure I I see in the meantime that there is an extra person on the documents. Oh.

C

Is an extra person on the documents.

A

Yeah, this is a.

C

uh On what documents I'm confused.

A

C

Oh on the minute somebody who can't get into the meeting good who got to the minutes.

C

C

A

Okay, uh sorry for interrupting you m.

C

No, no! That's what, let's see if Aran gets.

D

A

Hello Jennifer.

C

D

Jennifer, hello, hello,.

A

C

D

C

You we don't have a lot going on. Do you have anything you'd like to talk.

D

D

Actually so far, I don't have some new idea about about this. So this is not my at this time to join so I want to to Lear from you. This.

C

Time: okay, um what are your interests.

D

Do you want to.

C

Are you interested in contributing or using or.

D

Actually, maybe more using because um our company C it's time to using Captain for our Cloud release, automation, management and actually and we starting a plan to use Captain version, one which is um the old version of Captain. And now you are using the captain left cycle management, which is the new version. Actually I think is it's kind of evolution um comparing to other other version, so there many chance so I'm studying documentation of the captain, nle to K and uh I thought.

D

I think this is a very good solution comparing to verion one, it's more flexible and more more comfortable with many different tools. So I think this is a good solution and uh and I'm going to to do piloting with my with my comping and project um plan deployment and some kind of testing, pre and post deployment task together, and uh the other thing is that we are using a datase. So we want to integrate with Captain is d t to to build our pipeline for Le management.

C

Oh good, what are you using for your deployment engine? Are you using Argo or flux, or something else.

D

uh Our company is using. My company is using a flex Flex in the yeah Flex for deployment in the junk for be Pon.

C

D

C

So how far have you gotten in your mation.

D

C

How far have you gotten in your implementation.

D

How far um I think, um maybe um not the fun time to focus on this one- maybe uh maybe in total I- think it's maybe around one month, maybe because uh we also do some do. We are also having an T to do so. This is not parin testing our side, but we want to have a to to to move to move more efficiency efficiently on this kind of parting. So in the future we are going to spend more time to to on Captain.

A

It's amazing: okay, we have the help Channel, if you want any support in your proof of.

D

A

To drop us slck.

D

A

Thank you and uh I. Don't know if you were there in the previous meeting, but I think Florian a couple of meetings ago uh showed uh the newest feature that we will release, which is about U, SLO and SLI. So this is yeah what will be the same as Captain B1, so I guess you're.

E

Interested in that too,.

D

Yeah all right, yes,.

A

And uh maybe we should welcome also Arian.

F

A

I, don't know if you were in the meeting for the dev contributors, but uh there is the video posted now. So if you want to contribute to the code, maybe you want to have a look at this. Andre did a good job, showing everything to do to set up your own.

G

A

Okay, I diverge: uh do we have anything else we want to discuss for the community, your documentation.

C

Block okay, I'll take a minute for documentation actually because I'm going to pick on Jennifer, because oh but I can't share, could.

A

I sh I will stop sharing for you.

C

Okay, here you go um because I have been thinking about we're working on stuff to get. People started like getting started, documentation and I'm, realizing that we have some issues, so I would love to hear somebody else's opinion and here's exactly what I'm looking for.

C

um Oh come on, and now we have to be slow there we go okay, so we just recently added somebody did what I think is a brilliant, getting started piece here for, but this goes over metrics and observability. It does not get into the life cycle management stuff.

C

Now we did have we go back a couple of releases. We did have another exercise that is very heavy on the we called it end to end that probably wasn't really true. It's heavy on the life cycle management and getting the tasks and stuff.

C

um But it's not um one of the flaws to this is that some of the more difficult things to set up they just have a script that you run so you so everything gets running easily, which is nice, um but it doesn't necessarily so actually I'd like to hear from you um uh Jennifer what.

D

C

Are you looking for in the docs to get you started.

D

um Actually, I I I haven't written doation for on the installation, a startup and the on a concept to introduce about left cycle management such as um the captain, Tas definition, Captain, Tas, Captain, AP Captain work, all this kind of key concept so and the AL so about a component diagram. How to interaction with between each component for KT, so I can get on some overview understanding of Captain KN cycle taret and um and for this one I'm not looking for focusing on this Captain task. Yes, pre and post deployment task here, because.

F

D

Want to integrate with the for it's it's um sorry, S, no and S definition to integrate with how you re it. Our.

C

Task go back to um so. Have you found this uh little guide.

D

C

Working with Captain tasks.

D

C

Okay, and is that working for you, I I'm, asking honestly because I'm the writer and I work with these people who know all this stuff so.

D

um I think it's quite it's quite good documentation. It's easy understanding on expression is good to to me I'm, not native English speaker, so, but it's very good um State out on um on a how to say on um key key key features of of Captain pass. So I think you to me.

C

Okay- and uh that's that's really good to here- yeah and I, your English impresses me it's much better than any of my languages other than English, so no need to apologize.

D

C

Much but I would, if you find things that aren't clear, I would love it. If you just ping I know people always feel like they're being rude, but it's the most helpful thing, because we can I've got great people to review this stuff as to whether it's accurate, but whether it answers your questions. These people can't tell me um and we we make a lot of improvements, because people come in with a question on.

G

C

And we're like, oh yeah, that's not very clear in the documentation is that we knew it. So um are you using customized.

D

C

D

Also using some customized full Department, yes,.

C

Okay, I, don't know if you found this. um If you go into the life cycle.

B

C

uh Repo um in examples and Sample app and version three, that's actually the um the exercise that was in that old, getting started that end to end that we had that either needs to be replaced or have some work done.

G

But it does and the.

C

One my one, the other problem I have with this is it is using customize and I realized. We.

G

Haven't really.

C

Talked about customizing the dots, but it's obviously the way that the good people, the smart people, people do stuff so, but this is using customized so that code example might help you with some examples.

A

G

Yeah the whole example.

A

Folder has a make file and you can rely on that to have a.

C

D

Deployment information.

C

ah There's the make.

A

C

A

It's not super documented, but uh yeah. It's straightforward in a sense that it has install then run of the various part, and probably the red me has a little bit of information, but for sure it can be improved.

C

uh Yeah but I think you're right. The.

A

Ry I meant the Ry.

C

A

C

In the examples yes I'm out of examples now aren't I yeah. um Here we.

D

C

D

C

There's read me: there's a sample application and yeah there's a little bit of explanation. There.

D

Okay, actually, by the way, I think the captain toid documentation, is much better than version. One I think version one documentation is is some is having some C issue really on.

C

Side so we're getting better, that's good to know.

A

We're learning something.

D

C

So we look for do keep us posted um and we'd love if you, if you run and if you're always welcome, to bring stuff to the these meetings, sometimes they're full, but a lot of times like today. We've got tons of time and we'll help you debug or whatever you need so. Okay, I bored, everybody enough with documentation.

A

Let's go back and do the real.

C

Stuff go for it.

A

Co, if you don't mind, I share again my screen and yes, we move on.

C

Let's refine part.

A

Which should be refinement, I checked before the meeting, and we have two tickets to refine. One is from floran and one is from Rashid uh who wants to.

E

Start I can start.

A

You want to share or.

E

uh If you just open the issue should be enough.

A

I was prepared.

E

Perfect okay, so this is a little extension for the Prometheus provider, so, for example, in both the data do and the dinat TR providers, we support um making use of credentials for accessing data, do or Dino Trace, uh while defining the credentials in a secret. uh This is currently missing from the Prometheus providers, so here we only have the possibility to use the URL of the Prometheus server, uh but to make it more available for more customers uh who might U have a prometheous instance. That's secured, for example, with user password authentication.

E

We might want to add a support for that, and the way this should be defined should be yeah similar to the current implementations of the data. Do and uh datra providers.

C

A

So basically, we need to add handling of authentication. We can check what is happening for the other two providers for inspiration, and then we make unit test.

F

A

Else we should is this easy to test locally? You.

B

E

uh Well, maybe now, since we have the uh mock server set up in our integration test, uh we could also look into verifying whether we get the expected credentials on the mock.

E

Server might at least be worth looking into. If that's.

C

Possible and could I have a tick to review, update the documentation about Secrets, which currently don't mention this little flaw with Prometheus, so I'm I'm skeptical the quality of that dock anyhow. But let's make sure we get it right.

A

Now this would be probably fitting in the part where we talk about the providers setup or.

C

um That we have a section on.

C

Secrets, okay,.

B

C

It's buried in the tasks Guide chapter and I'm thinking it probably should be out on its own, so it sticks out there in what would be user guides. It's currently implementing, but that's soon to be called next release that will be user guides. But if you go in there and working with Captain tasks and that we do parameters and then Secrets.

A

Okay, but um these are for the task and uh the authentication in our case would be for the connecting.

C

With for the providers? Okay, we don't have covered, which we don't even have Docs so.

A

Do do we have nothing for provider set up apart from the crd.

E

Reference here in the C metrics.

C

E

I, don't think.

C

No because that's what because I can't I asked a couple of times, you know, I I wondered I, knew the secret Secrets was for tasks.

A

C

I knew there were secrets for things, and was this all the same. It was like yeah, yeah and I'm. Not I may even have an issue out there. Let me go I, have a doc issue to look at the secret stuff and maybe I'll I'll just make that active and mention this PR.

A

Yes, but for for now I guess we could add it in here where there is a documentation for the.

C

Right or figure out a.

A

Providers yeah.

C

We don't have a.

A

Specific documentation for the each provider I see.

C

Yeah that and that that may be that's been another question of mine, whether we should and I don't know what to do about it. But um let me pull out. I have I. Think I have an is an old issue out there about secrets. So I'll do that and I'll just link to this issue, and so.

A

Something general 2128.

A

um This could probably be just for now updating the crd, I guess crd.

C

A

C

Okay, what CDs it's going to be.

A

In uh the provider metric provider.

C

A

Should we refine this with the size or it's just.

B

Maintenance now would say it's a new feature, but we can refine it. um Do you want to use the pocker, or should we just.

A

Let's use the chat.

B

Let's use the chat.

A

Let's uh improve or feature usage, everybody writes uh small, medium, large, I guess and when I say it, prenter sounds fun. You ready me ready, enter. Okay, it's an.

A

B

A

D

Find and little.

A

Cow yay: this was fun thanks, Flo.

E

A

The next one rash do you want to talk about it.

G

uh I didn't have much to talk about this. We talked about it in the last meeting that we should have new these fields in the for CU Captain metric uh I just wanted to ask if we could add this as a good first issue for new contributors to get started.

A

G

There is already somebody.

A

G

Yeah I think is interested.

C

On this, oh that's Arian who's. Here, isn't it.

A

C

Exactly talk among yourself.

E

So, for me it would be fine to add the new first uh good first issue here.

A

A

That's and Arian, are you still interested? Can I assign you.

F

A

uh Do you have anything you want to ask about.

F

A

I signed myself out of Abit anything you want to ask about this since we're.

F

Here I have to look at for I'm, currently working to know about Much More Much About to Captain right now, because I'm new to the community.

A

Okay, so have a look at what Andre posted and yeah. Let us know if you need any help with this.

F

A

Hold that was easy, I think we finished.

E

A

Y, not much more.

A

Here anybody wants to say something before we.

D

Leave I have long CR actually than yeah, so so I, Char, M and S. What that S and M stand.

A

For u I there was some lag I didn't understand. What does it stand for? What.

D

Yes, for for not chart you you, someone ty, not chart in in m in.

A

ah Okay yeah, so we have when we refine ticket, we use T, T-shirt size, so small, medium large to decide.

G

A

It is, and I was too too lazy to set up a proper voting.

C

D

Okay got it: we just use that okay.

A

And uh we we are pretty proud. Do you want to wait?

A

Yeah, let's see if we have one refined one.

D

So so, how long is for your for each Sprint release? You are using your Sprint right for for to find issues.

A

uh Are we using Sprints yeah? Usually they are Sprints of two weeks right but uh weeks we are not well. What do you say? Are we good at releasing? We have now a different release system.

E

Yeah, so we don't really have a really fixed release interval. So mostly that's whenever a bigger epic is completed or when there has been a bug fix for one of the already released.

A

Versions, yeah, but basically now we are a monor repo, so each of the services is is released.

A

Separately, uh we're going to soon have also separate Helm charts.

D

C

A

But the next release is coming soon. We are pretty close to the.

D

A

G

A

You can track what we are doing and what we're working on here in the projects.

A

And yeah I think we miss only documentations and examples for the SLO before.

A

Release y I think.

A

Else, if not I would stop.

A

Here and I was with my hands up with AO.

C

A

A

Day see you next week, I guess you have time cool thanks. Everyone excellent.

C

G

You bye, bye, bye. Thank you.

G