This is a BUG REPORT

Version of Helm and Kubernetes:

• Helm
  • 2.10+
• Kubernetes
  • 1.11.3
  • 1.11.4
  • 1.13.x

Which chart:
stable/prometheus-operator
Probably all versions of the chart but occurred on 0.1.7, 0.1.21,4.0.0

What happened:
Under some circumstances - apparently just the above helm and kubernetes version the install with default values fails with

Error: validation failed: [unable to recognize "": no matches for kind "Alertmanager" in version
"monitoring.coreos.com/v1", unable to recognize "": no matches for kind "Prometheus" in version 
"monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version 
. . .
. . .

There appears to be a race condition occurring because doing a kubectl get crd | grep coreos a few times will show the resources gradually appear (4 in total) but much later after the error has already occurred and the chart install has failed.

This is reproduceable multiple times if the resources are deleted and the chart installation is attempted again.

What you expected to happen:
The crd-install hook used to create the 4 CRDs in this chart should either succeed or fail.

How to reproduce it:
Attempt to install the chart on a cluster without the the coreos CRDs and the install fails

** UPDATE **
A proposed fix for this issue can be seen here: helm/helm#5112