Problem:

Documentation on Helm support for OpenShift is everywhere and not efficient enough at connecting all the different pieces together. It's likely that a end-user will miss information and not understand the complete scope of the Helm support on openshift.

For example, 3 different places where it is speaking about Helm:

• Helm Charts from the developer perspective on openshift 4: https://docs.openshift.com/container-platform/4.7/applications/application_life_cycle_management/odc-working-with-helm-charts-using-developer-perspective.html
• Configure custom Helm Chart repositories: https://docs.openshift.com/container-platform/4.7/cli_reference/helm_cli/configuring-custom-helm-chart-repositories.html
• Helm is also integrated in the Web Terminal: https://docs.openshift.com/container-platform/4.7/web_console/odc-about-web-terminal.html so you can use the helm CLI directly from the Web Terminal if you installed it.

Goal:

Helm continues to experience broad adoption in the Kubernetes ecosystem as the defacto package manager. As a result, we need to get Helm a better touch point interaction for our openshift users/customers. Helm must be treated as a first class citizen of OpenShift. 

That impacts documentation.

For that, the goal would be to provide a single page about Helm that will highlight all the capabilities that are supported for Helm on OpenShift. We need a single place that will include documentation about:

• Using Helm Charts provided out of the box
  • Red Hat Charts
  • Community Charts
  • Certified Charts (in this section, we will highlight and reference to the partner certification program)
• Explain how to configure custom helm Chart
• Highlight the capabilities provided by the Developer Perspective
• Highlight, how people can use Helm CLI, how they can get it...
• Speak about integration with the WebTerminal
• Speak about the oc-helm plugin
• Speak about the chart-verifier tool that could be helpful from end-user point of view

Why is it important?

Helm continues to experience broad adoption in the Kubernetes ecosystem as the defacto package manager. As a result, we need to get Helm a better touch point interaction for our openshift users/customers. Helm must be treated as a first class citizen of OpenShift. 

Use cases: