Goal:

sabre1041 has been kicking off the effort for oc helm, an openshift cli plugin to integrate with platform capabilities supporting Helm.

We would like to integrate the tool and provide it a bit more visibility into the product.

Task:

• Reference it as part of the product documentation
  • Documentation about OpenShift CLI plugins
  • Documentation about Helm on OpenShift
• Blog post
• Integration with WebTerminal Operator by default
• Have the Helm team ready to contribute and maintain along the OpenShift release cycles.

Possible extensions:

• Add a custom registry
• Validate Charts for OpenShift readiness? (As a dev, I should be able to use the chart-verifier tool on my chart)

Problem:

Today customers that want to use helm have two interfaces: the helm cli (binary) and the ocp helm console. This brings a few problems that results in different experience while using different interfaces:

1. On helm cli there is not easy way to coordinated a consistent version per client, different user can potentially have diff clients with diff features and bug fixes.
2. On Dev Console all user are using the same helm version
3. When helm cli is used there is no secured way to track metrics for the releases at the cluster level because releases are stored in secrets.
4. When Dev Console is used we can track metrics for every operation on the helm releases
5. When helm cli is used to install charts with dependency charts. It is not possible to update the release from helm console without reseting the values file. Making it harder for user to make values only updates.

Goal:

Support oc helm that will call same helm backend that Dev Console calls.

Why is it important?

Consistency on the cli and gui experience, and more accurate metrics collection

Dependencies (External/Internal)

oc approval of subcommand or process to integrate plugins

Exploration

There are two ways to do this, one is with plugin approach and another with an oc subcommand. We need to explore both options

Note