This message was deleted.

Thanks Mark. Is 1.2.2 still targeted for May so those with 1.2.1 will have to wait until then to upgrade? And presumably Rancher 2.8.2 is safe to use provided you don't upgrade from 2.7.11 (i.e. upgrade from some other 2.7.x version)?

Yes 1.2.2 is still targeted for May and we’re making good progress on it. As for Rancher upgrades, 2.7.10->2.8.2 is a successfully tested path and I expect anything 2.7.x prior to 2.7.11 is fine, just not 2.7.11. Good suggestion on the docs in addition to having it in the release note, I’ll see if we can get something in there.

thanks, i'll have to be patient and wait for 1.2.2 before upgrading to 1.3.0 though I might throw that on a separate NUC in the meantime

Hmm, it would be nice for Harvester to release smaller updates multiple times (and, of course, ensure that all functionalities are stable and tested). For now, it seems that we get a new release every few months (which is quite a lot of time..).

Very very dumb question. But 'which Rancher', is meant when we see these statements 🙂 I assume the rancher within Harvester -- so going into support -> Rancher cluster (having enabled ability to explore). That Rancher? Or is it also if you install the Rancher Addon, and then manage harvester via that Rancher? Or is it only if you run Rancher external from Harvester to manage Harvester? Or is it any of thesse or some of these is 2.7.11 to be concerned? 🙂

TL;DR: • "Embedded" Rancher: not affected, more as a consequence of how it is not used for creating guest clusters • rancher-vcluster: could be affected, but Harvester will not manually upgrade this. Recommend not manually upgrading this until we have a chance to publish more info on the fix • Rancher Manager deployment (not rancher-vcluster Addon): affected --- Not a dumb question at all! We haven't done ourselves any favors with how many different ways you can say "Rancher managing Harvester" and have them all be correct 😂 > I assume the rancher within Harvester -- so going into support -> Rancher cluster (having enabled ability to explore). That Rancher? The Harvester developers refer to this as the Embedded Rancher, and it is not affected. It's more of an implementation detail, so it's OK for anyone and everyone who doesn't want to think about it anymore to just ignore it. > Or is it also if you install the Rancher Addon, and then manage harvester via that Rancher? Yes, but as far as I know, Harvester will not automatically upgrade experimental addons (@great-bear-19718 for fact-checking 😂 ) So if you have previously deployed the rancher-vcluster Addon, it would be Rancher 2.7.6. Don't manually upgrade the Addon to 2.8.1 or 2.8.2 until we get a chance to iron this out. > Or is it only if you run Rancher external from Harvester to manage Harvester? A non-rancher-vcluster Addon Rancher Manager would also be affected, yes.

Thank you for the great reply! Had been wondering a while but never asked<3

harvester will not automatically upgrade the vcluster addon, it needs to be done manually