Charts: [stable/prometheus-operator] Errors with Helm3

[shadycuz]

Describe the bug
When deploying the chart:

shadycuz-> kubectl create namespace monitoring
namespace/monitoring created
[~/repos/shadycuz/kube_monitoring]
shadycuz-> helm upgrade -i --namespace monitoring -f values.yml monitoring stable/prometheus-operator --version 8.3.3
Release "monitoring" does not exist. Installing it now.
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
NAME: monitoring
LAST DEPLOYED: Sun Dec  8 15:35:40 2019
NAMESPACE: monitoring
STATUS: deployed
REVISION: 1
NOTES:
The Prometheus Operator has been installed. Check its status by running:
  kubectl --namespace monitoring get pods -l "release=monitoring"

Visit https://github.com/coreos/prometheus-operator for instructions on how
to create & configure Alertmanager and Prometheus instances using the Operator.
[~/repos/shadycuz/kube_monitoring]
shadycuz-> kubectl --namespace monitoring get pods -l "release=monitoring"
NAME                                                   READY   STATUS    RESTARTS   AGE
monitoring-grafana-57699d9c7c-9fgbm                    2/2     Running   0          72s
monitoring-prometheus-node-exporter-bsj8f              1/1     Running   0          73s
monitoring-prometheus-node-exporter-k84m6              1/1     Running   0          73s
monitoring-prometheus-node-exporter-kpqb4              1/1     Running   0          73s
monitoring-prometheus-node-exporter-l8gjv              1/1     Running   0          73s
monitoring-prometheus-node-exporter-shvd5              1/1     Running   0          73s
monitoring-prometheus-oper-operator-689bfd4f59-qkmks   2/2     Running   0          72s

Version of Helm and Kubernetes:

shadycuz-> helm version
version.BuildInfo{Version:"v3.0.0", GitCommit:"e29ce2a54e96cd02ccfce88bee4f58bb6e2a28b6", GitTreeState:"clean", GoVersion:"go1.13.4"}

shadycuz-> kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:18:23Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:09:08Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}



md5-ec31de5aefb7203c75bfd45177573258



stable/prometheus-operator --version 8.3.3

What happened:
Errors about CRD

What you expected to happen:
No errors ;)

How to reproduce it (as minimally and precisely as possible):
Try to install chart with Helm 3.0, after some googling it appears this is a common error for charts not compatible with Helm3

Anything else we need to know:
I logged into grafana and I do see some dashboards and data looks populated but I haven't looked everything over.

[Belonias]

Did you find any solution? I am experiencing the same error but when the installation is done I don't get the message that everything deployed fine.

[shadycuz]

@Belonias Everything seems to be working for me. My only complain is when I change from one dashboard to the other, It asks me to save the dashboard even though I didn't change anything. Not sure if thats a bug with the dashboards, grafana or what.

[Belonias]

ok @shadycuz thank you for your time to reply. For me it seems the problem was EKS in GKE everything works perfect, I think that I am messing somehow in cluster creation.

[shadycuz]

@Belonias I think I was wrong. The CRD's don't get deployed.

shadycuz-> kubectl get prometheuses.monitoring.coreos.com -o yaml
apiVersion: v1
items: []
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

This means you will not be able to do lots of things the Prometheus Operator is for, like adding new services into monitoring =/.

[maver1ck]

Can we maybe hide this hook on helm3 ?

[maver1ck]

I have error and failed release because of this error:

FAILED RELEASES:
NAME
prometheus-operator
in ./helmfile.yaml: failed processing release prometheus-operator: helm exited with status 1:
  manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
  manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
  manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
  manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
  manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
  Error: context canceled

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[lucj]

Hello,
any update on this issue ? Got the same thing on a fresh k3s cluster.

[Ps3ud-0nym]

I'm also seeing this. Could somebody look into this please?

[NicoForce]

Also seeing this problem, opting to install helm 2 and use it.

[diversario]

Somewhat unexpectedly, I was able to install the chart with Helm 3 by setting prometheusOperator.createCustomResource=false (like so). My understanding is that Helm 3 picks up the contents of the crds/ directory, but doesn't do anything special with it (so "helm.sh/hook": crd-install doesn't do anything). Without it, CRDs end up under templates/ dir, where Helm _does_ process them as templates, causing the error.

[onedr0p]

Moreover in the docs for prometheusOperator.createCustomResource=false

Regardless of value of this, Helm v3+ will install the CRDs if those are not present already. Use --skip-crds with helm install if you want to skip CRD creation.

My understanding of that is if you are using helm 3 make sure you have prometheusOperator.createCustomResource=false so that the warnings don't show up.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[stale[bot]]

This issue is being automatically closed due to inactivity.

[lishitiancn]

Come on. Quickly support helm3

[onedr0p]

This works great with helm 3, what are you on about?

[lishitiancn]

When deploying... The info log doesn't matter?
[root@master ~]# helm install prometheus-operator stable/prometheus-operator -n prometheus-operator
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-instal"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"

[onedr0p]

Did you read the comments, specially the one I posted like 2 comments back?

[Hashfyre]

Existence of an workaround does not mean the error does not exist, if we have to manually create CRDs and disable CRDcreation through a flag, that's not a fix. Ordered CRD Creation does need a fix for helm3.

[abdennour]

This issue last for more than 6 months.. and till now it is not fixed.
PR approval also took time.
Any other solutions ?

[faraonc]

Still an issue for

$ helm version
version.BuildInfo{Version:"v3.3.4", GitCommit:"a61ce5633af99708171414353ed49547cf05013d", GitTreeState:"dirty", GoVersion:"go1.15.2"}