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

Add-On Config Area UX Improvements: Additional Manifest Section Visibility in Add-on Config area #11918

Open
skanakal opened this issue Sep 13, 2024 · 2 comments
Labels
JIRA kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this status/waiting-ux
Milestone

Comments

@skanakal
Copy link
Contributor

skanakal commented Sep 13, 2024

Setup

  • Rancher version: 2.9.1
  • Rancher UI Extensions:
  • Browser type & version: any

Describe the bug

The Additional Manifest section in the RKE2 cluster configuration dashboard's "Add-On Config" area is frequently overlooked by users due to its location further down the page. Many customers fail to notice, resulting in missed configurations. Additionally, the form-based editor does not provide a clear or user-friendly way to interact with the additional manifest settings, confusing users accustomed to direct YAML editing.

To Reproduce

  • create custom rke2 cluster with CNI: cilium
  • Click on the Edit Config and click on "Add-on Config" under Cluster Configuration

Result
The additionalManifest section is hidden further down the "Add-On Config" area

Expected Result

The additionalManifest section should be more prominent and easily accessible, potentially through a collapsible or drop-down UI element that makes it clear or add another tab for additional manifest

Screenshots

maybe something like this:
image

Additional context

Internal ref: SURE-8962

@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 Sep 13, 2024
@gaktive gaktive added this to the v2.11.0 milestone Sep 16, 2024
@skanakal
Copy link
Contributor Author

@gaktive @dkeightley Looks like this has been implemented here
#12066

I can confirm on 2.10 cluster:
image

@dkeightley
Copy link

Yes, thanks! I noticed it was also added in ~v2.9.4

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

No branches or pull requests

4 participants