Problem:

The registry of helm-charts for OpenShift should require as minimum effort from us but deliver great value to end-users and customers who will be consuming those charts. 

How do we ensure that the Helm charts we are providing out of the box with OpenShift are working properly when a new version of OpenShift is coming along? 

How do we cleanup Charts that are not working anymore?

Goal:

Provide an automated process that will allow us to scale the registry from manual testing while preserving the end-user value.

The process should handle the following scenarios (not exhaustive):

• Testing available charts when a new version of OpenShift is coming along
• Allowing a Chart provider (community author, red hat or partner) to test their charts against a specific set of OpenShift version

Why is it important?

We want to provide a rich and "robust" registry of applications, tools and services that will be provided by Helm Charts. For that, we need to make the life of a Chart author as easy as possible.

• we should lower the entry bar to the bare minimum so it gets easy to submit a chart to our registry. 
• we should maintain the consistency of the registry - so that Chart author are notified when their Charts have issues
• we should make sure that any charts that is available to an OpenShift user is usable, maintained and safe to use

Use cases:

1. As a Chart author submitting an Helm chart, I should be able to test and certify my Charts on all version of OpenShift that are currently supported, so I make sure my charts fits the requirements of the platform. 
2. As a Chart author, once I submitted my chart, I should be notified when a new version of OpenShift is coming and if my Charts is still compliant or not. 
3. As maintainer of the Chart registry, I should be able to know what are the Charts that are not compliant anymore when a new version of OpenShift is coming. 

Acceptance criteria:

TBD

Dependencies (External/Internal):

Design Artifacts:

Exploration:

Note: