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 a better UX for experimental charts in the Apps and Marketplace - opt-in to experimental charts #5170

Open
Tracked by #6402
rosskirkpat opened this issue Feb 18, 2022 · 2 comments
Assignees
Labels
docs-impact Label for design changes that will require documentation to be updated kind/design QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this requires-prototyping Label for complex designs that would require a UX designer to create full layouts and workflows research-needed Label for design issue that requires more technical research than what is in the issue description
Milestone

Comments

@rosskirkpat
Copy link

Currently, there are two UX issues when it comes to experimental charts:

  1. if the latest version of a chart is marked as experimental there is no ability in the UI to filter out experimental chart versions to show the latest version that is not marked as experimental.

  2. If a chart has an experimental version, once selecting the chart to install you no longer see the experimental tag

Solutions:

UX Issue #1

Adding this feature would allow us to create an opt-in experience for displaying experimental charts where the user has to check a box stating something along the lines of "Show experimental charts". All of the charts shown when this box is not checked would be considered as "stable" charts.

This also provides far more flexibility on the rancher/charts side of the house as we can publish an experimental chart and a customer who has not opted-in to experimental charts would not have their UX change.

An example use-case for this is the vsphere-csi charts. We are working to bring in the newly added upstream support for Windows in the csi node daemonset via a new experimental version of the vsphere-csi chart. We want to make this chart available to rke2 windows customers on 2.6.4 but if the changes were merged today, the experimental chart would show as the latest/default chart for all customers when 2.6.4 is released. This is not the overall customer experience that we want to deliver on the GA release.

With this feature, the rke2 windows customers in the use-case would be able to opt-in to the experimental charts and install the vsphere-csi chart when 2.6.4 is released.

UX Issue #2

If a chart has a mix of non-experimental and experimental versions or only has experimental versions, we should show experimental next to the version of the chart. This is the same concept as charts showing (linux-only) when selecting a chart version. The sriov chart only has experimental versions and as you can see below, the versions are not marked as experimental once you click the sriov chart card to install it.

sriov chart

@rosskirkpat rosskirkpat added this to the v2.6.5 milestone Feb 18, 2022
@lvuch
Copy link
Contributor

lvuch commented Feb 18, 2022

related: #5007

@nwmac nwmac modified the milestones: v2.6.5, v2.6.6 Mar 21, 2022
@nwmac nwmac modified the milestones: v2.6.6, v2.6.x May 9, 2022
@catherineluse catherineluse added [zube]: Design Backlog research-needed Label for design issue that requires more technical research than what is in the issue description requires-prototyping Label for complex designs that would require a UX designer to create full layouts and workflows docs-impact Label for design changes that will require documentation to be updated and removed [zube]: To Triage labels Jul 12, 2022
@catherineluse
Copy link
Contributor

@rosskirkpat Which charts are experimental? is vsphere-csi charts the only one?

@nwmac nwmac added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-impact Label for design changes that will require documentation to be updated kind/design QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this requires-prototyping Label for complex designs that would require a UX designer to create full layouts and workflows research-needed Label for design issue that requires more technical research than what is in the issue description
Projects
None yet
Development

No branches or pull requests

7 participants