Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🤖 Automatically generate JSON with latest versions #1304

Open
Tracked by #2130
sdwilsh opened this issue Apr 15, 2023 · 2 comments
Open
Tracked by #2130

🤖 Automatically generate JSON with latest versions #1304

sdwilsh opened this issue Apr 15, 2023 · 2 comments
Labels
ci enhancement New feature or request

Comments

@sdwilsh
Copy link
Contributor

sdwilsh commented Apr 15, 2023

Is your feature request related to a problem? Please describe.
The Kairos version contains the version of Kairos (like 1.6.1) as well as the version of k3s (like 1.26.1, so the full version was v1.6.1-k3sv1.26.1-k3s1). Unfortunately, at least as far as I can tell, this makes it impossible for Renovate to help someone keep appraised of version updates like they might for other libraries. For 2.0, the equivalent version was v2.0.0-k3sv1.26.3-k3s1. Note that both the versions of k3s and Karios changed. While Renovate could track the latest version of both of those, that runs the risk of creating a version that doesn't actually exist.

Describe the solution you'd like
I think the easiest way to handle this might be some kind of alias system such that v2.0.0-k3sv1.26 maps to the specific point release of k3s that actually ships with. Anyone who wants to manage the Kairos version with a specific version of Kubernetes can at least get the notifications about Kairos being up-to-date.

Describe alternatives you've considered
I've tried a few options with Renovate and their Regular Expression capabilities, but they have not panned out. I'm not sure of any options on the Kairos side of things other than what I've suggested.

Additional context
I use an ansible play to run an upgrade on my cluster, and I have Renovate configured on the repository to help me stay up-to-date on libraries I depend on.

@sdwilsh sdwilsh added the enhancement New feature or request label Apr 15, 2023
@mudler
Copy link
Member

mudler commented Apr 17, 2023

Hey @sdwilsh, good thoughts in here.

Having only part of the version could be really problematic - then you can't anymore know what's the minor version used, which is ok for most cases I guess - but we should probably annotate that as part of image labels, or similar.

I'm fine with dropping part of the versions, however, I'm thinking that maybe we should just generate a json when we release, with all the versions informations in there and publish it somewhere (ideally, our website? I guess it's rather easy to automatize that with a PR). So there is no more guessing around versions. Would that help in your case too?

@mudler mudler removed their assignment Apr 17, 2023
@mudler mudler moved this to Todo 🖊 in 🧙Issue tracking board Apr 17, 2023
@sdwilsh
Copy link
Contributor Author

sdwilsh commented Apr 17, 2023

Yeah, I agree that the information contained in the version numbers is useful, so it would need a new home.

@mudler mudler changed the title Kairos version unable to be managed with Renovate 🤖 Automatically generate JSON with latest versions Apr 17, 2023
@mudler mudler added the ci label Apr 17, 2023
@mudler mudler mentioned this issue Apr 17, 2023
29 tasks
@mudler mudler mentioned this issue Sep 5, 2023
22 tasks
@mudler mudler mentioned this issue Dec 18, 2023
38 tasks
@mudler mudler mentioned this issue Apr 18, 2024
33 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

2 participants