Safe upgrade paths

[Arsenikki]

First of all thanks for this very cool project!

The challenge we have is that our customers are in the life sciences industry where often there's very slow change approval process. This means we end up with version drift as some customers may be fine with always running the latest versions while other customers could only be accepting changes every 6 months or so. This adds a fair bit more complexity into upgrade process especially since there's usually specific suggested upgrade paths.

Talos docs reference following upgrade path example:

For example, if upgrading from Talos 1.0 to Talos 1.2.4, the recommended upgrade path would be:
upgrade from 1.0 to latest patch of 1.0 - to v1.0.6
upgrade from v1.0.6 to latest patch of 1.1 - to v1.1.2
upgrade from v1.1.2 to v1.2.4

Are there any plans to automatically handle safe upgrade paths within this project or do you see some other ways around this? Currently we are thinking of building our own workflows which would automatically be updating the tuppr custom resources based on the recommended upgrade path and checking the upgrade statuses in between.

[onedr0p]

There are no plans to implement this as of right now, keep in mind this project is largely focused with homelabs in mind. I can see how it might be useful so I'll keep the issue open.

In the meantime you can probably use renovate and separate major / minor and minor / patch, if you are not using renovate, I am unsure outside manually handling the upgrade process by following the Talos docs.

• https://docs.renovatebot.com/configuration-options/#separatemajorminor
• https://docs.renovatebot.com/configuration-options/#separateminorpatch