-
Notifications
You must be signed in to change notification settings - Fork 88
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
🐛 Adapt kairos upgrade list-releases command to handle new repositories #1999
Comments
wip branch: https://github.com/kairos-io/kairos-sdk/tree/1999-introduce-versioneer I will move all logic to golang so that we can implement other things like:
|
We need this change: #2035 |
Sample output:
or (when only k3s version is higher):
|
The upgrade with no version passed must have been broken for a while:
because we sanitize the spec before we handle the empty source. I guess, since nobody complained, it's ok to deprecate that feature and always require a version. |
Instead of re-implementing the |
Didn't Santosh mentioned they were using it? not sure in which version they are atm ... but I agree, probably it's not being relied on so it's safe to remove |
to let the kairos-agent handle upgrades from now on. It used to be that provider-kairos returned releases from the provider-kairos repository but it's no longer the case. Everything is release in the kairos-io/kairos repository and the new versioneer library of the kairos-sdk (which is used in the kairos-agent) is capabable of handling both "standard" and "core" images. Part of: kairos-io/kairos#1999 Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
We need to make sure this does not break other provider upgrades because of the removal of the bus #2072 |
kairos-agent upgrade --source
or some fancy selectorrelates to #1998
The text was updated successfully, but these errors were encountered: