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

Create page for SCC registration for Rancher Prime #13288

Open
cnotv opened this issue Feb 4, 2025 · 4 comments
Open

Create page for SCC registration for Rancher Prime #13288

cnotv opened this issue Feb 4, 2025 · 4 comments
Assignees
Labels
area/prime kind/enhancement priority/0 QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@cnotv
Copy link
Member

cnotv commented Feb 4, 2025

Describe

Based on following design, create page for SCC registration.
Page will be placed under RM Settings.
Implementation will be finally part of the Rancher Prime extension.

Image Image
@cnotv cnotv added this to the v2.11.0 milestone Feb 4, 2025
@cnotv cnotv self-assigned this Feb 4, 2025
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Feb 4, 2025
@cnotv
Copy link
Member Author

cnotv commented Feb 12, 2025

Updated the design given the new information with RFC 22

@cnotv
Copy link
Member Author

cnotv commented Feb 13, 2025

@kwwii It seems like there's a bug to extend the setting page navigation to add the registration there. We will have to either fix it (#13396) or pick another place.

@cnotv
Copy link
Member Author

cnotv commented Feb 13, 2025

Updated UI:

Image
Image
Image

@cnotv
Copy link
Member Author

cnotv commented Feb 14, 2025

Latest agreed UI/UX tested with code.

Kapture.2025-02-14.at.12.16.41.mp4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/prime kind/enhancement priority/0 QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

1 participant