Look at gating mechanism so that Elemental 2.0.0 doesn't run in Rancher 2.10

[aalves08]

Look at gating mechanism so that Elemental 2.0.0 doesn't run in Rancher 2.10. User reported this problem, which breaks their system.

Workaround is to use safemode if Rancher get's "stuck" and not running

[richard-cox]

The problem isn't the dashboard's gating mechanism.

• Rancher 2.10.0 roughly aligns with a shell version of 3.x
• The latest elemental extension is for 2.9 only but has the annotation "catalog.cattle.io/ui-extensions-version": ">= 2.0.0-0",
• Rancher 2.10.0 evaluates 3.0 as >= 2.0 so loads the extension

The fix is to update the existing chart. I don't think we can release a new version of the extension as the previous one will still load and we shouldn't be putting 'if extension x with version y don't load' in dashboard if there's a better solution.

[gaktive]

There's one report from the community of trying to run Elemental 2.0.0 in Rancher 2.10.0 today so folks are hitting this.

[richard-cox]

Update to #12631 (comment)

Fix needs to cover two scenarios

• Already installed elemental
  • 2.10.0 timeframe - Release information on how to remove plugin (/safemode or by deleting resource/s)
  • 2.10.1 timeframe - Gonnna backtrack on Look at gating mechanism so that Elemental 2.0.0 doesn't run in Rancher 2.10 #12631 (comment), we would need to put in an if rancher 2.10 and elemental and version 2.0.0 blocker in dashboard code
• Preventing new elemental installs
  • Need to release 2.0.1 with the correct annotation
  • Should also double check 1.x, and other plugins (including examples)

[aalves08]

Waiting for Elemental QA to test elemental-2.0.0-rc.3 and elemental-3.0.0-rc.3 to get the sign-off to release 2.0.0, 2.0.1 and 3.0.0

[aalves08]

closing this issue since the new versions of Elemental have been released and the action points have been communicated to the stakeholders and general public