keptn User Groups, 21 Dec 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Keptn 2021 Christmas Update - Keptn User Group, Dec 21 2021

Description

Oleg Nenashev and Andi Grabner talk about the key Keptn project and community updates in 2021.

Slides: https://docs.google.com/presentation/d/1Mvh04uvzUaEgfjggRsAsEYnM2kndQwnyMYlMBJ68vQY/edit?usp=sharing
Join the Keptn Community here: https://community.cncf.io/keptn-community/

A

Okay and then the project update, so uh 2021 is almost over. um By this time we had 10 releases of captain. Three of them were your major baselines and yeah. I'm pretty sure that we will have another really soon.

A

So thanks a lot to all teams working on captain and on integrations because yeah, the velocity this year was really high in terms of the number releases shipped, a number of various features, dependency updates and integrations. So it was really great and thanks a lot to everyone on this call or who watches it um right. Now we have uh more than 70 instances that submit usage starts. There are also some instances that they do not and yeah. Hopefully the number will grow considerably uh over the next years and yeah also to mention.

A

uh According to our github organization. This year we had more than 80 contributors, it's difficult to complete because we scattered that multiple github works, but this is just good contributors. We also have contributors who create content.

A

Writing newsletters, submit quality issues, submit the usage studies, so the community is growing and of course, we have many users joining the slug. So currently we have more than 800 participants there and, let's see how it evolves.

A

Also, for me, the key highlight for captain in this year was growing extensibility. So there were two generic services introduced, a job executor service and webhook service.

A

Also, there were significant updates in extension templates, so hopefully, now it's much easier for users to develop new extensions, and we have seen quite a number of them created this year, including uh by end users of captain who wanted to have their integrations.

A

So it definitely goes in the right direction and when we have captain as a kind of generic orchestration engine with a capacity for running services with custom integrations, uh it will be really great. And if you see any integration mistake again, it's a good opportunity to submit a github vision.

A

Another highlight for me this year was that now we are represented on artifact hub, so captain itself and all project services we have uh listed uh on artifact hub, which is basically becomes a default platform for kubernetes, and uh if you want to find something, if you want to get embedded documentation, if you just want to quickly navigate between projects and their dependencies, then artifact hub becomes uh one of the entry points for you um also. The highlight that is, we actually get more and more services represented.

A

So, for example, here you can see github actions webhook, so it's not a service on its own. It's just a webhook extension and a piece of documentation that shows how to use a webhook service for triggering github actions. uh The same way is possible, for example, for slug the results documentation how to implement slack with webhook services and yeah.

A

It becomes uh quite handy too, for adding additional integrations, because uh if you use rest apis or if you use cli tools, which job executor service, you can actually integrate a lot of tools with captain these days.

A

So yeah. If you want to know more about web hook service- and you did a great uh introduction in five minutes- I believe it's based on slug right in there.

B

The video out there.

A

Yeah and also there is the same demo for job executor service. So please take a look, uh but for me it's definitely key highlight in terms of the features and my question to andy, johannes and everyone else on the call. What is actually your highlight in terms of features? uh Do you see any other major updates that need to be mentioned today.

B

Yeah, I think, maybe additionally, um a big improvement happened this year on the heat map on the whole slo evaluation. The way we visualize sli slo results. There was a lot of great feedback from the community on how to make it more interactive, uh but also how to just uh better visualize the heat map. I think that's it. That was actually a big one for me,.

A

Great any other major updates. Have you missed those features.

B

No, I think uh I think, that's really it uh at least for myself. I know johannes had to drop, unfortunately, because they're really the top of the hour, so he's no longer with us here.

A

Yeah understood so still, there is a lot of updates happening in there. We had a major dependency updates. For example, mongodb was updated in 11th version, which requires some additional migration changes. So there is a lot of things happening under the hood to ensure that a captain is more scalable and that it fits many environments. For example, they will fixes for open shift for additional integrations, so yeah the project definitely keeps growing, uh and that option keeps going too other highlight for me is new tutorials.

A

Actually this one of the topics, I will be looking in going forward, but uh when the year started we had just six tutorials. I believe now it's 10 and there will be more. Hopefully this additional updates. We will be able to provide a great uh experience for those who start with parameters and to those who also want to do common integrations, uh for example, with sleep mascaras with jenkins, maybe with backstage so whatever we support. uh Hopefully, we will be able to introduce many tutorials here so that everyone can easily get introduced to these integrations.

A

