Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RKE1 deprecation banner on cluster management page #13379

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

momesgin
Copy link
Member

Summary

Fixes #13284

Technical notes summary

A warning banner will be displayed on the Cluster Management page only if at least one RKE1 cluster is installed. It relies on the existing flag isRke1().

Since this is not a permanent change a manual testing will be sufficient.

Areas or cases that should be tested

Try adding and removing an RKE1 cluster to make sure it's displayed properly.

Areas which could experience regressions

Screenshot/Video

dep.mov

Checklist

  • The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
  • The PR has a Milestone
  • The PR template has been filled out
  • The PR has been self reviewed
  • The PR has a reviewer assigned
  • The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
  • The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

@momesgin momesgin added this to the v2.11.0 milestone Feb 11, 2025
@momesgin momesgin self-assigned this Feb 11, 2025
@momesgin
Copy link
Member Author

@richard-cox re your comment about relying on the new flag, I discussed it with @codyrancher and since those changes might not end up in 2.11 we should go with the existing isRke1() for now.

Copy link
Member

@richard-cox richard-cox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@codyrancher can you make sure the update to support this is in vai world tracked somewhere?

@momesgin momesgin requested a review from richard-cox February 12, 2025 18:50
@momesgin momesgin marked this pull request as ready for review February 12, 2025 21:33
@momesgin momesgin requested a review from jordojordo February 14, 2025 18:34
Copy link
Member

@richard-cox richard-cox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one text suggestion, also the issue mentions showing a warning on the create/edit screen. if we show it there we should probably also show it in the detail page as well?

if not already, this should have a general UX review including the additional places to show the warning

@@ -1871,6 +1871,7 @@ cluster:
=1 { {pool_name}: The provided value for {fields} was not found in the list of expected values. This can happen with clusters provisioned outside of Rancher or when options for the provider have changed. }
other { {pool_name}: The provided values for {fields} were not found in the list of expected values. This can happen with clusters provisioned outside of Rancher or when options for the provider have changed. }
}
rke1DeprecationMessage: 'Rancher Kubernetes Engine (RKE, RKE1) will reach end of life on July 31, 2025. Rancher 2.12.0 and later will no longer support provisioning or managing downstream RKE1 clusters. We recommend replatforming RKE1 clusters to RKE2 to ensure continued support and security updates. Learn more about the transition <a href="https://www.suse.com/support/kb/doc/?id=000021518" target="_blank" rel="noopener noreferrer nofollow">here</a>.'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
rke1DeprecationMessage: 'Rancher Kubernetes Engine (RKE, RKE1) will reach end of life on July 31, 2025. Rancher 2.12.0 and later will no longer support provisioning or managing downstream RKE1 clusters. We recommend replatforming RKE1 clusters to RKE2 to ensure continued support and security updates. Learn more about the transition <a href="https://www.suse.com/support/kb/doc/?id=000021518" target="_blank" rel="noopener noreferrer nofollow">here</a>.'
rke1DeprecationMessage: 'Rancher Kubernetes Engine (RKE / RKE1) will reach end of life on July 31, 2025. Rancher 2.12.0 and later will no longer support provisioning or managing downstream RKE1 clusters. We recommend replatforming RKE1 clusters to RKE2 to ensure continued support and security updates. Learn more about the transition <a href="https://www.suse.com/support/kb/doc/?id=000021518" target="_blank" rel="noopener noreferrer nofollow">here</a>.'

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has undergone a general ux/ui review, but I think your feedback on adding the banner to the details page really makes sense. I'll address your comments.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think another good place to display this banner would be the create cluster page where we have the RKE1/RKE2 toggle, and only show it when RKE1 is active. I'll have a meeting with Ken to review your suggestion as well as mine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RKE1 EOL UI Warnings
2 participants