Problem:

When chart repositories are added to OCP, user will often find the charts in that repo will not work properly

Goal:

Embed a new functionality in dev console that will allow a user to click on very button before they run an install. The verification can take some time so it most be allowed to run asynchronously and the state should be persistent so that other user can see the latest verification state.

Why is it important?

Will allow users to have better information about charts that have not been certified by Red Hat

Use cases

There are two use cases:

1. Run on-demand and make state persistent.
2. Run in groups for example for a whole repo, or for an artifacthub search result.

Acceptance criteria

1. I can run chart verifier and get an idea if the chart I want to use has a good chance to work well on OpenShift
2. I can run on-demand for single chart or for a group of charts.
3. I can run from oc if helm already integrated with oc.

Dependencies (External/Internal)

oc integration with helm

Design Artifacts

Stories seen today:

1. Make chart verifier a library with and API that can be run from CLI of from any go program.
2. Determine how to store the persistence of the results for chart verifier on a specific chart.
3. Integrate with Console backend and target on demand single chart first.
4. Implement multi-chart verification.

Exploration

Note