Another important highlight is that yeah this year we celebrated one year in the cloud native computing foundation. um Captain is basically under the umbrella of our attack. Application delivery there. uh He starts up this for captain that presents they believe every month or two there and basically this year, one of the important objectives- and one of highlights is that the captain qualified for incubating status. We passed internal due diligence, we submit applications to the cncftvc, and currently we are waiting for decision so hopefully by the next cube column. I will have updates on that topic.

A

Fingers crossed. We also participated in a kubecon and yeah. I have slides somewhere later, so, basically, andy jurgen and other contributors represented at the different kubecons. I believe they were coney sessions, also office hours hosted from kubecons and yeah. Thanks a lot for doing that, then the captain became more active in the continuous delivery foundation, especially in the cdf of ncc. There is new standard, the cd events, which is basically based on cloud events and implements continuous integration and continuous delivery.

A

Eventing and actually captain uh team uh was one of the contributors there. The standard also takes into account how captain events are organized and maybe later, as we discussed, there might be even more integrations and maybe specifications for other events. Captain users, for example, for life cycle uh currently captain is represented in the cdftoc, so they will be more communication and there are discussions about collaboration with other projects like dicton or jenkins, for example on the city events, adoption and maybe for some capital integrations.

A

So let's see where it goes, and we also participated in city con this year and hopefully we'll participate next year in june 2. Maybe we see one extended agenda compared to what we did: okay, uh sneak peek and captain roadmap, so this is what you can see on github, as I mentioned today.

A

One of the items uh upcoming in the next release would be a role-based access control. It actually consumes a lot of time and a lot of effort. Also there is support for zero time upgrades coming. uh There is support for managing captain uh through the bridge, including various configuration functionality and also triggering of sequences.

A

So it becomes uh quite handy, and hopefully it will address some use cases, another update for the roadbumper that now we have documentation and community items added here, mostly for traceability purposes, but yeah. I believe it's a right approach to have everything under the single groove, because when we talk about captain community, it's not just code contributions, it's a huge system and we want to grow all parts of this ecosystem.

A

Okay, speaking of the community, uh any questions any comments.

B

No not from me.

A

Okay, uh so yeah. uh First of all, I would like uh to thank all uh captain users. We have a lot of them. We got many adopters. This year we had many presentations at captain user groups.

A

I believe we had 11 user group presentation, this year's- and uh there were multiple key studies published, for example, for uh reference and for vitality group thanks a lot to 20 for preparing this content, and I believe that uh our list of adopters is going to grow, and actually one of my topics for the next year is to ensure that uh our adopters in d actually represents uh the actual state, because now we have how many ten companies today, I believe so everyone who uses captain you're welcome to submit uh patches here or just contact me.

A

I will be happy to put you here- maybe even put some logos and but anyway, the adoption is growing, and this is something very important to see for the project.

A

And yeah this year we had only two rock stars, officially announced so kartik and alvin for litmus cause integration and again for more litmus house integration, including tutorials, including guidelines and yeah. We slightly dropped the ball on this program um in the end of the quarter.

A

Actually we have uh one uh uh captain rockstar terminated, uh but we haven't announced him yet so stay tuned, and if you want to nominate a captain user or captain contributor for some for a major contribution to the community, please do so because you would be happy to promote these contributions.

A

Okay, so yeah. This is why I missing slightly about kubecon, but yeah. We definitely got there thanks a lot to everyone who participated. uh Hopefully we will be able to be in person.

A

In valencia there were some discussions about doing captain community, and hopefully it happens- another update from one month ago, so yeah jurgen announced that he would be stepping down from some roles, including uh leading uh meetings etc. uh So uh I just wanted to thank jorgen again for the contributions to the captain project and uh yeah. Hopefully you will be back to the community in some capacity soon. So looking forward to that and yeah.

A

This is just a screenshot of one of our community meetings, so we got uh 14 people on the call and for me, it's a kind of achievement and we need to keep working so that we get more people because sometimes it's 14, sometimes it's two so definitely something we could improve, um but yeah, it's great that we have some people participating and it's nice so that we can meet, discuss some activities, answer questions and also celebrate uh major milestones for the projects so yeah. Let's keep doing so yeah.

A

If you don't participate in advent calendar, there are just uh two or three days left. uh They were special schwak giveaway yesterday and thanks a lot to julia for organizing all this effort, preparing content, debugging people to prepare their songs, etc.

A

We did that and it was actually quite fun, so you can find it on twitter and on linkedin. So this is all from me today and actually I even went over time. So thanks everyone who contributes to captain uh who uses captain and hopefully the next year, will be even more interesting full of new uh features. You know case studies and new integrations, so maybe we will get to hundreds or even thousands, of captain installations who know, but but it's definitely my goal for the future. So yeah happy captain christmas.

B

A

Watch this youtube.