Skip to content

[backport v2.15.1] Update community EOL notification #18320

Description

@rancher-ui-project-bot

This is a backport issue for #18318, automatically created via GitHub Actions workflow initiated by @richard-cox

Original issue body:

Setup

  • Rancher version: v2.15.0 (and before

Describe the bug

  • rancher dynamic content can supply EOM and EOL metadata for the version of rancher found when running
  • these are then converted into text and used in notifications
    • dynamicContent.upcomingEom
    • dynamicContent.eom
    • dynamicContent.upcomingEol
    • dynamicContent.eol
  • we won't use EOM for community, but that shouldn't change any of our code
  • we will use EOL for community but it's a slightly different meaning
  • this means the text isn't applicable

To Reproduce

Result

  • the content talks about EOL and supported, when neither are really applicable

Expected Result

  • if the rancher is community display different messages
  • the messages are the same except
    • dynamicContent.upcomingEol
      • title: Replace the End of Life text with No more updates
      • message: Replace with This version of Rancher ({version}) will not receive updates in {days} day(s). Consider upgrading to the latest version when it is released.
    • dynamicContent.eol
      • title: Replace with No more updates
      • message: Replace with This version of Rancher ({version}) will not receive updates. Consider upgrading to the latest version.

Screenshots

Image

Additional context

Metadata

Metadata

Assignees

Labels

QA/dev-automationIssues that engineers have written automation around so QA doesn't have look at thisarea/dashboardkind/bug

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions