Problem:

We are playing catchup with Helm releases and each time there is a new release, we need to backtrack that manually.

Goal:

Automate the process in order to ship with every new release of OCP, the latest available version of Helm which will be compatible with OpenShift.

The process should automate as much as we can so that it's a low effort for the team:

• Pull the latest version of Helm
• Test it on OpenShift (with https://issues.redhat.com/browse/HELM-36)

In a later phase, we could look at also automating (as part of other epics):

• Tests of existing charts from the catalog 
• Tests of chart verifier
• Tests with ODC/SBO and potential other dependencies.

Why is it important?

• Free some of our engineering effort
• Complete process to test Helm on OpenShift
• Make sure we don't miss opportunity to deliver value (from upstream Helm) to our customers

Use cases:

Acceptance criteria:

1. Each time there is a new release of helm, we should be notified about it's availability and if we want to update it in OpenShift
2. Tests should be triggered each time a new version of Helm is coming along

Dependencies (External/Internal):

Design Artifacts:

Exploration:

Note: