1. Proposed title of this feature request
"Document Helm client installation procedures (repo)"

2. What is the nature and description of the request?
Users complain that the OpenShift docs do not tell them how to maintain the Helm client on their RHEL machines in a way that's consistent with normal admin procedures.   [1][2]
The users tell us the docs do describe how to go curl a binary [3], but that's not the way an admin likes to do things.  They'd rather use admin tools like 'dnf' to do it.  Please allow this.

3. Why does the customer need this? (List the business requirements here)
They want to maintain their Red Hat machines using consistent administrative processes.  If we deviate from our recommended procedures, they have to do 'one-off actions' like curl downloads to run their infrastructure, this is inconvenient and sub-optimal.

4. List any affected packages or components.
Just docs.  We'll have to maintain a list of the repos that we put Helm client components in, though.

[1] https://gss–c.vf.force.com/apex/Case_View?srPos=0&srKp=500&id=5006R0000212cCq&sfdc.override=1
[2] https://access.redhat.com/support/cases/03952162
[3] https://docs.openshift.com/container-platform/4.17/applications/working_with_helm_charts/installing-helm.html