This message was deleted.

Well the skinny I heard is that

community

and

prime

are not currently like how Rancher is, where

prime

is locked behind a support contract. Instead, the first release will always be

community

- which is considered to never be

stable

like in the old system, but rather

prime

indicates that it's production quality and will be a release version of Virtualization (vs upstream Harvester) Upgrades to prime versions will appear with the upgrade version like how the

stable

tag use to. The prime releases being public might get changed at some point in the future, but aren't currently going to change. Hope others find that useful. 🙂

I'm not from Suse, but might have a bit of a clue: From the new lifecycle it should be possible to ugprade from any 1.5 version to any 1.6 version (as long as a compatible Rancher is running, 2.12.x in this case). Technically it's the rke2 version in Harvester which defines whether or not it's possible to upgrade directly, since minor versions cannot be skipped (not the only part, but the most important one). The rest of your information is correct.

The bigger change for me, at least in part, was that 1.x.0 releases would never be stable. They weren't always

stable

in the past, but sometimes they were.

Even more interesting: Will Suse be able to keep up with that lifecycle. Imho it is still too static for e.g. zero day CVEs, but it's a step into the right direction. I'd expect more releases in a stable version, but this is not the case yet. The competition is upgrading every 3-6 weeks...