[LFX Mentorship] Automate the release process

[rexagod]

Hello, thank you for showing interest to KSM's LFX issue!

Every time a release is cut, there's a renewed interest towards automating the release process, rather than repeating the same steps manually.

There have been efforts in the past to drive this to completion, initially #2085 which was followed by #2325, but since KSM is unarguably the most active sub-project under SIG Instrumentation, and given the maintainers' limited bandwidth, there's little time to spare after the weekly triages and follow-ups on more pressing issues.

As such, we'd like to guide and support someone who can resume the effort, as well as address any gaps or bring any improvements to the proposed pipeline (SBOM generations, a more integrated govulncheck step, etc.).

If you're interested, please feel free to come by and say hi, we'd love to hear from you! 👋

[Omswastik-11]

Hii @rexagod 👋!! I would like to apply for this project in LFX term 3 .
Previously worked on GitHub workflows of medic/pyxform . Can you suggest to some relevant good-first-issues so that I can contribute to the repo and understand the project as well ?

Thanks for your attention !! looking forward to your response 👍

[rexagod]

Hi, @Omswastik-11! 👋

Thank you for piping up, I glanced over our issue tracker and #2043 seems like a good entry point to familiarise yourself with the user-facing options KSM offers.

Furthermore, I'd suggest joining the SIG bi-weekly discussions to introduce yourself. Also please note that we'll formally kick-off this effort once the cncf/mentorship facing PR is in, just so we stick to the upstream process, which shouldn't take long IMO.

[Omswastik-11]

Thanks @rexagod for replying !!
I will try to attend the session 👍.
I will look at the details you shared and let you know my doubts and ideas within some days 👍. If you have any thing else ping me

[priyanshuharshbodhi1]

Hey @rexagod , I am up for it.
I have contributed previously to contributed to kubestellar.io which you can see here
And I was also a mentee in GSoC'25 in Rocket.Chat

[richabanker]

/triage accepted

[priyanshuharshbodhi1]

@rexagod , Can you share some more good-first-issues ?

[gitsofaryan]

hi @rexagod @richabanker, my name is aryan jain and im a computer science student. im interested to work on this project, i have previously worked on automating release pipeline in my Google Summer of Code period Proof of Work here i worked on automating release of binaries with every release foe desktop version of simultor in Rust. i have also written a many CI's including tests. I really interested and confident that i will able to work and complete this project, i need your attendtion to assign me some issues related the project so you can better undersatand my abilities! thank you.

[StarTrooper08]

hi @rexagod @richabanker

Got to know about this project from LFX Mentorship portal and I found this project interesting.

I have worked mostly with GH Actions, and yes also with bash scripting! And known to concept like semantic versioning and cron schedule jobs which might be helpful for this project.

Just a curious question!
Does this project requires knowledge of GH actions or other CI/CD tool? Because it nowhere mentioned in the project description but I think the project revolves around GH Actions. Please correct me I'm wrong here.

Some proof of work of mine.
https://atharva08.hashnode.dev/efficiency-unleashed-dockerizing-and-optimizing-a-fastapi-app-with-slimtoolkit-and-github-actions

Except reusable GH Actions workflow. I had build a custom actions previously where I learned the fundamentals of GH Actions in depth. Project : https://dev.to/hey_atharva/notify-bot-github-action-workflow-2676

That's the short intro regarding my skill-set and interest to work on this project.

Thank you for your time.

Regards,
Atharva S

[PhantomInTheWire]

Hello @rexagod, @richabanker,

I am Karan from the Indian Institute of Information Technology. I’m very interested in this project. I’ve previously contributed to other CNCF projects and their CI processes, and I’m intimately familiar with GitHub Actions and its quirks.

As proof of work, here are the PRs I made: [migrated SOBM generation of WasmEdge to using a REST API from the legacy GitHub Action](WasmEdge/WasmEdge#4196), and [removed legacy cgroup v1 devices from Runwasi's workflow](containerd/runwasi#996).

I have also worked on a lot of other deep tech stuff and scripting in the CNCF ecosystem (you can look over my profile for those).

I would be thrilled to work with you guys on this.

[Peacesandy]

Hi @rexagod @richabanker 👋

I’m Peace Sandy, and I came across this project through the LFX Mentorship portal. I’m really excited about the opportunity to contribute to Kube State Metrics especially in driving the release automation work forward and supporting the wider SIG Instrumentation goals.

I’ve actively contributed to several open source projects including:

🛠 Mautic Community Handbook – improved contributor-facing docs

📘 TWMP Technical Writing Course – migrated documentation to Docusaurus and redesigned the landing page

🧬 Bioconductor – contributed documentation and improvements to the open source bioinformatics project

You can find more of my work on GitHub: https://github.com/Peacesandy

I’m eager to start contributing to open issues as soon as possible, and I’d love to pick up where the previous automation efforts left off. I'm also open to tackling any other areas that need attention within the project.

Looking forward to learning, contributing, and collaborating with the team!

[Rishab87]

hey @rexagod , I'm Rishab, a third year undergrad, I've been getting into devops lately and I'm very interested in this issue. I've already worked with ci/cd pipelines and contributes to several open source orgs. I am a part of gsoc too.

I've already been exploring the codebase and have submitted a few contributions to get familiar with the project:

• feat: include reason label to kube_deployment_status_condition #2719
• fix: Fixed the format of Markdown files #2714
• feat: Add performance tests for custom-resource-state-metrics perf-tests#3483
• docs: High Availability Setup documentation #2715

Looking forward to learn and contribute here.

[assu-2000]

Hi @everyone,
For those who missed the info session held on 15/07, I suggest you take a look at it to better understand the community's needs, how it works, and some useful tips like "Avoid The Good First Issue Trap" and the "why" exlpained .
==> K8s New Contributor Orientation for 2025-07-15.
All the best to y'all ...