Description of problem:

When a user installs a Helm Chart, the content of the chart's value.yaml is copied in the form.
The chart's value.yaml is often (always?) used to provide sensible default values that can be overridden by the user. Most of the time, the user do not need to change any of these.

Having the form UI filled with default values provides a poor UX as it exposes the user to technical implementation details that are not providing any value.

This would follow more closely the UX from using the helm cli.

When I do a `helm install <chart>`, I don't need to specify the chart's value.yaml because it is already taken into account. I only need to specify any values that overrides the ones provided by the chart's value.yaml

If I remove any content from the YAML view and install the Helm chart, it works fine.
But it would be a better UX to start from empty view and only ask the users to provide any values that are different from the Chart's default

Version-Release number of selected component (if applicable):

Tested on OpenShift 4.7

How reproducible:

Always

Steps to Reproduce:
1. "+Add" > "Helm Chart" > "Quarkus v0.0.3"
2. Click on "Install Helm Chart"

Actual results:

The Form & YAML views are filled with the chart's value.yaml
In this examples, the content is:

-8<-
build:
contextDir: null
enabled: true
env: null
jvm:
imageStreamTag:
name: 'java:11'
namespace: openshift
useReleaseNamespace: false
mode: jvm
native:
dockerfilePath: Dockerfile
useDefaultDockerfile: true
output:
kind: ImageStreamTag
pushSecret: null
pullSecret: null
ref: main
resources: null
uri: 'https://github.com/redhat-developer-helm-quickstarts/quarkus-getting-started'
deploy:
applicationProperties:
enabled: false
mountPath: /deployments/config/
properties: '## Properties go here'
env: null
envFrom: null
extraContainers: null
initContainers: null
livenessProbe:
tcpSocket:
port: http
ports:

• name: http
  port: 8080
  protocol: TCP
  targetPort: 8080
  readinessProbe:
  httpGet:
  path: /
  port: http
  replicas: 1
  resources: null
  route:
  enabled: true
  targetPort: http
  tls:
  caCertificate: null
  certificate: null
  destinationCACertificate: null
  enabled: true
  insecureEdgeTerminationPolicy: Redirect
  key: null
  termination: edge
  serviceType: ClusterIP
  volumeMounts: null
  volumes: null
  global:
  nameOverride: null
  image:
  name: null
  tag: latest
  -8>-

Expected results:

The views should be empty.

Additional info:

Removing the YAML content does not prevent the installation of the helm chart.
This RFE is to avoid populating the view with the Chart's value.yaml content